On 28 Jun 2018, at 11:45, Keifer Bly keifer.bly@gmail.com wrote:
It is also a pain at times keeping the OS, especially on macOS, the newer versions of which my not support older machines, up to date while trying to keep the relay stable, as relay status is changed so quickly (removing relays from the conseoucsus list within 40 mins) which can be troublesome for areas that sometimes experience power outages, which happens during winter where my relay is run.
But a 60 minute turnaround for relay reachability is *good* for clients.
I think that is a part of the relay guide that we can improve: Relays exist so that clients can use the network. Consensus flags exist so that clients can use the network efficiently. Bandwidth weights are assigned so that clients can use the network efficiently.
What seems strange to me is that I see there is a “running” flag. This flag seems pointless to me if the relay is just completely removed from the conseoucsus if it’s detected as not currently running to begin with;
You're right, the Running flag is historical, and kept for backwards compatibility. (We used to list relays that were not Running, but removed them from the consensus to save client bandwidth.)
why not just give an “X” flag if the relay is unreachable for three days or so?
Remember: consensus flags exist so that clients can use the network efficiently. How would clients use a NotRunningForThreeDays flag?
T