Where zBRETT fits —
and where it doesn't.
zBRETT gets put in boxes it doesn't belong in: prepper radio, yet another Meshtastic, a poor man's forum. Here's the honest placement — next to the things it's confused with. In short: zBRETT competes with none of them. It's a layer of its own.
The stance: an everyday network, not an emergency one
A network that only runs in a disaster is broken in a disaster.
Because no one knows it, maintains it, or has practised with it. zBRETT is deliberately something for everyday use that doesn't fail in an emergency. That's the ordering every placement follows from: zBRETT isn't the tool you unpack when things go wrong — it's the layer already running, with people on it, when the grid goes down.
Side by side, not against each other
The same question — "reach people without the internet" — gets four very different answers. zBRETT occupies a gap the others leave open.
| zBRETT | Amateur radio / EmComm | Meshtastic | Internet forum | |
|---|---|---|---|---|
| Licence | none (ISM 868 MHz) | amateur radio licence | none (ISM) | none |
| Range | city / neighbourhood | regional–global (HF) | local / mesh | global (needs the net) |
| Structure | threaded boards | mail / live chat | flat channels | threaded, but net-dependent |
| Operating model | everyday network, 24/7 | deploy in emergency | everyday / hobby | everyday, centralised |
| Infrastructure | none central (solar hubs) | operator + antenna | none central | server / data centre |
Next to amateur radio & EmComm
Winlink, JS8Call, VARA, SDR on a rugged tablet, plus the whole of Wikipedia offline — a strong grid-down stack. zBRETT replaces none of it; it adds the layer that's structurally missing.
That stack is the long-haul link and the reference library: Winlink is email over radio (point-to-point, gateways to the world), JS8Call is weak-signal keyboard radio over great distances, Kiwix the offline knowledge. Strong — but licensed, operator-intensive, and it sits in a pouch until you need it.
zBRETT is licence-free (868 MHz ISM — no callsign, no exam), local and threaded: the neighbourhood bulletin board that lets many talk to many, persistent and sorted by topic. Your neighbour with a pocket device and a phone is in — she can't operate the Winlink stack.
A rugged x86 Windows machine is an ideal zBRETT host. Reticulum/Sideband run on Windows; an RNode (nRF52840 + SX1262) over USB/BLE makes the same machine a zBRETT node alongside Winlink and JS8Call. Own such a device? You're exactly the field tester we're looking for.
Next to Meshtastic
Related hardware, different firmware, different goal. Meshtastic provides the transport — zBRETT brings the semantics Meshtastic lacks.
Meshtastic can do radio, but its channels are flat: no threading, no message IDs, no history, no subscriptions. zBRETT brings back exactly what the German mailbox networks had solved from 1986 on: globally unique IDs, reference chains (threads), duplicate detection, selective subscriptions and a per-board policy.
Technically crucial: zBRETT uses Reticulum, not Meshtastic. "Meshtastic-compatible" hardware therefore says nothing about zBRETT suitability — what matters is RNode/Reticulum firmware. Details in the architecture.
Next to the internet forum
No replacement. If you have the internet, you have it better — this is something else.
zBRETT is Usenet semantics with SMS economics: a thread is a tree of 140-character nodes, the reader renders it as a discussion. The forced brevity isn't a shortcoming but a feature — it eliminates full quotes and enforces one thought per post.
So it's not a worse forum, it's a different species: one that needs no data centre, no central server, and has no off-switch to pull.
To keep the placement honest
zBRETT is text-only, local, slow and at the MVP/concept stage. It's not a drop-in tool you put into service solo today. Its strength — the everyday network — assumes hubs are up around the city and people take part. That has to be built first. It's the missing social layer you raise in the field, not one you buy.