Thread

I was talking about this and other routing protocols such as cjdns with Squiggs at CMH yesterday. It's an interesting one, but I don't know how well the routing algorithm actually works in practice on a dynamic mesh network — it's something I've read about, so have a good technical understanding of, but not something I've actually experimented with to see whether its fault-tolerance mechanisms actually work. You can "host" whatever you like "on Yggdrasil". It's not a hosting platform, it's a routing protocol, like IP itself. You wouldn't say "I host my website on IPv6," you'd say "my website is available/reachable over/using an IPv6 connection." Likewise, you'd say "my Nostr relay is reachable using Yggdrasil." The goal in the context of making routing accessible to the masses should be to minimise the technical knowledge needed to deploy them. To that end, even good old IP is fine, but the problem is hiding all of the complexities of BGP from laymen that want to deploy routers, and making sure the routing algorithms are still efficient at that kind of scale. The modern internet remains scalable due to its semi-hierarchical structure, which facilitates route aggregation; despite IPv6 network IDs being 64 bits, the global IPv6 routing table almost entirely consists of 32-bit and 48-bit route IDs. You can achieve this kind of aggregation with plain old IP even without organisations such as ISPs, as long as local communities can agree on their locally unique name/ID, such as a city name within a country, a village name within a city, or a postcode/zipcode within a country. Yggdrasil differs by not relying specifically on name-level aggregation like a postal mail address, but instead relying on an "aggregated" view of a network graph: a spanning tree.