// the find
TheCommsChannel/TC2-BBS-mesh
A BBS server for Meshtastic for posting bulletins, sending mail to users, and channel directory.
A BBS server that runs on top of a Meshtastic radio node, letting people exchange mail, post bulletins, and browse a channel directory over LoRa mesh with no internet involved. Built for the ham radio / off-grid mesh crowd, typically deployed on a Raspberry Pi hanging off a Meshtastic device over serial or TCP.
Node-to-node sync (`bbs_nodes` in config) lets multiple BBS instances federate mail and bulletins across a mesh, which is the actually hard part of this problem and it's handled rather than punted. Ships both a systemd unit file and a Docker Hub image, so it covers the two deployment paths its actual users have: a Pi running headless, or someone who just wants a container. Interface layer abstracts serial vs TCP connections to the radio, so it isn't hardcoded to one Meshtastic hardware setup.
No test suite or CI anywhere in the tree — for software mediating message delivery over an unreliable radio link, that's exactly the kind of thing you want regression coverage on. The README itself flags an open, unresolved problem: some device roles stop responding to requests after running for a while, with no root cause given, which means you adopt a known-flaky baseline and have to debug mesh issues yourself. Everything is driven off a single INI file and the architecture is a handful of flat modules (command_handlers.py, message_processing.py) rather than any documented structure, so there's no real guide for extending it beyond reading the source directly.