Bitchat – A decentralized messaging app that works over Bluetooth mesh networks

If I were an Android developer, though, I'd just use the Swift files as a requirements spec, and write it native.

It's an Arduino library for mesh networking, that works over BLE and UDP, but it can also link to MQTT.

An MQTT node routes the packets it sees to the appropriate topics, and subscribes to topics for all the channels local nodes want, so you should be able to talk to anyone anywhere via the gateway.

The packet destination addresses are rolling codes, so you can't tell if someone's online just by watching their channel, at least not for more than an hour.

And there's a web app that talks directly to the public MQTT broker, and it can do chat and sensor data.

All payloads are Messagepack to make it easy to add new data types, and all packets are encrypted, authenticated, and timestamped to provide a bit of replay protection.

Everything is purely symmetric crypto, trust is left to a higher layer or something out of band, so you there's no handshakes or connection state management overhead, aside from one announce packet per hour to make the MQTT gateways work.

No LoRa, but the transports are modular and pluggable so you can easily add them. I just only have one LoRa Arduino node here so I haven't bothered writing a driver.

I'm also working on a Python port for easy pip-installable bots and home automation stuff.

https://github.com/EternityForest/LazyMesh#

the spitball questions I would ask might be, a) how do you handle a theoretical timing attack where the time to respond to a room scan could yield whether a given device is a member of a known room, (the paralellism?) and b) does the GCM counter IV/nonce value cluster around rooms, so the counter for a given room will be in a shared range?

not dealbreakers or anything, this is simple and cool for its purpose, but design consideration wise, what's the thinking on those scenarios?