Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

validating which services continue to be available #1

Open
ansuz opened this issue Mar 13, 2016 · 5 comments
Open

validating which services continue to be available #1

ansuz opened this issue Mar 13, 2016 · 5 comments

Comments

@ansuz
Copy link
Member

ansuz commented Mar 13, 2016

Historically lists of services on Hyperboria have fallen into bad states.

People tend to:

  1. join the network
  2. launch a service
  3. add their service to the list
  4. get bored or otherwise unable to maintain their service
  5. disappear, but leave their service's address on the list

If we're going to attempt to maintain a list of services on the network, we should set up some means of testing whether they are still active, and some policy for when a service should be removed from the list.

@ansuz
Copy link
Member Author

ansuz commented Mar 13, 2016

Perhaps for the purpose of encouraging existing efforts, we should require that to be added, a node must host a nodeinfo.json file.

@Kubuxu
Copy link
Collaborator

Kubuxu commented Mar 13, 2016

Requiring nodeinfo.json is good thing, daily checks of service availability also should be doable and might be useful even for service owners themselves, my site once went down I a didn't notice for a week.

Simple scriptable check engine, maybe in Lua would be awesome. We would store services and check scripts in this repo and have worker do the checks.

The script might be simple, fetch index.html, check if error code is ok in case of most sites. In case of IPFS gateway it might do a bit more extensive tests but those should be easy to write.

@benhylau
Copy link
Member

Agree with all above, especially the importance of this.

One node may announce a service hosted by another node (i.e. One of the service:uri not associated with the node's public key). Is that permitted, or we have to check against that?

@ansuz
Copy link
Member Author

ansuz commented Oct 16, 2016

data is now in services.json, which should make writing nightly tests a bit easier.

@kylerchin
Copy link
Contributor

I did it manually.... f00gle is down, lots of services that should be added. Other than that, everything is up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants