Ben Meadors

> Assuming we choose to move forward with code refactoring into /lib, there would take a non-negligible amount of required work before any unit tests could be written. This being...

That's after my latest change to add the telemetry packets into the "sendToPhone" logic, like we did for position? That one was at @andrekir's request. I'm wondering if it's behaving...

I do agree that position and telemetry packets should be de-priotized in the to-phone queue in favor of incoming text message packets, if there is contention for space.

I have a PR up for updating our NimBLE lib_dep version. We're quite a bit behind. I have no idea if it'll fix this issue or not, but it's worth...

Latest attempted fixes are being pushed to this PR (see artifacts) https://github.com/meshtastic/Meshtastic-device/pull/1629 Enhanced logging is enabled on this build, so serial logs when bugs are encountered are very helpful for...

@garthvh do we know if this has been resolved with the transition to the new bluetooth stack?

Closing. It's a great idea, but any future efforts at a similar solution to enhanced privacy need to take into account the limited resources we have to work with on...

Tested and it seems to work on 1.3 set from the python cli. 1. Set LongName as call sign (and shortname based on that) 2. Dropped encryption from the primary...

Confirmed this is working in the latest firmware. I added some more detailed debug logs locally, so that the packet routing flow is more visible. ``` 12:51:51 169 [RadioIf] handleReceiveInterrupt()...

> In my testing on 1.3.44 both --sendping and --reply are already working. When using 'meshtastic --reply' on one device, sending a message 'Hi there' from another gets a response...