further nesting for credentials

Question

further nesting for credentials

ansuz opened this issue 8 years ago · comments

The js api recurses over the directory structure, finding keys, and exposing everything as a searchable JSON structure.

Now that this api is being used by a queryable http api, it's apparent that this repo could benefit from a further nested structure.

/<continent>/<country>/<region>/<city>/<neighbourhood>/credential.k would expose more search terms that users could employ to find nearby nodes.

Caleb Smith · Answer 1 · Sat Oct 01 2016 19:06:14 GMT+0800 (China Standard Time)

While more info is always great for finding closer peers, what about those
people who might not want to volunteer data that precise? For instance, I'm
happy to volunteer I live in Virginia, but I don't usually mention where.

On Sat, Oct 1, 2016, 6:02 AM ansuz notifications@github.com wrote:

The js api recurses over the directory structure, finding keys, and
exposing everything as a searchable JSON structure.

Now that this api is being used by a queryable http api
https://github.com/fc00/peers-api, it's apparent that this repo could
benefit from a further nested structure.

//////credential.k would
expose more search terms that users could employ to find nearby nodes.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#76, or mute the thread
https://github.com/notifications/unsubscribe-auth/AHZULh9-ciDaLHZJ-SbpvKqA6vIj4ZGQks5qvi_EgaJpZM4KLuAR
.

ansuz · Answer 2 · Sat Oct 01 2016 19:10:26 GMT+0800 (China Standard Time)

It could be optional, but in any case the public node would only work if an IP is provided.
People can find where your node is already (not you), this would only improve discoverability of nodes which are intended to be public anyway.

Caleb Smith · Answer 3 · Sat Oct 01 2016 19:12:18 GMT+0800 (China Standard Time)

Fair enough. +1 for further nesting.

On Sat, Oct 1, 2016, 7:10 AM ansuz notifications@github.com wrote:

It could be optional, but in any case the public node would only work if an
IP is provided.
People can find where your node is already (not you), this would only
improve discoverability of nodes which are intended to be public anyway.

—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
#76 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHZULrY7MvY5AhES5xvh1o1oFE4QEXb0ks5qvj-igaJpZM4KLuAR
.