-
Notifications
You must be signed in to change notification settings - Fork 10
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
Comments
Perhaps for the purpose of encouraging existing efforts, we should require that to be added, a node must host a nodeinfo.json file. |
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. |
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? |
data is now in services.json, which should make writing nightly tests a bit easier. |
I did it manually.... f00gle is down, lots of services that should be added. Other than that, everything is up. |
Historically lists of services on Hyperboria have fallen into bad states.
People tend to:
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.
The text was updated successfully, but these errors were encountered: