The #Meshtastic code is absolutely full of hardcoded magic numbers. I suspect changing the size of a single buffer might prove problematic.
Timeline
Post
Remote status
Context
3
@lattera switch to Meshcore, it's a much better project. They haven't wasted all the bandwidth with noise. I couldn't do anything with Meshtastic, but with Meshcore I can reach north of Vancouver Canada down to northern Oregon, hundreds of nodes
though both have a similar problem with network capacity. Meshtastic falls over once you hit ~25% airtime being used, Meshcore with ~30%. Too many retransmits. It's like everyone's sharing an ethernet hub -- just one fat broadcast domain everyone is fighting over
though both have a similar problem with network capacity. Meshtastic falls over once you hit ~25% airtime being used, Meshcore with ~30%. Too many retransmits. It's like everyone's sharing an ethernet hub -- just one fat broadcast domain everyone is fighting over
@feld After my "hacker show & tell" on Saturday, I plan to take a very deep look at #MeshCore. I suspect both MeshCore and #Reticulum will play crucial roles in the next phase of my R&D on a censorship- and surveillance-resistant mesh network.
@lattera sounds awesome!
Replies
0Fetching replies…