3 ms·

@dang? Can someone please fix the title? Something like "I have been unable to connect to Stack Overflow using Tor today" would be appropriate. The title at the

@dang? Can someone please fix the title? Something like "I have been unable to connect to Stack Overflow using Tor today" would be appropriate. The title at the moment is rash speculation. One doesn't expect HN to be perfect, but one expects more conscientiousness than this.

float4 5y ago
I disagree. I just opened Tor myself to check, and indeed every circuit (I've refreshed ~10 times using cmd+shift+L) results in an error page that literally states: "Reason: Blocked."
- thomassmith65 5y ago
  It's beside the point. What if you had connected? What if an endpoint with a different IP can connect? The standard here ought to be that the title accurately reflect the content. This post does not. I don't take HN as the kind of place where people want to read speculation masquerading as fact.
  - float4 5y ago
    The core of your argument is that you don't think many reloads, by different users, from different Tor IP's, is convincing evidence, and I think that makes you part of a very tiny minority.
    - thomassmith65 5y ago
      It probably does, sadly.
    - stjohnswarts 5y ago
      I had the same result, 8 connects from "new identity" feature, all ips blocked. It may be temporary though, but today, for sure they are blocking tor.
      - thomassmith65 5y ago
        I don't know StackOverflow's Tor practices. Given the post's title, I was disappointed to finish reading the post and still not know. If I had read the same post with a title like "Ask HN: is Stack Exchange (Stack Overflow) now blocking Tor?" I would have no complaint.
jandrese 5y ago
I ran into this yesterday when testing a Tor middlebox. I didn't think much of it at the time because you slam into a lot of these "no" pages when browsing via Tor. I did think it was a shame that they didn't even give you the "10 CAPCHAs in a row" option that Google will hit you with if you really really need to use the service.
muzani 5y ago
I'd say titles with "Tell HN" in general should trigger an alert. A good deal of it is speculative at best, slander at worst.

float4 5y ago

I disagree. I just opened Tor myself to check, and indeed every circuit (I've refreshed ~10 times using cmd+shift+L) results in an error page that literally states: "Reason: Blocked."

thomassmith65 5y ago
It's beside the point. What if you had connected? What if an endpoint with a different IP can connect? The standard here ought to be that the title accurately reflect the content. This post does not. I don't take HN as the kind of place where people want to read speculation masquerading as fact.
- float4 5y ago
  The core of your argument is that you don't think many reloads, by different users, from different Tor IP's, is convincing evidence, and I think that makes you part of a very tiny minority.
  - thomassmith65 5y ago
    It probably does, sadly.
  - stjohnswarts 5y ago
    I had the same result, 8 connects from "new identity" feature, all ips blocked. It may be temporary though, but today, for sure they are blocking tor.
    - thomassmith65 5y ago
      I don't know StackOverflow's Tor practices. Given the post's title, I was disappointed to finish reading the post and still not know. If I had read the same post with a title like "Ask HN: is Stack Exchange (Stack Overflow) now blocking Tor?" I would have no complaint.

jandrese 5y ago

I ran into this yesterday when testing a Tor middlebox. I didn't think much of it at the time because you slam into a lot of these "no" pages when browsing via Tor. I did think it was a shame that they didn't even give you the "10 CAPCHAs in a row" option that Google will hit you with if you really really need to use the service.

muzani 5y ago

I'd say titles with "Tell HN" in general should trigger an alert. A good deal of it is speculative at best, slander at worst.