BBS: TELESC.NET.BR Assunto: Re: getting and keeping n De: Jas Hud Data: Fri, 23 Jan 2026 20:43:15 -0600 ----------------------------------------------------------- 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) ----------------------------------------------------------- [Voltar]