Is this as good as it gets for 2019 and beyond?
Is this as good as it gets for 2019 and beyond?
Hello All!
Except for maybe some improvements to a couple of BBS programs
(Synchronet, Mystic..), and couple of nntp or fidonet "apps" for mobile devices in the recent years, has there been anything else new to fidonet technology?
BinkD as been around for atleast 20 years.
Jamnntp looks like the most recent contribution (2013?, but I spotted a listing in Jul 17, 2004 for jamnntpd-0.6)
Is this as good as it gets for 2019 and beyond?
Hello All!
Except for maybe some improvements to a couple of BBS programs (Synchronet, Mystic..), and couple of nntp or fidonet "apps" for mobile devices in the recent years, has there been anything else new to fidonet technology?
Not in the underlying FTN technology, no.
BinkD as been around for atleast 20 years.
It is a staple today (the binkp protocol). It's all I use today when connecting with other nodes.
Jamnntp looks like the most recent contribution (2013?, but I spotted a listing in Jul 17, 2004 for jamnntpd-0.6)
Is this as good as it gets for 2019 and beyond?
The sky is the limit. All the stuff we have today is there because somebody, or a group of people did it. I see no reason not to carry on with what we have and also what new ideas people bring in.
I added networked voting support to Synchronet a couple of years ago (message up/down voting and polls), but only for QWK networking. I've been asked about adding support to SBBSecho (for FTNs) but without any other FTN software authors engaged, it wouldn't really be of any use. I inquried about any interest in FTSC_PUBLIC I think it was, and got no responses.
So perhaps the active developers just didn't see the inquiry or there's just not any interest at least in that particular feature. Or there are no other active FTN software developers (!). :-)
I added networked voting support to Synchronet a couple of years ago (message up/down voting and polls), but only for QWK networking. I've been asked about adding support to SBBSecho (for FTNs) but without any other FTN software authors engaged, it wouldn't really be of any use. I inquried about any interest in FTSC_PUBLIC I think it was, and got no responses.
I remember reading your post in FTSC_PUBLIC.
I wonder if you went ahead and
implemented that in SBBSecho and published the details in the wiki if it would be implemented in other software?
I know that wiki.synchro.net is well know as a source of FTN and BBS info.
So perhaps the active developers just didn't see the inquiry or there's just not any interest at least in that particular feature. Or there are no other active FTN software developers (!). :-)
I think a lot of FTN/BBS developers worry about compatibility issues (a real concern) so might like the idea but worry about things like that.
If you could come up with a "standard" of some sort it might just catch on. :)
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,029 |
Nodes: | 17 (1 / 16) |
Uptime: | 134:00:35 |
Calls: | 503,659 |
Calls today: | 9 |
Files: | 155,706 |
D/L today: |
14,763 files (14,174M bytes) |
Messages: | 443,626 |
Posted today: | 1 |