2 ms·
Alright, I looked throught the code. Suprisingly there is no default configuration that includes a third-party-operated resource. https://raw.githubuserconten
by 1vuio0pswjnm7 5y ago
Alright, I looked throught the code. Suprisingly there is no default configuration that includes a third-party-operated resource.
https://raw.githubusercontent.com/slackhq/nebula/master/examples/config.yml 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/remote_list_test.go 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.
- psanford 5y ago> No idea why that is there. That's a test file.