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
Replies
8
@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!
@varx @lattera yeah, up here in the Seattle area they're getting really close to max capacity with the existing repeaters and I see people in the local public channel discussing adding AI bots and shit to it which is not a great use of a super limited resource. They're going to end up just crushing the network with garbage messages, and then stuff like the emergency channel will be useless.
@varx @lattera this is what I can see with Meshcore with a credit card radio sitting on my desk
edit: I didn't realize until I took these screenshots that we can reach Idaho now
edit: I didn't realize until I took these screenshots that we can reach Idaho now
@polishdub @lattera no they cannot communicate with each other.