re: decentralization
ansuz opened this issue · comments
A common convention for organizing public peering credentials is a step towards the goal of making cjdns easier to configure for the first time.
That being said, keeping the credentials in this repository where a set of gatekeepers can add or remove files centralizes an important aspect of cjdns (who connects with whom).
I'm considering creating a reference implementation that can scrape this repository, or another repository with the same structure. The conventions that make that possible should be agreed upon (indexing via html? keeping a json index?).
@kpcyrd, I expect you'll be interested in this because of yrd and nightfall.
@clehner Maybe we can tie this in with nij, generating a nodeinfo.json file in accordance with commonly agreed on location data, and then read nodeinfo.json when looking for nearby peers (programatically)?
I added a js-api that should work for any project with the same structure.
Maybe this could be used to provide an http api? Search for nodes by region?
If we're exposing this as an api, it would be interesting to have something tag based. For example have a script that connects to some cjdns nodes running in the same data centre, which is often free traffic.
@lgierth pointed out that the configurator now only sends data which will be used by cjdroute, so we're less limited in terms of how much data we want to put into the credentials.
What would we name a field like that?
- circuit
- noc
- vps
- hosting
- backbone
technically, if enough nodes are added, is it decentralized? @ansuz @kpcyrd @wfleurant
I just work here man
@ansuz I'm gonna make you very 😄 .... YOUR FIRED!
@ansuz It was intentional, as someone as dumb as Donald J. Trump himself will never have correct grammar. It's exaggerated in all the YouTube Videos. Oh wait, your too old. Or I'm too young. (13)
