Public resource but access restricted and exclusive
This community tracks restricted access resources (generally websites) that are supposed to serve taxpayers and the general public, but they fail in that duty by imposing arbitrary restrictions on access. This is where we document these cases.
Most often, it is the Tor community who is marginalised by incompetantly implemented infosystems. This community will be mostly littered with references to tor-hostile public resources to a fatiquing extent, but this is expected. It is not necessarily limited to Tor. Any demographic of people who are refused service would have a relevant story here. E.g. someone traveling outside their country and being denied access to a homeland website on the basis of presumed IP geolocation.
This is very closely related to the [email protected] community. But there are some nuanced differences. Not all fiefdoms are necessarily always restricted access. E.g. some rare Facebook pages are reachable to non-FB users.
And not all manifestations of restricted access entail a fiefdom. E.g. it’s increasingly common for a gov website to block Tor visitors at the firewall without involving a digital fiefdom.
Cases of Cloudflare, Facebook, LinkedIn and the like can be crossposted in many situations. They are a fiefdom walled garden and also commonly configured to restrict access. IDK.. use your best judgement. Might suffice to just post in [email protected] in those cases.
Also related: [email protected]
Scope and rules:
What is not relevant here:
- NGOs
- non-profits
- anything in the private sector
This community is focused on tax-funded government programs and services like public education, social services, voter reg, courts, legal statutes, etc. NGOs and non-profits may exist for the pubic benefit, but if they are not funded by force (taxation) then they are not really relevant here.
Recommended style:
- the title should mention the jurisdiction (state/province and/or country)
view the rest of the comments
It’s possible that it’s an accident, but unlikely IMO. The accidental case is overload and timing fragility. Tor introduces a delay, so if a server already has a poor response time and the user’s browser has a short timeout tolerance, then it’s a recipe for a timeout. Firefox does better than Chromium on this (default configs). But I tried both browsers. At the state level I think they made a concious decision to drop packets.
It’s also possible that they are not blocking all of Tor but just the exit node I happened to use. I did not exhaustively try other nodes but I was blocked two different days (thus likely two different nodes). In any case, this forum should help sort it out. Anyone can chime in with other demographics who are blocked, or tor users that are not blocked.
(edit) ah, forgot to mention: www.flsenate.gov also drops Tor packets.
This seems like two odd decisions that I'd really like to know the thought process behind. Why block Tor to begin with, and why specifically packet loss? It makes me wonder if it's some kind of odd attempt at a honeypot, though that seems unlikely. Thus interesting to know about. Thanks for posting.