GUVWAF

I'm sorry but I don't get why that is better than using the last byte, which is 0..255. It's not a checksum, it's to uniquely identify a node. If the...

Version 3.0 will most likely have a different default modem preset (people have advocated for MediumFast) or another sync word to deliberately make nodes incompatible. I'm not really sure half-working...

Ofcourse the decision will not be taken lightly and people have been saying it will be happing at least a year from now. I'm not entirely following why you're advocating...

> This is one of the biggest issues I have with the proposal: it uses up all the unused bits for its purposes and doesn't fix the versioning issue which...

> Where are such far-reaching decisions discussed and decided? This was discussed by admins on Discord, but is also just an idea right now. When 3.0 comes closer, there will...

After looking at this again, I realized I made a big assumption that’s likely often not valid. I set the `next_hop` of a node to the one that was forwarding...

For your information: I2C support has been added to a fork of this project here: https://github.com/meshtastic/framework-portduino

@geeksville PR submitted. All credits for I2C support go to @jp-bennett BTW. He got Meshtastic running on a Raspberry Pi with LoRa hat and some I2C screens :)

This is the other way around: packets from MQTT (downlink) can be controlled to not be transmitted over LoRa. Just like the public MQTT server is currently doing with zero-hopping,...

> We've had reports from Germany by people being confused about MQTT not working after they enabled it, because on duty cycle limited regions config.lora.ignore_mqtt defaults to OFF already. With...