
First of all, let me state for the record that I admire the works of passion like this. Thanks for sharing it.
Now, that we have that out of our way…
logic to NOT repeat any packet it hears more than 2x
if it hears one, waits a tiny bit, making sure no other packets come in
just re-transmits so no real “hops”.

I strongly suggest not letting this out of the lab.
While it’s normal for meshtastic network to just lose a message here or there due to clients moving around, meshcore made an intentional decision for every repeater to repeat all flood messages, unless the number of traversed hops reaches the treshold, or unless the message is region scoped.
I can also see a potential issue with non flood traffic. If somebody sets a route for a message to go through a specific path, your node, sometimes switched to the other network temporarily, sometimes not repeating at all (if heard 2x) has a potential to intermittently break the path, forcing the 2 nodes with established message path to fall back to flood.
With both meshes being half duplex, it’s a miracle they work as well as they do. We can’t really afford to introduce additional obstacles.


























I can see the appeal. The bottom half with the first person point of view helps you quickly orient yourself, while the top half makes it easy to visualize the route ahead. All connected through a smooth transition.
However, the fact that something like this is patentable is kinda laughable.