@victor@Moon >What do I get by connecting to them? Access to my instance through y.ryona.agency, mostly. There's 83 more sites listed on sites.ygg ([21e:a51c:885b:7db0:166e:927:98cd:d186] if without ALFIS domains), the networks works well but feels even more desolate than I2P.
I see from the Yggdrasil FAQ that this is part of a deprecated IPv6 range (so is basically free for all).
So I guess DNS requests still go through clearnet, but all traffic between hosts on Yggdrasil is encrypted? Is there any concept of onion routing, or is it solely a mesh network to build other stuff on top of while using the clearnet’s routing?
@victor@Moon The traffic is end-to-end encrypted, but there's no onion routing, just a simple spanning tree (you can still build a Tor-like network over it, though, as well as connect to Yggdrasil through public peers in Tor). The IPv6 address is the public key, and for each address in 200::/8, a /64 subnet in 300::/8 is assigned (don't know what will happen during collission, but it haven't happened yet; the bigger the lower bits (2XX) are, the harder it is to bruteforce the address). There's no built-in DNS at all, so it'll go through whatever you set up separately. You can use both the regular ICANN domains, OpenNIC, Namecoin/Emercoin/etc, and there's been a few projects that provide Yggdrasil-specific DNS: Wyrd (crawls nodeinfo for DNS records, I think it stopped working due to breaking changes in routing in 0.4), meshname (also works with cjdns, provides onion/b32-like addresses) and ALFIS (small blockchain, not yggdrasil-speficic but .ygg domain is hardcoded to be restricted to 200::/8).