3 ms·

I can't reproduce it, and it's not the sort of bug HN's architecture would tend to produce. The most likely culprit may be excessively aggressive caching by so

by pg 15y ago

I can't reproduce it, and it's not the sort of bug HN's architecture would tend to produce. The most likely culprit may be excessively aggressive caching by someone between you and HN. I've heard reports of that.

tptacek 15y ago
This happens to me pretty regularly; I just never thought to complain about it.
- pg 15y ago
  Wow, really? Can you describe what happens?
  - tptacek 15y ago
    Come to a comment thread via the comments pages of one of the users I follow (say 'anigbrowl). Reply to an 'anigbrowl comment. Find myself on the comments page of whoever 'anigbrowl was himself responding to. My comment has posted, of course; I just have to back-button back to 'anigbrowl's page. So no big deal.
    - pg 15y ago
      Do you always end up on the grandparent page?
      - tptacek 15y ago
        I thought about it right after I posted. Answer: not sure. I'll be sure to take note next time it happens. This is totally not a big deal, at least to me.
  - anigbrowl 15y ago
    Yeah, sorry that my description was a bit vague. I have not noticed a consistent linkage between where I post and whose comment page I end up on, yet; only that it tends to happen in longish threads. I get this about once a 'busy' day - say a whole day of being at the desk and participating in about 10 threads. So it probably only affects people who have HN permanently open. Edit: looking at Tom's remark about the grandparent, I notice that the comment of his to which I replied was a 8th-generation reply to a moldbug comment (http://news.ycombinator.com/item?id=3692241 http://news.ycombinator.com/item?id=3692241). I had replied to another comment at similar depth just previously (http://news.ycombinator.com/item?id=3704308 http://news.ycombinator.com/item?id=3704308). So it may be a function of tree depth rather than overall thread size.

3 ms·

I can't reproduce it, and it's not the sort of bug HN's architecture would tend to produce. The most likely culprit may be excessively aggressive caching by so

by pg 15y ago

tptacek 15y ago
This happens to me pretty regularly; I just never thought to complain about it.
- pg 15y ago
  Wow, really? Can you describe what happens?
  - tptacek 15y ago
    Come to a comment thread via the comments pages of one of the users I follow (say 'anigbrowl). Reply to an 'anigbrowl comment. Find myself on the comments page of whoever 'anigbrowl was himself responding to. My comment has posted, of course; I just have to back-button back to 'anigbrowl's page. So no big deal.
    - pg 15y ago
      Do you always end up on the grandparent page?
      - tptacek 15y ago
        I thought about it right after I posted. Answer: not sure. I'll be sure to take note next time it happens. This is totally not a big deal, at least to me.
  - anigbrowl 15y ago
    Yeah, sorry that my description was a bit vague. I have not noticed a consistent linkage between where I post and whose comment page I end up on, yet; only that it tends to happen in longish threads. I get this about once a 'busy' day - say a whole day of being at the desk and participating in about 10 threads. So it probably only affects people who have HN permanently open. Edit: looking at Tom's remark about the grandparent, I notice that the comment of his to which I replied was a 8th-generation reply to a moldbug comment (http://news.ycombinator.com/item?id=3692241 http://news.ycombinator.com/item?id=3692241). I had replied to another comment at similar depth just previously (http://news.ycombinator.com/item?id=3704308 http://news.ycombinator.com/item?id=3704308). So it may be a function of tree depth rather than overall thread size.