███████╗ ██████╗ ██████╗ ██╗ ███████╗████████╗ ██╔════╝██╔═══██╗██╔════╝ ██║ ██╔════╝╚══██╔══╝ █████╗ ██║ ██║██║ ███╗██║ █████╗ ██║ ██╔══╝ ██║ ██║██║ ██║██║ ██╔══╝ ██║ ██║ ╚██████╔╝╚██████╔╝███████╗███████╗ ██║ ╚═╝ ╚═════╝ ╚═════╝ ╚══════╝╚══════╝ ╚═╝
foglet is a small, self-hostable bulletin board served over ssh. the web is only the porch light. the place itself is inside your terminal.
── try the public beta ── $ ssh bbs.foglet.io # bring a handle, a password, or later: the key your ssh-agent already knows
── elixir/otp · postgres · phoenix as infrastructure · terminal ui over ssh
one elixir application. one postgres database. one ssh daemon. a bbs with boards, threads, posts, board chat, door games, short public notes, and a sysop who can keep the lamps lit.
categories, boards, threads, replies, edits, soft deletion, read pointers, subscriptions, and stable per-board message numbers.
the main product surface is the terminal UI served over ssh. a new login promotes the new connection and closes the older one.
registration, login, verification, password reset, profile settings, preferences, and public-key management live inside the tui.
short public notes for the front-room feeling: a quick signal that someone else was here, recently, and left a mark.
live chat rooms sit beside boards when a sysop enables them. talk in the same small room as the threads, with ephemeral or kept history.
modern in-beam doors and external pty doors can live next to classic dropfile games, with launch rules and audit records under sysop control.
operator surfaces for users, boards, site settings, limits, invites, moderation snapshots, and break-glass mix tasks.
phoenix runs the landing page, health check, telemetry, pubsub, and operational pieces. it is not a browser forum.
── the key you already use, pointed at a small bbs.
foglet users can add ssh public keys to their accounts from inside the terminal ui. after setup, the next login can use public-key auth instead of another password prompt.
keys can be labeled and removed, so a retired laptop does not become folklore. take the key off the account; keep the account.
bbs login should feel like opening a familiar shell, not entering a growth funnel. ssh keys let the operating system do what it is already good at: prove that this machine is allowed through.
the password is still there for setup and fallback. the key is the better ritual once the place knows you.
── after a key is on file ── $ ssh bbs.foglet.io Authenticated using "publickey". ╔══════════════════════════════════════════════════════╗ ║ welcome back. ║ ║ the fog remembers this key. ║ ╚══════════════════════════════════════════════════════╝ foglet> _█
foglet uses modern tools in service of an old-network feeling: slower, smaller, less extractive, and meant to be run by a person.
:ssh daemon under the app supervision tree
foglet is beta software. the public instance is an invitation, not a promise that every corridor is finished.
$ ssh bbs.foglet.io
── foglet · a small bbs you reach over ssh · nothing here is for sale ──