add removal policy
ansuz opened this issue · comments
At what point are credentials considered expired?
I think we should give operators some response time (say 48 hours) to
address credential issues, and if they do not respond to the issue that it
should be removed.
- someone creates an issue about broken creds
- operator is contacted and asked to respond
- incident is addressed in issue or else it gets removed after X time
On Sat, Oct 3, 2015, 2:53 PM ansuz notifications@github.com wrote:
At what point are credentials considered expired?
—
Reply to this email directly or view it on GitHub
#4.
48 is probably a little short. It's a volunteer project and people will get annoyed if they go on vacation and their server goes down. A week?
I just wanted to open a similar issue before I found this one. It seems like a lot of the offered peers (tested only EU) are no longer reachable and it's quite frustrating to try to connect to dead nodes. A simple UDP-portscan with nmap resulted in closed ports for:
Is there something planed which isn't written in this issue so far?
we were planning on setting up some automated testing, but it hasn't happened yet.
@jaythespacehound, @oniichaNj, @fbrandstetter, maybe you folks can report on the status of your nodes?
My node should be up and running just fine, I used it the other day without issues whatsoever.
It seems to go down every few hours for me with no errors in the log. Process just vanishes.
I've just pulled the latest version let's see if it stays up longer. If not I'll eventually cave and systemd it I guess.
I've removed this server it seems like. I'll fastly grab another one and setup CJDNS there and edit the config, so please don't delete it so far. Feel free to mark it as "down" meanwhile though.
We should probably remove public peers that aren't up to date (currently v18).
There are a number of fixes, and public peers should be a shining example for the rest of the network.