Take the same Knit mesh across kilometres

Every phone running Knit can send, receive and carry messages for the people around it. Your phone hands a sealed message to another Knit phone in range, that phone can hand it onward, and the message keeps moving without either person having to think about the route.

In a festival, convention, campus or busy neighbourhood, that works beautifully because the next phone may be only a few steps away. Spread the same people across a trail, a campsite or opposite sides of a valley and the missing ingredient is not the mesh. It is simply the distance between the next two phones. That is the gap LoRa can fill.

LoRa makes a very different trade from Wi-Fi and Bluetooth. It sends small amounts of data slowly, and in return a single hop can cross kilometres of open ground. Meshtastic brings that radio technology to pocket-sized, battery-powered boards through an open-source ecosystem that people have been building and exploring for years.

That reach comes with a tight bandwidth budget, so Knit treats every transmission as something worth spending carefully. The long-range link is reserved for the parts of a conversation that fit it well, while larger or less urgent traffic stays on faster paths. The result is not Wi-Fi stretched across kilometres. It is a purpose-built long hop for a mesh that already knows how to do the rest.

A Meshtastic board is not just an accessory for the person carrying it. In Knit it becomes another node on the mesh. Messages it hears over LoRa can continue outward over Bluetooth and Wi-Fi, while messages from nearby Knit phones can take the radio in the other direction.

That means a group does not need a radio for every person. Put one board with each distant group and Knit can use the long-range hop between them, then distribute the message locally the same way it always has. Everyone else keeps using the phone already in their pocket.

Knit coordinates nearby boards automatically, too. If more than one can carry the same message, they do not all waste airtime transmitting it. One takes the job while the others stand down, and another can take over if the first board disappears or runs out of power.

LoRa is at its best with small, useful pieces of information. Knit uses it for the public Nearby room and for direct messages, while heavier traffic stays on Bluetooth, Wi-Fi or an optional Internet relay.

Send a direct message with a photo and Knit can treat the two parts independently. The words can arrive over LoRa first, with the image waiting until a faster path becomes available. The conversation reaches you as soon as it can, and the attachment fills itself in later.

Group chats stay on the phone mesh or an optional relay rather than using LoRa. Knit makes that boundary visible in the conversation, so there is no guessing about which path a message can take.

Sending a direct message over LoRa does not create a weaker version of that message. Knit sends the same sealed, signed frame it would have handed to another phone, and the recipient opens it the same way. The radio changes the route, not the protection around the message.

Like other shared radio systems, LoRa still needs information outside that sealed message so radios can discover one another and move traffic. The message body stays unreadable, but the sender and recipient addressing, timing and approximate size do not. On a long-range radio, that metadata can be visible from much farther away than it would be over Bluetooth.

Knit puts that choice in your hands. Direct messages over LoRa can be disabled from the radio screen while the board continues carrying the public Nearby room. You get the extra reach when it fits your threat model, without having to give up the rest of the integration.

Connecting a board is designed to feel much more like pairing an accessory than configuring a radio network. Knit creates its own channel in the first available slot, reduces routine position and telemetry broadcasts to conserve battery and airtime, and marks the node as unmonitored so other Meshtastic users are not invited to message something that is not acting as a normal chat client.

Knit also remembers what it changed. Restore puts those settings back the way it found them, including the board's name.

The board's primary Meshtastic channel stays untouched. That keeps it connected to the Meshtastic network already around you, where compatible nodes can help repeat traffic. Knit joins that shared ecosystem as a careful guest, gaining range from the mesh while deliberately limiting how much airtime it consumes.

Pairing a board also brings its primary Meshtastic channel into Knit. You can see the radio mesh around you and post to it without switching between apps.

That channel is intentionally separate from Knit's private messaging system. A stock Meshtastic channel uses a publicly known key, while a channel configured with a custom key is shared by every radio that knows it. Neither is the same thing as a Knit direct message that only its sender and recipient can open, so Knit presents the Meshtastic room without a private-chat padlock.

On that channel, the radio itself is the identity. Knit can associate a post with a contact using the radio's number, but treats that match as unverified because a number alone is only a claim. With firmware 2.8 and newer, a valid radio signature can be checked against the key stored in a Knit profile and turn that match into a verified one.

The room remains local to Meshtastic. Its posts do not enter Knit's mesh and Knit does not send them to the Internet. If that channel is not useful to you, a switch removes it from your chat list and stops your phone processing its messages.