https://raw.githubusercontent.com/slackhq/nebula/master/exam...
This puts Nebula in a relatively small group of what I would call true self-hosted overlay networks (by the definition of "self-hosted" I subscribe to). Kudos for that.
What drew my attention was the remote IP address in
https://raw.githubusercontent.com/slackhq/nebula/master/remo...
No idea why that is there.
Anyway, while I would not necessarily choose to run Nebula myself (I prefer smaller overlay networks, for example), it is certainly an exception to the pattern I see in so many other "self-hosted" peer-to-peer projects. I apologise if the comment I submitted implied otherwise.
Note I never suggested innernet "runs on Nebula". The words I used were "innernet relies on Nebula." Of course, that, too, is incorrect. The blog post was just comparing innernet to Nebula. My bad! I am just too cynical about peer-to-peer projects since so many fall into the same patterns I dislike; hence I skimmed where I should have read more closely.
If you checked Nebula's readme you'd see the following:
> Nebula lighthouses allow nodes to find each other, anywhere in the world. A lighthouse is the only node in a Nebula network whose IP should not change. Running a lighthouse requires very few compute resources, and you can easily use the least expensive option from a cloud hosting provider. If you're not sure which provider to use, a number of us have used $5/mo DigitalOcean droplets as lighthouses.
Beyond that, innernet does not run on nebula.