2026-09-24 19:01 UTC
@sean@scoat.es The map is clearly wrong. A typical result of prefix collisions. What I do in @meshy while building the path on the map is that in case of a collision I pick the geographically closest colliding node to the previous node in the path. It mostly works. But only using 2B or 3B prefixes fixes this completely. I'm surprised someone still uses 1B in Canada. But it happens, the official client still defaults to it.
Replies (1)
-
@sean@scoat.es 2026-09-24 19:05
@sesivany@social.vivaldi.net Yep; definitely not realistic. We’ve been discussing disallowing vanity prefix generation on the #montreal mesh, too. This is interesting data. (We also recommend 3-byte, but the tyranny of the default is real indeed.) I like that closest-match strategy. It’s imperfect but better than this for sure.