Can you communicate the value of Octelium in 25 words or less?

This is the correct capitalisation.

Thanks. Made my day.

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.

For the use case given by Zrok, Mycoria is very similar.

Nothing can access your device by default. You will have to define services and add "friends" (your other devices) to allow them to access.

It's quite fast. Especially if you host a server near you and connect to it.

If nobody knows who you are, you are still anonymous, even if there is an ID.

With private addresses (in the future) this will also be solved, as Mycoria will be able to temporary addresses / IDs.

It'd help if you could clarify what "everything is authenticated" really means, I can't find it on the website. Do you just mean the fact that things are bound to the cryptographic ID in the address?

Thanks for taking the time for this feedback.

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).

Ah nice! Glad to see you've already thought of this. Any sense of what % of addresses you would hope to be private vs geo-marked? (Asking because it's easy to mark all private addresses as being "bad" if they're in the minority, but once they reach a tipping point that becomes infeasible - at least we've seen this with addresses tagged as belonging to VPN providers).

If you have a decent amount of private addresses in the mix (1) such that blocking them would 'break' the mycoria experience(2) then it sounds like you've got a decent solution here - geo-aware prefixes for convenience and private addresses for when you'd prefer the anonymity.

1) I freely confess to not knowing what percentage a good mix would be. 20%? 5%? In practice, going back to the VPN example for IPv4, it's "a high enough percentage of important users complaining that their VPN connections are broken for a long enough time". Depending on the jurisdiction that can be 1% (well off / well connected people in a jurisdiction complaining to the right people that in turn overwhelm management with their complaints) to >20% (not necessarily well off or well connected users, but a critical mass that instead overwhelms ISP help desks with complaints).

2) Assumption: mycoria / the app you're building on top of it becomes so important that breaking it completely is a non-starter for the average ISP.

Probably - depending on your use case. Mycoria is still more or less MVP though.

Veilid is new to me, will have to read about it first. Thanks the pointer!

Nope. I did that with the last network I built: https://safing.io/spn/

Mycoria focuses a more on scalability, but still has some privacy focus.