location in nodeinfo.json about docs HOT 9 CLOSED

the relevant commit

from docs.

I think latitude and longitude are useful. How is location.url meant to be different from 'http://' + hostname? If a node is in the US should they use state for region and city for municipality?

from docs.

👍 no issues here

from docs.

@clehner looks like the URL is meant to link to some mesh-local specific stuff, so eg the Seattle Meshnet nodes could link to the position of the node on our map.

from docs.

Since all keys are optional there are no issues for me.

from docs.

@clehner looks like the URL is meant to link to some mesh-local specific stuff, so eg the Seattle Meshnet nodes could link to the position of the node on our map.

Ok, that makes sense. I also notice that url is used in location whereas uri/uris is used in services. I assume url it to emphasize that the resource is something accessible in a web browser, vs. uri which could be hkp, telnet, cactus, …

from docs.

Good point. In an effort to support the cactus:// protocol, i vote we change it to uri. @ansuz ?

from docs.

works for me, someone else want to make the edit?

from docs.

fixed it. thanks for the input everyone.

from docs.