TZUTC: -0600
MSGID: 1437.fidonet_bbscarni@1:3634/27 2dd970d9
REPLY: 5599.carnival@1:2320/105 2dd8da9c
PID: Synchronet 3.19b-Win32 master/a2a9dc027 Jan  2 2022 MSC 1928
TID: SBBSecho 3.11-Win32 r3.177 Sep 20 2020 MSC 1927
CHRS: ASCII 1
  To: Dumas Walker
  Re: Re: getting and keeping n
  By: Dumas Walker to ALEXANDER GROTEWOHL on Fri Jan 23 2026 10:07 am

 > > respond:

 > > you sound like a big baby

 > To be accurate, it sounds like ChatGPT was the one being a big baby.
 > ;)


yeah but he fed chatgpt a leading question.
so he was still behind the wheel.

i asked grok a non retarded non leading question and got a good result.

i asked "why aren't new people getting involved in bbs softwares. I mean 
bulletin board softwares that used to be old but are still being developed 
for the internet"



Bulletin Board Systems (BBS) originated in the late 1970s as dial-up services 
for messaging, file sharing, and games, but they largely faded in the 1990s 
as the internet rose. While some modern adaptations exist (e.g., telnet-based 
systems like Synchronet or Mystic BBS, or hybrids blending retro aesthetics 
with web tech), involvement from new developers and users remains low. Based 
on discussions in online communities and historical analyses, here are the 
key reasons:


1. Shift to Modern Alternatives
BBS functionality has been superseded by more accessible platforms like 
Reddit, Discord, forums (e.g., phpBB), and social media. These offer similar 
features- threaded discussions, media sharing, and communities-but with 
better scalability, multimedia support, and no need for specialized clients 
or dial-up/telnet. Historical accounts note that BBS declined sharply in the 
mid-1990s due to services like AOL and CompuServe, which supported more 
simultaneous users without hardware limits. Today, why build on BBS when 
tools like Discourse or even Mastodon provide modern, open-source 
equivalents?


2. Niche and Nostalgic Appeal
Modern BBS development often caters to retro enthusiasts rather than broad 
audiences. Communities like r/bbs on Reddit highlight that much of the 
interest comes from veterans reminiscing about the 80s/90s era, with 
questions about why software hasn't "evolved" to include modern graphics or 
sounds. New people aren't drawn in because it's seen as a hobbyist relic, not 
a cutting-edge field. For instance, ongoing projects like new hybrid BBS 
software blend old and new tech, but they're shared in small Facebook groups 
for "BBS fans," limiting exposure.


3. Technical and Accessibility Barriers
BBS software typically relies on outdated protocols (e.g., telnet, ANSI art) 
that don't integrate well with current web standards or mobile devices. 
Developers note compatibility issues, like finding telnet clients that handle 
PC-ANSI properly on modern hardware. New coders prefer stacks like 
JavaScript, React, or cloud services, which are more employable and easier to 
learn. Older BBS codebases (e.g., MajorBBS or Worldgroup) are often treated 
as abandonware, with calls to open-source them unmet, deterring 
contributions.


4. Lack of Visibility and Education
BBS isn't part of mainstream tech education or hype cycles. Younger 
developers focus on AI, web3, or app dev, where jobs and funding abound. 
Forums like phpBB, a spiritual successor to BBS, are perceived as "dead" by 
former contributors due to inactivity and lack of fresh involvement. Without 
marketing or viral appeal, new talent doesn't discover it-contrast this with 
how GitHub trends boost projects in other areas.


5. Community and Economic Factors
The ecosystem is small and aging, with sysops (system operators) retiring and 
few replacements. Atari or Macintosh BBS threads show evolution stalled 
decades ago, tied to specific hardware. There's little economic incentive; 
BBS isn't monetizable like SaaS tools. Broader software dev trends, like 
resistance to outdated practices or focus on maintenance over innovation, 
compound this.
That said, pockets of activity persist-e.g., new multi-platform BBS projects 
in 2026 still pop up in niche groups. If you're interested in getting 
involved, check communities like r/bbs or BBS-focused Facebook groups for 
entry points.

--snip--

you notice it gave good feedback instead of blaming people for creating a 
'learning curve' by responses.   also if people want to know how to set 
things up they can read the docs.  i can count on one hand how many times 
i've had to ask for help in 26 years with synchronet.
--- SBBSecho 3.11-Win32
 * Origin: *The Gate BBS*Shelby, NC USA*thegateb.synchro.net* (1:3634/27)
SEEN-BY: 1/120 18/0 200 103/705 104/119 105/81 106/201 114/10 116/116
SEEN-BY: 120/302 616 123/0 25 126 180 525 755 3001 3002 4040 124/5016
SEEN-BY: 128/187 129/14 305 135/115 153/757 7715 154/10 30 50 700
SEEN-BY: 203/0 218/700 220/20 90 221/0 6 222/2 226/18 30 44 50 227/114
SEEN-BY: 229/110 112 134 206 300 310 317 400 426 428 470 664 700 705
SEEN-BY: 240/1120 5832 250/1 263/1 266/512 275/1000 280/464 5003 5006
SEEN-BY: 291/111 292/8125 301/1 320/219 322/757 341/66 234 342/200
SEEN-BY: 396/45 423/120 460/58 256 1124 633/280 712/848 1321 770/1
SEEN-BY: 902/26 2320/105 3634/0 12 24 27 57 58 60 61 119 5020/400
SEEN-BY: 5020/8912 5054/30 5075/35
PATH: 3634/27 12 154/10 280/464 460/58 229/426