About ATXbbs

The story of the software, the BBS that came back, and why this exists.

The lineage

ATXbbs descends from two pieces of conferencing software that defined an era of online community:

• PicoSpan (Marcus D. Watts, ~1985) — the conferencing system that ran The WELL from Sausalito, California. The first system to formalize the model of conference → topic → response instead of flat threads. Built for terminal access; web came later.
• Yapp (Armidale Software, 1990s) — literally "Yet Another PicoSpan-like Program." Web-first. Ran spring.com / spring.net in Austin, Texas from 1996 to 2014, plus dozens of other community BBSes.

ATXbbs is the third generation. PicoSpan in 1985 → Yapp in the 1990s → ATXbbs in 2026. Each one made the older idea easier to deploy and slightly more web-native, while preserving the core model: conferences hosted by volunteers, made up of topics that accumulate threaded responses.

Why this exists

In April 2026, Paul Walhus — who had run spring.com in Austin from 1996 until 2014 — decided to find out if his old BBS still existed anywhere. The answer, like most internet history questions, was: partially, in the Wayback Machine.

Roughly 4,000 archived thread URLs across spring.com and spring.net had been captured at one time or another between 1996 and late 2013. About 2,900 of them returned full content when fetched. The other 1,100 were partial, broken images, or 404s.

Resurrecting them as a readable archive was relatively straightforward. The harder question was: can we make people post on top of the archive again? Could a 1998 Colin Firth thread that ran 14,000 replies long pick up new replies from people who'd posted in it as twenty-year-olds, now in their mid-fifties?

That second question is what ATXbbs exists to answer. Yapp's archive without the live commenting layer is just a museum. The live layer is what turns it back into a community.

Design principles

• Use the language the cohort speaks. Conference, topic, response. Not channel, thread, post. The original 1,000+ members of spring.com remember those words.
• The killer feature is "what's new since I last looked." Every other feature is secondary. Without that one, the BBS feels like a graveyard.
• No email required. Yapp required email; we don't. Handle + password. Email is opt-in for password reset and reply notifications.
• No algorithm. Time-ordered or explicit filters only. No "for you." No engagement-maximizing reordering. The "Last 333 across all conferences" pulse view from yapp is a perfectly fine homepage.
• Soft delete, never hard delete. Moderation hides; data persists. Audit trail by design.
• Cross-link with reference sites. A discussion forum is more useful when it's connected to the things people are discussing. Drool ↔ firth.com. Austen ↔ austen.com. tv ↔ tvreviewer.com.
• Static where possible, Flask where required. 95% of pages served by nginx as plain HTML. CDN-ready. Graceful degradation.
• Cheap to run. The whole reference deployment lives on a $6/month droplet. No managed databases, no SaaS dependencies beyond Resend (free tier) and Backblaze B2 (free tier).

Who's behind it

ATXbbs is built by Paul Terry Walhus (@springnet) in collaboration with Claude Code (Anthropic).

Paul started the original Spring BBS as a Unix command-line system in 1996 in Austin, Texas. It grew to over 1,000 members across 85+ conferences and ran continuously until 2014, when the spring.net domain was sold and the BBS went dark. Paul became "the original King of Twitter" at SXSW 2007 (per a BuzzFeed profile), and the handle @springnet is named after this BBS.

ATXbbs the software is the third act. PicoSpan was the first. Yapp was the second. This one is meant to outlast them both.

Other community / forum software in the lineage

If you're researching this space:

• PicoSpan — CASE/Marcus D. Watts, ~1985. The WELL. (still running on its successor)
• Caucus — Charles Roth at University of Wisconsin, 1980s. Inspired PicoSpan.
• Yapp — Armidale Software, 1990s. Spring, others.
• Discus — Karen Strom, 1996. Education-focused.
• WebX — Open Text, 1996. Enterprise-focused.
• vBulletin / phpBB / SMF — the 2000s wave. Big, themeable, plugin-rich, complex.
• Discourse — Jeff Atwood et al., 2013. Modern, JS-heavy, enterprise SSO.
• Mastodon, Bluesky, Discord, Slack, Reddit — not BBSes, but the things community gravitated to once BBSes faded.

ATXbbs occupies a deliberately small niche: simple, single-sysop, archive-first, no-algorithm, no-email-required, runs on a $6/month box. If your needs are larger, Discourse is a better fit. If your needs are smaller, you don't need a BBS at all.

Source

Source release is planned for v0.5, after the API surface stabilizes and after the May 1, 2026 official launch of the reference deployment.

If you want to run your own ATXbbs now — for example, to revive a different defunct BBS from Wayback — email terry@atxbbs.com and we'll work with you directly.

Contact