What are the current requirements to get an HSDir flag assigned to a relay? MYCROFTsOtherChild has, at last heartbeat message, been up for 35 days and 7 hours. To the best of my knowledge, it has not had an HSDir flag in the consensus at any time since it was last started more than a month ago. What are the current requirements to get a Fast flag assigned to a relay? MYCROFTsOtherChild often runs busily at 330 KB/s to 350 KB/s. Sometimes since it was last started over a month ago it has had a Fast flag in the consensus, and at other times it has not. The Fast flag seems to come and go like the wayward breezes. The Bandwidth= value in the consensus entry for MYCROFTsOtherChild has varied from somewhere in the 30s to the 110s, AFAI have seen, but is always subject to the delayed effects of the presence or absence of the Fast flag, of course, and prior to the currently running instance has also been subject to the presence or absence of the HSDir flag. The authorities have seemed to be acting more or less at random when assigning flags for the consensus for many months. Does the tor project envision any timeline for a return to rational, predictable behavior on the part of the authorities?
Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at sdf.org *xor* bennett at freeshell.org * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * **********************************************************************