Yep. This time around the particular comment seems to be 1rvk in the numbering scheme used in URLs.
On what thread?
I can’t tell, since I can’t see that particular comment. I’ve inferred that “number” by some boundary testing, inputting various URLs to see which ones worked and which breaked.
I see—playing with http:// lesswrong.com/comments?count=50&after=t1_[comment-ID] seems to suggest 1rvj may be responsible, as http://lesswrong.com/comments?count=50&after=t1_1rvj has 1rvi as the first visible. That said, http://lesswrong.com/comments?count=50&after=t1_1rxo works where http://lesswrong.com/comments?count=50&after=t1_1rxn fails, which suggests 1rw8 breaks the page, too.
Edit: At least on my viewer—other people may have their Recent Comments set to show fewer comments.
Yep. This time around the particular comment seems to be 1rvk in the numbering scheme used in URLs.
On what thread?
I can’t tell, since I can’t see that particular comment. I’ve inferred that “number” by some boundary testing, inputting various URLs to see which ones worked and which breaked.
I see—playing with http:// lesswrong.com/comments?count=50&after=t1_[comment-ID] seems to suggest 1rvj may be responsible, as http://lesswrong.com/comments?count=50&after=t1_1rvj has 1rvi as the first visible. That said, http://lesswrong.com/comments?count=50&after=t1_1rxo works where http://lesswrong.com/comments?count=50&after=t1_1rxn fails, which suggests 1rw8 breaks the page, too.
Edit: At least on my viewer—other people may have their Recent Comments set to show fewer comments.