A bulletin board is a machine that answers a phone number. Somebody put a spare computer in a spare room, hung a modem off it, and other people called it. No terms of service. No algorithm deciding what you saw. No third party keeping a copy for later. The sysop was a person you could ring up and argue with, and if you did not like how a board was run you started your own, because the barrier to entry was a second phone line.
Where this came from
CBBS went online in Chicago on 16 February 1978, written by Ward Christensen with hardware by Randy Suess. The January blizzard that shut the city down handed them the quiet weeks to finish it. It ran on an S-100 machine with 64 kilobytes of memory and answered one caller at a time.
Thousands of boards followed. Each one was somebody's own idea of what a community should look like: a music board, a board for one town, a board that was really just its sysop and eleven friends. At the peak in the mid-1990s an estimated 60,000 were running in the United States alone, and FidoNet tied tens of thousands of them into a store-and-forward network that moved mail around the world overnight, for free, run entirely by hobbyists.
Almost all of them ran on hardware weaker than the five dollar chip this software runs on.
What replaced it
The web arrived and it was better at almost everything, and then it consolidated. Now the conversation lives on machines you cannot see, indexed, scraped to train something, ranked, monetised, and deleted at somebody else's discretion. You do not own the room, the member list, the history, or the right to keep any of it. You rent all of it, and the rent is paid in attention and data.
The thing that was lost was not the modem noise. It was that the system belonged to somebody you could name.
What this is
A telnet BBS that runs on a bare ESP32, a microcontroller the size of a postage stamp, and grows into an IoT terminal server through plugins. Nodes, handles, a user list, a chat room in the style of DDial and Gtalk, messages, doors, a caller log, a sysop who can page you.
The board is yours. Not an account on somebody's platform, not a tenant on a server farm, not a feature that can be deprecated out from under you. A chip you own, on a port you chose, running software you can read all of in an afternoon and change when you disagree with it. Switch it off and it is off. Leave it in a drawer for a year, plug it back in, and it still works, because there is nothing at the other end that has to still exist.
The user list is a text file. The settings are a text file. A message goes from one caller to another through a chip on your shelf and is gone the moment it is read. There is no account to create, nothing to subscribe to, and no vendor who can change the deal. It is GPL, so nobody can take it away from you later, including the person who wrote it.
Privacy forward, and what that actually means
Every system you use was built by somebody, and the question worth asking is who it was built to serve. A board is built to serve the person who owns it. That is the whole of the privacy argument, and everything else follows from it.
There is no third party in the middle. Not a company, not a platform, not an advertiser, not a model being trained. A message goes from one caller to another through a chip on somebody's shelf and it is gone when it is read. Nobody is standing between those two people taking a copy, because there is nowhere for a copy to go and nobody whose business it would be.
Here is the difference, drawn out.
CALLING A WEBSITE
you --> DNS --> CDN --> load balancer --> the app
| | | |
v v v v
who asked edge logs session account
and when your IP fingerprint history
| | | |
+---------+------+------+-----------------+
|
v
analytics . ad exchange . data broker
model training . retention policy
breach disclosure in eighteen months
|
v
you cannot audit any of it
CALLING A BOARD
you --> your router --> a chip you own
|
v
a text file you
can open and read
that is the entire list
The left-hand column is not a conspiracy. Every box on it exists for a reason somebody could defend, and most of them were added by decent engineers solving a real problem. It is simply what a modern service is made of, and the effect of all those reasonable decisions together is that you cannot say who holds what about you, or for how long, or what it will be used for next year.
The right-hand column has no boxes to add. There is no account system to breach, no analytics to leak, no retention policy to change, no company to be acquired by somebody with different ideas. What is not built cannot be exploited, and what was never collected cannot be handed over.
The power is in your hands, literally
You flash the firmware. You set the password. You decide who gets a handle, what the board is called, what the rules are, and whether it is on the internet at all. You can read every line of the software before you trust it, and change the parts you disagree with, and nobody can stop you, because the licence says so and the source is right there.
If you switch it off, it is off. Nobody else gets a say in that.
Turn the board off and the service ends. Not "your account is deactivated but we retain your data for legitimate business purposes" — ends. Pull the plug and the chip stops answering. Wipe the flash and the user list is gone. That is what owning something means, and it is startling how unusual it has become.
Honest about the limits
Telnet is plain text, because a Commodore 64 cannot do TLS and pretending otherwise would be worse than saying so. This keeps a board off the public internet's record; it does not keep it off the wire. If a conversation has to survive somebody watching the link, put the board behind a VPN or leave it on the local network. Privacy you can explain in one sentence beats privacy you have to take on faith.
Small on purpose
One static binary. Static allocation, no heap in the main loop, a fixed memory budget on a chip with 520 KB of RAM. No web stack, no scripting runtime, no package tree to audit at two in the morning, no telemetry, no update that arrives without you. What is not built cannot be exploited, and what fits in one head can be trusted by the person whose head it fits in.
Serial did not die
RS-232 was standardised by the EIA in 1960 and still runs the console and management ports on network equipment, industrial controllers and test gear, and its asynchronous framing survives on nearly every microcontroller made since as a TTL-level UART. Sixty-five years on, the way a machine from 1982 talks is still the way you talk to the switch in the rack. That is why a Commodore 64 and a laptop bought this year can both call one of these boards, and why a board can turn round and drive whatever is hanging off its own serial port.
Why the micro sign
Because it runs on a microcontroller, and because microcomputers are what put
computing into the hands of people who were never going to be given time on a
mainframe. The Altair 8800 in
1975, then the Apple II, the Commodore PET and the TRS-80 in
1977,
took the computer out of the raised-floor room that somebody else controlled and put it
on a kitchen table. This is the same move, one more time, on a chip you can lose in a
drawer. Where the symbol cannot be shown, it is written unleashed.
You can do this today
Not as a re-enactment: as a live system with callers on it tonight. Flash a board, give it your wifi, forward one port on your router, and you are running a public BBS. No hosting bill, no domain required, no provider to ask permission from, no account with anybody. A chip on a shelf and one line in your router.
The source, the documentation and the build instructions are here. It is free software under the GNU General Public License, version 2 or later.