= Сообщение: 4264 из 7124 ====================================== FTSC_PUBLIC = От : Ozz Nixon 1:275/362 15 Feb 19 10:22:12 Кому : Sean Dennis 15 Feb 19 10:22:12 Тема : Campaigning... FGHI : area://FTSC_PUBLIC?msgid=1:275/362+5c66ea22 На : area://FTSC_PUBLIC?msgid=1:18/200.0+5c65f858 = Кодировка сообщения определена как: CP437 ================================== ============================================================================== Hello Sean.
14 Feb 19 18:23, you wrote to me:
SD> -=> Ozz Nixon wrote to Carol Shenkenberger <=-
SD> I'm not trying to pooh-pooh anything you've done (and it's impressive SD> to me the amount of stuff you've done, TBH). I'm just trying to see SD> where everyone is going with the FTSC.
Everything is being done in bby foot steps - if I can gt it working smoothly over 9600bps - then those cities that have mbps or even gbps services for home users will obviously be able to enjoy. I only have the dial-up system here so I can retrofit back to FroDo... I am a partner in a WiSP in Kentucky, where highspeed is not available yet - but through wide area WiFi - we a able to provide service to people (places "VERIZON" does not even cover)... there are many *markets* dial-up is still viable.
However, everything I am developing is also being forward compatible with my cross platform compilers - so I can do it over TCP, RTCP, etc. I worked so much on the JAMAPI for example, as I want it to be the backend for my FMTP (Unproposed FIDONET MESSAGE TRANSPORT PROTOCOL) ... to get buy-in of course, I am rewriting JAMNNTPd - so I can stress test my code. As FMTP servers would work like SMTP - echoing from Regional Hub to Regional Hub, Country to Country. BBSes could elect to stream "On Demand" per user, or "Fetch/Post" like we currently do. The Server code easily handles 50,000 concurrent connections - so in the long run, operating a BBS would be more of the focus on "Look and Features", Messaging would become centralized on a FMTP network. If JAMAPI does not work out, then I own a SQL Database company, and I can leverage that tech and equipment as the backend... but, I am trying to keep it in a technology I feel is more appropriate.
FMTP works like NNTP for client Fetch/Post, and more like POP4 for On Demand.
I have already started a plugin for PHPBB, so it looks like the threads are on the web server, however, the output is coming from my Arizona FMTP Server in PHPBB HTML. But, I am months out until these go outside my testers. We are still focused on JAMNNTPd rewrite right now... ;-)
SCALE GOAL: Raspberry Pi Zero with FULL Backbone. As close to zero diskspace as possible. (With or Without DOSEMU).
Ozz
--- FMail-W32 2.0.1.4 * Origin: Richmond VA (RVA) Fidonet Support (1:275/362)
