hyperboria/peers

add requirements for json to README

ansuz opened this issue · 6 comments

ansuz commented
  1. Creds should be valid json (no comments).
  2. Creds should not be so long that they overflow (we need a linter)
  3. The json should have required fields. Obviously publicKey and password, but also:
    • location
    • contact
  4. Path must adhere to the repository layout. That means keeping a consistent hierarchy for folders.
  5. ???
ansuz commented

tabs or spaces? It should match cjdroute.conf

dansup commented

I think tabs.

On Sat, Oct 3, 2015, 2:47 PM ansuz notifications@github.com wrote:

tabs or spaces? It should match cjdroute.conf

—
Reply to this email directly or view it on GitHub
#3 (comment).

kpcyrd commented

I think there needs to be an example what valid json is, since most people don't exchange valid json for peering ->

"ip:port":{ ... }

if the spec is "one line, regular peering format" we could just concat all files, which is what I've planned for nightfall.

ansuz commented

we need an extra step to validate that it will fit within a datagram after bencoding. Too much json will crash the configurator.

kpcyrd commented

#2 is invalid on jsonlint.com