On of the use-cases for this is for Peer-to-Peer matrix: https://matrix.org/blog/2020/06/02/introducing-p-2-p-matrix
Except I think the matrix project is going with pinecone instead. https://github.com/matrix-org/pinecone
Yggdrasil – Early-stage implementation of an end-to-end encrypted IPv6 network
41–50 of 109 posts
Re: Yggdrasil – Early-stage implementation of an end-to-end encrypted IPv6 network
#42Earlier quoted context omitted.
Can anyone help with the pronunciation? There's no help from the Wikipedia article. (Not that Wikipedia pronunciation guides are of any use to anyone other than language nerds, anyway.)
In parts of Europe it's quite common (at least in Sweden and Norway I know it's true) to learn the IPA so you can make sense of the alphabet and its phonemes, no need to be a language nerd to have a passing knowledge of IPA. I recommend you studying it a little, it's really not that hard, just looks weird.
Can confirm. Also learned it in school in Germany, although I forgot most of it, because I almost never use it. For most things, forvo [0] works good enough.
Re: Yggdrasil – Early-stage implementation of an end-to-end encrypted IPv6 network
#43Re: Yggdrasil – Early-stage implementation of an end-to-end encrypted IPv6 network
#44Re: Yggdrasil – Early-stage implementation of an end-to-end encrypted IPv6 network
#45Earlier quoted context omitted.
Except I think the matrix project is going with pinecone instead. https://github.com/matrix-org/pinecone
Which is based on yggdrasil.
it's fairly circular actually - we used Yggdrasil in some of the earlier P2P Matrix POCs. This showed up some limitations, so we worked on solutions for them (alongside Yggdrasil) which became Pinecone on the Matrix side, and Ironwood on the Yggdrasil side. Then Yggdrasil 0.4 is incorporating them for general purpose IP overlay routing, while Pinecone is focusing on Matrix-specific application layer overlay routing. Perhaps the two will converge in the end, but until then they're somewhat overlapping friendly sister projects :)
Re: Yggdrasil – Early-stage implementation of an end-to-end encrypted IPv6 network
#46Earlier quoted context omitted.
Can anyone help with the pronunciation? There's no help from the Wikipedia article. (Not that Wikipedia pronunciation guides are of any use to anyone other than language nerds, anyway.)
In parts of Europe it's quite common (at least in Sweden and Norway I know it's true) to learn the IPA so you can make sense of the alphabet and its phonemes, no need to be a language nerd to have a passing knowledge of IPA. I recommend you studying it a little, it's really not that hard, just looks weird.
Know of any good resources to learn it?
-noob language nerd
Re: Yggdrasil – Early-stage implementation of an end-to-end encrypted IPv6 network
#47Earlier quoted context omitted.
Can anyone help with the pronunciation? There's no help from the Wikipedia article. (Not that Wikipedia pronunciation guides are of any use to anyone other than language nerds, anyway.)
Lifted from the Wikipedia article: Yggdrasil Linux/GNU/X, or LGX (pronounced igg-drah-sill) Don’t need to be a language nerd to understand that.
You have to love that it's a "Linux/GNU/X" system.
Not even at GNU/Linux, but a Linux/GNU system... Would Stallman accept that or does GNU have to be first?
Re: Yggdrasil – Early-stage implementation of an end-to-end encrypted IPv6 network
#48What a stupid name. Looks like misspelled medicine name.
Re: Yggdrasil – Early-stage implementation of an end-to-end encrypted IPv6 network
#49What a stupid name. Looks like misspelled medicine.
Re: Yggdrasil – Early-stage implementation of an end-to-end encrypted IPv6 network
#50Earlier quoted context omitted.
It's an overlay network (a software defined network that runs on top of another network... like you internet service providers network). It's closer to bittorent than a VPN. It has end-to-end encryption and each node (the app that runs on your PC) distributes routes to each other (similar to how routing works on the Internet between large networks). It appears to be a flat spanning-tree style network. They mention th…
Do I understand correctly that it does not do hole-punching, and e.g. unlike with a VPN a host behind NAT will not be able to accept incoming connections?
This is correct in the sense of peering, however hosts behind a NAT can simply connect to any other host on the network such as a pubic peer and then they can accept incoming connections over the yggdrasil network.
I use yggdrasil for NAT hole punching my VPN, for example.