hyperboria / services

Services on Hyperboria
30 stars 10 forks source link

Service info format #4

Open Kubuxu opened 8 years ago

Kubuxu commented 8 years ago

What should be the format on different layers:

ghost commented 8 years ago

IPLD :D

Kubuxu commented 8 years ago

It should be mainly human readable and easily parsable :smile:

IPLD could be an option if there was something for IPLD like jq for JSON.

dansup commented 8 years ago

Why not use nodeinfo.json ? Also what is IPLD?

Kubuxu commented 8 years ago

Problem with nodeinfo is that it from begging was a non-schema format. I for example would like to have (even small) CI nightly checking services and tagging those that are down. We are having problems with services that get rarely used, go down and nobody notices until someone wants to use it.

cschmittiey commented 8 years ago

I'd prefer something human-readable as well.

On Sun, May 8, 2016, 12:18 PM Jakub Sztandera notifications@github.com wrote:

Problem with nodeinfo is that it from begging was a non-schema format. I for example would like to have (even small) CI nightly checking services and tagging those that are down. We are having problems with services that get rarely used, go down and nobody notices until someone wants to use it.

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/hyperboria/services/issues/4#issuecomment-217730528

ansuz commented 7 years ago

since nobody acted it seems it's just going into a markdown table. :smile:

I added h.ipfs.io just now, maybe it's time we start populating this more?

ansuz commented 7 years ago

the markdown table is now json.

We can use that to construct a page that lists services in a table.