I think that many of my previous scans were not useful and showed inaccurate
I'm glad that it turned out that these previous results might have been inaccurate (because the results were scary if found to be accurate)
results because the IP address i was scanning from might have gotten black listed by dir-auths?
I don't see how dir auths could blacklist specific client IP addresses (tor clients use fallbackdirs)
or perhaps blocked by many relays by the anti-denial-of-service mechanisms in tor?
can you let me know the start and end date of the scan (2018-03-12?) so I can check how many of the relays you scanned (the top 100 relays by cw? at the time) had a tor version with anti ddos features at the time?
During your first scans (2017) there have been no anti-dos features.
i got rid of that virtual server and lost use of it's IP address... so we'll never know.
Katharina and I are interested in doing lots more thorough scans of the Tor network rather than this limited methodology i've been using.
I'm excited to hear that.
What are the guidelines to avoid getting blocked by the tor network?
stay under the public thresholds? https://www.torproject.org/docs/tor-manual-dev.html.en#_denial_of_service_mi...
Is it possible to check the consensus to see if a client IP has been blocked?
the consensus holds information about relays not about tor client IP addresses, but I assume you know that and I misunderstood your question?