Anyone here who have experience with Yggdrasil who want to comment on that?
I’ve been running Yggdrasil on seven boxen for the past two months, and it’s been running flawlessly from what I can tell.
Yggdrasil is way easier to build than cjdns, and to peer with other nodes all you need is an IP address and a port number. You can literally have Yggdrasil up and running in less than half an hour. And Yggradrasil nodes on a LAN will auto-discover each other (like cjdns with the beacon activated).
I’ve been using it for a while, and I have to say, for alpha it’s really good at just working consistently well without any crashes and similar issues. At least for me, I’ve heard someone had crashes, though that was fixed, apparently.
Tunneling over tor, and even i2p works without problems (other than slowing things down, especially in case of i2p).
Totally unlike my experience with cjdns, which, when I tested it, consistently kept dying at least few times a day, and had other issues, like weird 2 process model and when I sigterm master it leaves child running (so not good for daemontools), no support for tcp (so any kind of tunneling required ugly hacks which didn’t work well), requirement of nodejs just to build it… Maybe my experience is outdated, as it’s been more than year now, but all of it just left bad taste. Oh yeah, this isn’t about cjdns.
Community is okay, developers are friendly and reasonable people, I’ve contributed some improvements for things I cared about, and they’ve been accepted.
Overall, my experience is largely positive.
ive been running Yggdrasil from the start, its freakishly stable for something only in alpha.
Developers are very organized and helpful and listen to users, documentation is also amazing.
They keep adding well thought out features.
There is a good community developing around with lots of little projects to boot.
If you have not tried it, i highly recommend and you can find the devs in irc, more info on their website.
This is what the network currently looks like as of this post:
Does it somehow work across home routers with masquerading?
Outbound peerings will work perfectly over a masquerading NAT.
My Bachelor’s thesis in 2003 was about simulating a distributed hash table network - more specifically using chord. So it is fun to see projects nowadays switching TO it.
Yep - we think it will have some benefits over the previous Kad approach. How did your simulation turn out?
oh, it was mostly fun to look at. you could inspect the routing tables as tables but also as a graph and that was fun to see when more nodes were joining.
I did some work towards injecting failures but didn’t quite finish it ;)