5
0
mirror of https://github.com/cwinfo/hyperboria-peers.git synced 2024-12-25 18:55:41 +00:00
A geographically sorted list of public peering credentials for joining Hyperboria
Go to file
2016-06-19 11:50:24 +02:00
AS sg.hub.icfreedom.net 2016-03-20 21:46:38 +00:00
EU @fbrandstetter node in AMS (#55) 2016-06-14 21:15:27 +02:00
NA h.us-west.hub.icfreedom.net.k 2016-03-18 19:30:34 +00:00
.gitignore bump package.json because of readme 2016-06-19 11:50:24 +02:00
.travis.yml Use new build system (followed old docs before) 2015-11-25 13:06:24 -08:00
index.js alias __dirname, use 'read' 2016-06-19 10:13:09 +02:00
package.json bump package.json because of readme 2016-06-19 11:50:24 +02:00
README.md big readme changes 2016-06-19 11:26:49 +02:00
tests.js no more hardcoding. search the directory structure for .k files and load them 2016-06-19 03:44:08 +02:00
tests.py Forgot to return true 2016-03-13 10:51:08 -07:00

peers Build Status

A geographically sorted list of public peering credentials for joining Hyperboria.

Hyperboria uses cjdns to construct an end-to-end-encrypted ipv6 mesh network. Connections between nodes are established manually, and traffic is restricted to the resulting social graph.

This repository exists for those who don't already know somebody on Hyperboria.

Adding your public node's credentials

If you've created a public node, and would like to have it listed here, fork the repo, add a keyfile, and submit a PR.

Filepath conventions

Credentials are sorted geographically, by continent, region, and municipality.

For example, a node in New York City is listed at NA/us/newyork.

Region and municipality codes are based on self identification, not any ISO standard. An operator might prefer to list their node in Cascadia instead of Washington state. For simplicity's sake, we'd prefer that new credentials conform to existing structures.

JSON formatting

We have tried to standardize the structure of the actual credential files, as such, they have the strictest requirements of anything in this repository.

  • Your credentials must be valid JSON.
  • They must contain the necessary fields:
    • ip/port
    • password
    • publicKey
    • contact (a means of contacting the operator)
  • credentials should be formatted such that:
    • there is a space after each colon
    • indentation uses four spaces
    • the file ends with a newline character.
{
    "192.168.1.5:10326": {
        "login": "default-login",
        "password": "nq1uhmf06k8c5594jqmpgy26813b81s",
        "publicKey": "ssxlh80x0bqjfrnbkm1801xsxyd8zd45jkwn1zhlnccqj4hdqun0.k",
        "peerName": "your-name-goes-here"
    }
}

Naming your entry

Credential files must end with .k. Otherwise, you can name your file whatever you want, but for simplicity's sake, avoid characters which will need to be escaped at the command line (or within the javascript api).

Javascript API

Peering credentials in this repository can be accessed via a simple Javascript API (using Nodejs).

It's available as a module on npm:

npm install hyperboria-peers

Usage

var Peers = require("./index.js");

/*  return a list of public peers located in North America */
Peers.filter(function (creds, path) {
    return path.indexOf('NA') !== -1;
});

/*  return a list of public keys */
Peers.map(function (creds, path) {
    return creds[Object.keys(creds)[0]].publicKey;
});

/*  the underlying data is exposed in a nested json structure */
console.log(Peers.peers);

console.log(Peers.peers.NA.us.california);