Virtual Private Server (VPS) Hosting provided by Central Point Networking cpnllc.com
For some reason, the "Nodelist" and "Recent Callers" features are not working.
| Sysop: | Ray Quinn |
|---|---|
| Location: | Visalia, CA |
| Users: | 60 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 11:32:57 |
| Calls: | 12 |
| Files: | 12,930 |
| Messages: | 98,465 |
Check out the US 99 menu above for links to information about US Highway 99, after which the US 99 BBS is named.
Be sure to click on the Amateur Radio menu item above for packet BBSes, packet software, packet organizations, as well as packet how-to's. Also included is links to local and some not-so-local Amateur Radio Clubs.
Is there a way to make BBBS render the (recommended) CHRS kludge, instead of CHARSET?
I have wondered about that but I have no answer for your question.
If you netmail Kim Heino at 2:222/2 or email b@bbbs.net he would
have a better idea when or if that change can be made.
Is there a way to make BBBS render the (recommended) CHRS kludge,
instead of CHARSET?
I have wondered about that but I have no answer for your question.
If you netmail Kim Heino at 2:222/2 or email b@bbbs.net he would have
a better idea when or if that change can be made.
If you netmail Kim Heino at 2:222/2 or email b@bbbs.net he would have
a better idea when or if that change can be made.
I netmailed Kim and he replied fast! Next release will use CHRS.
+1!
I netmailed Kim and he replied fast! Next release will use CHRS.That is good news. I also netmailed Kim about this along with
+1!
UTF-8 and CRAM-MD5 support. All are being added although some may
take time to implement.
If you netmail Kim Heino at 2:222/2 or email b@bbbs.net he would have
a better idea when or if that change can be made.
I netmailed Kim and he replied fast! Next release will use CHRS.
+1!
That is good news. I also netmailed Kim about this along with UTF-8 and
CRAM-MD5 support. All are being added although some may take time to implement
I'll be watching the bbbs.net website for updates.. :)
That is good news. I also netmailed Kim about this along with UTF-8 and
CRAM-MD5 support. All are being added although some may take time to
implement. I'll be watching the bbbs.net website for updates.. :)
It is neat :)
Yes, Toy-6 includes cram-md5 support and is working well for me. You
could ask Kim about that.. :)
Yes, Toy-6 includes cram-md5 support and is working well for me. You
could ask Kim about that.. :)
There is something about the file downloading via http methods instead ftp, through the web interface?
There is something about the file downloading via http methodsI don't think so although that would be good to have today since most browsers don't support FTP anymore.
instead ftp, through the web interface?
I don't think so although that would be good to have today since most
browsers don't support FTP anymore.
If you don't know, it means that it's not yet implemented in Toy-6. We will wait until Toy-7.
We don't know what Toy-7 has in store, but if you ask for a feature it
may get implimented.
We don't know what Toy-7 has in store, but if you ask for a feature it
may get implimented.
Since Janis is gone, you seem to be the liaison with Kim.
How do you think is better to raise to him the feature requests? Direct netmail?
This echo?
El Martes 22 Agosto 2023 a las 05:48, Alan Ianson escribi≤ a Enric Lleal Serra
We don't know what Toy-7 has in store, but if you ask for a feature it
may get implimented.
Since Janis is gone,
Janis is not gone, I'm sure she is lurking.. :)
How do you think is better to raise to him the feature requests?
Direct netmail?
I think b@bbbs.net will work.
I am NOT gone, Enric :) :)
I did resign Fidonet for about two months because I was a bit burned out... bu
I returned as 1:261/38 as soon as I was able :)
You should contact Kim via e-mail, at b@bbbs.net, he will probably respond to you via email.
Hey, Janis!Hi Enric :) :)
I am NOT gone, Enric :) :)I'm happy to see you here... :-)
I did resign Fidonet for about two months because I was a bit burned out... >> I returned as 1:261/38 as soon as I was able :)
I lost your trail in some moment and I heard about your departure... It's hard
to follow the international echoes sometimes... Sorry.
You should contact Kim via e-mail, at b@bbbs.net, he will probably respond to >> you via email.
Done. Thanks...
I know.. and I think things got confused when Dave Drum thought my
system was down, but it was not - it was probably problems with my
ISP... who knows.
Done. Thanks...Sounds good :)
I know.. and I think things got confused when Dave Drum thought my
system was down, but it was not - it was probably problems with my
ISP... who knows.
Ashes to ashes... what it's important is we are alive and kicking[1] ;-)
Very good. He has resolved the CRAM feature request and he's testing the http download is his own node.
I still don't know if I'll have to sell my soul to
Kim in return. :-DDD
[1] https://www.youtube.com/watch?v=ljIQo1OHkTI
I still don't know if I'll have to sell my soul to Kim in return. :-DDD
I still don't know if I'll have to sell my soul to Kim in return. :-DDD
Yes. Didn't you read the BBBS license agreement?
Compiling ansiterm.cpp
In file included from sbbs.h:315,
from ansiterm.cpp:22:
sftp.h:47:6: error: variable or field `sftp_handle_data' declared void
47 | void sftp_handle_data(sbbs_t *sbbs, char *inbuf, int len);
| ^~~~~~~~~~~~~~~~
sftp.h:47:23: error: `sbbs_t' was not declared in this scope; did you mean `sub_t'?
47 | void sftp_handle_data(sbbs_t *sbbs, char *inbuf, int len);
| ^~~~~~
| sub_t
sftp.h:47:31: error: `sbbs' was not declared in this scope
47 | void sftp_handle_data(sbbs_t *sbbs, char *inbuf, int len);
| ^~~~
sftp.h:47:37: error: expected primary-expression before `char'
47 | void sftp_handle_data(sbbs_t *sbbs, char *inbuf, int len);
| ^~~~
sftp.h:47:50: error: expected primary-expression before `int'
47 | void sftp_handle_data(sbbs_t *sbbs, char *inbuf, int len);
| ^~~
sbbs.h:471:9: error: `sftps_state_t' does not name a type
471 | sftps_state_t sftp_state = nullptr;
| ^~~~~~~~~~~~~
make: *** [/home/bbs/repo/src/sbbs3/../build/Common.gmake:546: gcc.linux.x64.obj.release-mt/ansiterm.o] Error 1
The frustration here is that I have set up a test system so I can make sure I can get a clean compile before trying this on the production system. So far, this strategy has not worked. I don't know what it is... the move from CVS to git, the move from 3.19 to 3.20, or something else... but getting a clean compile never used to be this difficult.
The code is built daily on a bunch of different platforms including multiple Linux distros, so the content in Git is good and should build. Try cloning the repo into a new directory and try again?