repo structure

[ansuz]

README.md
creds/
  *.json

naming scheme?

[daniel]

I think using the nodes ipv6 address would suffice.

For example:
peers/creds/fcec:ae97:8902:d810:6c92:ec67:efb2:3ec5.json

[ansuz]

If a few more people agree we'll go with that.

[daniel]

Actually, I don't think that is a valid file name. I propose to use the public key instead.

[Finn]

It should be based on region. IPv6 address is arbitrary, not something you look for with peering. What if we did like peers/creds/<country>/<state|bioregion|city>/<pubkey>.json

[ansuz]

oh, I like that

[daniel]

@thefinn93 I think that is good idea.

[ansuz]

nodeinfo.json has location fields now. those fields could then follow that same convention, and make peering suggestions easier.

https://github.com/hyperboria/docs/blob/master/cjdns/nodeinfo-json.md

Country, region, municipality?

[Caleb Smith]

Sounds good to me

[ansuz]

So, next thought:

If we're using , what's our policy with regards to nationstates collapsing, or controversial borders? It's an edge case, but I'm trying to think ahead.

Crimea or Palestine could easily be sensitive topics.

(edit) What about not even using nations (Canada/USA) and instead just using continental borders?

[ansuz]

Since there were no objections, I changed location.country in the nodeinfo.json spec to location.continent.

The spec can be found here.

Repo structure should ∴ be /creds/<continent code>/<region>/yourNodesPublicKey.k.