The Teletype BBS: A Serial Fiction Network

The Teletype BBS is a project to resurrect the Bulletin Board System (BBS) as a platform for serialized fiction, harking back to the days of dial-up, ANSI art, and intimate online communities. The system runs on a Raspberry Pi and is accessible via telnet or a web-based terminal emulator. It hosts multiple ongoing serial stories, each released chapter by chapter on a schedule. Users can read, comment, vote on plot directions, and even submit their own chapters for consideration. The entire experience is text-only—no images, no JavaScript, no algorithms—just words and ASCII art. The BBS aims to recreate the anticipation of waiting for the next installment, the camaraderie of a small readership, and the discipline of writing against a serialized structure. It's a deliberate counter to the fast-scrolling, fleeting nature of modern online fiction platforms.

Modern serialized fiction platforms like Wattpad or Medium are optimized for speed and virality, encouraging rapid consumption and algorithmic curation. There's little sense of ritual or community. Readers scroll past without engaging deeply, and writers are pressured to produce content that games the algorithm. The Teletype BBS scratches the itch for a slower, more intentional reading and writing experience. By reviving the BBS, it forces users to connect via a terminal, wait for chapters to arrive on schedule, and interact in a text-based, non-distracting environment. It's a deliberate retreat from the noise of the modern web.

• Launch a functional BBS server with telnet and web-terminal access.
• Host at least three active serial stories within the first three months.
• Achieve 100 regular users within six months.
• Implement a voting system allowing readers to influence story directions.
• Host weekly live writing events where authors write chapters in real-time while readers watch via telnet.
• Compile and publish a printed anthology of the best serials after one year.

• No mobile app or responsive design; the experience is desktop-terminal only.
• No social media integration or sharing features; the BBS is a walled garden.
• No monetary transactions; all content is free and the project is non-commercial.
• No graphical interface beyond ANSI art; no images, CSS, or modern web design.
• No algorithmic feeds; content is strictly chronological and selected by human curators.

• Backend: Python 3 with Twisted for the telnet server, SQLite for data storage.
• Frontend: Native telnet client, plus a web-based terminal emulator (xterm.js) for browser access.
• Hardware: Raspberry Pi 4 (or any Linux server) with a static IP.
• ANSI Art: Pyte library for terminal emulation, AAlib for ASCII art conversion, and manual ANSI art creation.
• Scripts: Python scripts for chapter scheduling, voting tallying, and user management.
• Communication: SSH for maintenance, no email integration.

The BBS runs as a Twisted Python server listening on port 23 (telnet) and an alternative port for web-terminal proxy. Upon connection, the user sees an ANSI welcome screen and a main menu with options: Read Stories, Message Boards, Voting Booth, Submit Chapter, and User Settings. Stories are stored as directories with chapter files in plain text or Markdown. A scheduled cron job releases new chapters at set intervals (e.g., weekly). Comments are stored in a simple board-style database table. Voting is handled via polls tied to each story; users can vote once per poll, and results are displayed as ASCII bar charts. Live writing events use a shared terminal session where the author types in real-time, and readers see keystrokes as they happen (mimicking a teletype). The system is intentionally minimal—no encryption, no fancy features—to keep the retro feel.

• Low adoption: The barrier of using telnet or a terminal may scare away casual users.
• Security: A telnet server with no encryption is vulnerable to eavesdropping; users' passwords and content could be intercepted.
• Moderation: Without automated filters, spam or offensive content could proliferate.
• Scalability: The single-threaded Twisted server might have issues with many simultaneous connections.
• Content quality: Relying on community submissions may result in inconsistent quality.

• Should we implement TLS for telnet (Telnets) to improve security, or maintain pure retro nostalgia?
• How to handle user authentication: plain-text passwords stored in DB, or a simple hash?
• What format for chapter files: pure .txt or Markdown (which can be rendered as ANSI)?
• Should voting be public or anonymous?
• How to prevent vote manipulation by multiple accounts?
• Should we allow anonymous reading or require registration?
• What moderation policies? Human or automated?

The project got prototyped on a Raspberry Pi and even attracted a handful of test users, but life intervened—new job, move, and the realization that the niche was too small to sustain long-term enthusiasm. The code still sits on GitHub, and the dream of a slow-fiction network remains a cherished what-if.

This project is not meant to be a commercial venture or a nostalgic replica of old BBSes, but a functional platform that leverages the constraints of text-only, scheduled releases, and community interaction to create a unique writing and reading experience. The ANSI art and terminal interface are essential to the aesthetic; the absence of images forces focus on the words themselves.