Mycoria is built for resilience - so not relying on the current Internet backbone working flawlessly.
Even if the current Internet works "normally", many users of similar network have reported better connectivity with the overlay network routing. Eg. routing on the IANA Internet is highly influenced.
If you let Mycoria generate a config for you, it will include your current public Interfaces on the device, so this will only be true for servers. Mycoria does not rely on IANA addresses, but uses them to improve the network structure automatically: Finding better routes between routers over the IANA Internet.
This is what I hope to solve with the private addresses: These are not geo-marked and not routable. Eg. they are randomly generated and cannot be attributed to a geographic location (easily).
Mycoria has in integrated firewall for this, just in case that information got lost somewhere.
This also means that devices of the company will help other devices of the company to reach their destination, adding to resilience in outages and emergencies.
You can of course build bridges between these networks. This definitely something that is planned.
Mycoria is secure by default: It has an integrated firewall that only allows access from explicitly defined addresses, or, optionally from anyone in the network.
Also, multicast is completely disabled on Mycoria.
Currently, this is just a fun project for me. I have technical ideas, but I don't have growths plans or the like - and it is nice that it does not have to.
Yes, I would expect the privacy would increase by some degree with more users, but I don't know by how much.
Although I will be using the technology in future projects, so Mycoria will benefit from that.
I wasn't really aware segment routing, tbh. However, I do think with where Mycoria is going, the additional control to change things as needed will be required.
I have used VerifPal https://verifpal.com/ for security analysis before, but not yet with Mycoria.