4 ms·

Hey Dan, completely unrelated, but I wanted to report what seems to be a HN bug. Please feel free to detach-collapse this. album: https://imgur.com/a/QcHG9VK h

Hey Dan, completely unrelated, but I wanted to report what seems to be a HN bug. Please feel free to detach-collapse this. album: https://imgur.com/a/QcHG9VK https://imgur.com/a/QcHG9VK In the first screenshot, notice that the highlighted comment has no replies. Here's a link to the page I was on, anchored to that comment: https://news.ycombinator.com/item?p=3&id=27424195#27429786 https://news.ycombinator.com/item?p=3&id=27424195#27429786 In the second screenshot, after navigating to the comment directly, there are in fact replies: https://news.ycombinator.com/item?id=27429786 https://news.ycombinator.com/item?id=27429786 The bug is that those replies should be showing up in the first link, shouldn't they? E.g. https://news.ycombinator.com/item?id=27430242 https://news.ycombinator.com/item?id=27430242 is a reply to https://news.ycombinator.com/item?id=27429786 https://news.ycombinator.com/item?id=27429786, but when viewed on the original page https://news.ycombinator.com/item?p=3&id=27424195#27429786 https://news.ycombinator.com/item?p=3&id=27424195#27429786, it's absent. I know that "more" pages shift toplevel comments around, but I've never seen child subtrees get completely pruned with no indication that they exist at all unless you navigate to the comment directly. Sorry for the distraction. I didn't want to email this for a few reasons, some of which might be invalid. However, it does seem to be a slightly-serious bug if true, since a recent refactoring must've caused deeply-nested children not to show up when browsing top-level "more" links. I'm not sure anyone else has noticed yet. (If this is intended behavior, sorry!) Good luck bug hunting.

dang 5y ago
The 'more' link in place of a 'reply' link is intended to indicate that there are more comments in the subthread. We're experimenting, in order to deal with this problem: https://news.ycombinator.com/item?id=27437362 https://news.ycombinator.com/item?id=27437362.
- hluska 5y ago
  We all love and owe you, Dan. I hope you hear that constantly.
- sillysaurusx 5y ago
  Oh! I’m sorry, I had HN blindness. I didn’t notice at all that “reply” got swapped to “more”. Cool. (Wish it was a different color, or included the descendant count.)
  - dang 5y ago
    It probably will. Ideas about how to get this right are welcome.
    - smegcicle 5y ago
      why have a different interface than the expandable [more] used for dead comments? seems intuitive to piggyback on the same fading ui hint as comments, having a bright "more" indicating standing of hidden comments...
    - sillysaurusx 5y ago
      Honestly, at HN’s scale, maybe it makes sense now. After spending today using it, my gut reaction was to be sad that people will feel reluctant to throw a bunch of effort into replies that will immediately be hidden (as with Reddit). But after the server meltdown yesterday, it’s understandable. 14 years was a really good run. I suppose even lisp has its limits. :( Yeah, adding the descendant count would make it pretty good. Hard to think of anything better. I’ll be honest: I’m really worried this will become another tool for moderators to control discussions, while concealing the fact that it was a moderator (rather than algorithmic) decision. But no one can stop you if that’s the kind of control you want for your team. The flip side of that is, since 2018, your team has done a stellar job, as far as I can tell. I don’t know if something changed, but things seem calmer now. I can’t even recall the last worrisome moderator decision, and I’ve found myself arguing on your behalf more than once. Dunno. You’ll get it right; you usually do. Thanks for being welcoming about ideas, and good luck wrestling with transpilers and performance issues.
    - deleted 5y ago
      [deleted]
    - sillysaurusx 5y ago

dang 5y ago

The 'more' link in place of a 'reply' link is intended to indicate that there are more comments in the subthread. We're experimenting, in order to deal with this problem: https://news.ycombinator.com/item?id=27437362 https://news.ycombinator.com/item?id=27437362.

hluska 5y ago
We all love and owe you, Dan. I hope you hear that constantly.
sillysaurusx 5y ago
Oh! I’m sorry, I had HN blindness. I didn’t notice at all that “reply” got swapped to “more”. Cool. (Wish it was a different color, or included the descendant count.)
- dang 5y ago
  It probably will. Ideas about how to get this right are welcome.
  - smegcicle 5y ago
    why have a different interface than the expandable [more] used for dead comments? seems intuitive to piggyback on the same fading ui hint as comments, having a bright "more" indicating standing of hidden comments...
  - sillysaurusx 5y ago
    Honestly, at HN’s scale, maybe it makes sense now. After spending today using it, my gut reaction was to be sad that people will feel reluctant to throw a bunch of effort into replies that will immediately be hidden (as with Reddit). But after the server meltdown yesterday, it’s understandable. 14 years was a really good run. I suppose even lisp has its limits. :( Yeah, adding the descendant count would make it pretty good. Hard to think of anything better. I’ll be honest: I’m really worried this will become another tool for moderators to control discussions, while concealing the fact that it was a moderator (rather than algorithmic) decision. But no one can stop you if that’s the kind of control you want for your team. The flip side of that is, since 2018, your team has done a stellar job, as far as I can tell. I don’t know if something changed, but things seem calmer now. I can’t even recall the last worrisome moderator decision, and I’ve found myself arguing on your behalf more than once. Dunno. You’ll get it right; you usually do. Thanks for being welcoming about ideas, and good luck wrestling with transpilers and performance issues.
  - deleted 5y ago
    [deleted]
  - sillysaurusx 5y ago