6 ms·

Was this removed from the front page because Replit has taken money from Ycombinator? EDIT: Just to clarify. This post has gained over 200 points and 70 comme

Was this removed from the front page because Replit has taken money from Ycombinator? EDIT: Just to clarify. This post has gained over 200 points and 70 comments on the last hour. It jumped from top 5 posts to low end of the top 50 posts in seconds and is rapidly sinking. Just curious what decision led to the hiding of a popular post.

brhsagain 5y ago
I don't think so. https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=by%3Adang%20yc%20%22less%2C%20not%20more%22&sort=byDate&type=comment https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...
- yepthatsreality 5y ago
  That’s for the previous thread though. Unless I’m missing something every thing he says doesn’t necessarily apply to this thread.
  - dang 5y ago
    From my perspective it does apply. Please see my comment upthread: https://news.ycombinator.com/item?id=27439301 https://news.ycombinator.com/item?id=27439301. If there's something there you feel I haven't addressed, I'd be happy to hear what it is.
    - yepthatsreality 5y ago
      Thanks for your reply and explain.
minimaxir 5y ago
Usually updates are penalized, which this is.
- yepthatsreality 5y ago
  That makes sense. Infinite scroll and linking to the updates section made me think it was a new article.
dang 5y ago
This story was at #1 all day yesterday: https://news.ycombinator.com/item?id=27424195 https://news.ycombinator.com/item?id=27424195. Under normal circumstances we downweight indignation threads—we have to, because otherwise they would dominate HN's front page every single day, and that's not the kind of site HN is supposed to be. However, we moderate HN less, not more, when YC-funded startups are involved in a story (https://hn.algolia.com/?dateRange=all&page=0&prefix=false&query=by%3Adang%20moderate%20less%20%22not%20more%22%20yc&sort=byDate&type=comment https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...). In keeping with that principle, we took a hands-off approach with yesterday's thread. Today's post, however, is a follow-up to yesterday's. Indeed it's basically the same story. There are well-established moderation rules about that: repetition is bad for curiosity [1]; we downweight follow-ups [2] unless they add significant new information (SNI), defined as information capable of supporting a substantively different discussion [3]. Moderating HN less does not mean not moderating it at all—that would be a gigantic loophole. Having bent the rules drastically to accommodate yesterday's thread, I don't think it would serve the community to do the same thing all over again the next day. Indeed, we've gotten a significant number of emails about this post, asking us why it was on the front page when the same story was so prominent yesterday. That's because HN users are used to the site not being overly repetitive. People come to HN for new things and different things [4], and we need to take care to preserve that property. [1] https://hn.algolia.com/?dateRange=all&page=0&prefix=false&sort=byDate&type=comment&query=curiosity%20repetition%20by:dang https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so... [2] https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sort=byDate&type=comment&query=follow-up%20by%3Adang https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sor... [3] https://hn.algolia.com/?dateRange=all&page=0&prefix=false&sort=byDate&type=comment&query=%22significant%20new%20information%22%20by%3Adang https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so... [4] https://hn.algolia.com/?dateRange=all&page=0&prefix=false&sort=byDate&type=comment&query=diffs%20by:dang https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so... Edit: I posted a related comment at https://news.ycombinator.com/item?id=27439412 https://news.ycombinator.com/item?id=27439412.
- sillysaurusx 5y ago
  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.

brhsagain 5y ago

I don't think so. https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=by%3Adang%20yc%20%22less%2C%20not%20more%22&sort=byDate&type=comment https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...

yepthatsreality 5y ago
That’s for the previous thread though. Unless I’m missing something every thing he says doesn’t necessarily apply to this thread.
- dang 5y ago
  From my perspective it does apply. Please see my comment upthread: https://news.ycombinator.com/item?id=27439301 https://news.ycombinator.com/item?id=27439301. If there's something there you feel I haven't addressed, I'd be happy to hear what it is.
  - yepthatsreality 5y ago
    Thanks for your reply and explain.

minimaxir 5y ago

Usually updates are penalized, which this is.

yepthatsreality 5y ago
That makes sense. Infinite scroll and linking to the updates section made me think it was a new article.

dang 5y ago

This story was at #1 all day yesterday: https://news.ycombinator.com/item?id=27424195 https://news.ycombinator.com/item?id=27424195. Under normal circumstances we downweight indignation threads—we have to, because otherwise they would dominate HN's front page every single day, and that's not the kind of site HN is supposed to be. However, we moderate HN less, not more, when YC-funded startups are involved in a story (https://hn.algolia.com/?dateRange=all&page=0&prefix=false&query=by%3Adang%20moderate%20less%20%22not%20more%22%20yc&sort=byDate&type=comment https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...). In keeping with that principle, we took a hands-off approach with yesterday's thread. Today's post, however, is a follow-up to yesterday's. Indeed it's basically the same story. There are well-established moderation rules about that: repetition is bad for curiosity [1]; we downweight follow-ups [2] unless they add significant new information (SNI), defined as information capable of supporting a substantively different discussion [3]. Moderating HN less does not mean not moderating it at all—that would be a gigantic loophole. Having bent the rules drastically to accommodate yesterday's thread, I don't think it would serve the community to do the same thing all over again the next day. Indeed, we've gotten a significant number of emails about this post, asking us why it was on the front page when the same story was so prominent yesterday. That's because HN users are used to the site not being overly repetitive. People come to HN for new things and different things [4], and we need to take care to preserve that property. [1] https://hn.algolia.com/?dateRange=all&page=0&prefix=false&sort=byDate&type=comment&query=curiosity%20repetition%20by:dang https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so... [2] https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sort=byDate&type=comment&query=follow-up%20by%3Adang https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sor... [3] https://hn.algolia.com/?dateRange=all&page=0&prefix=false&sort=byDate&type=comment&query=%22significant%20new%20information%22%20by%3Adang https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so... [4] https://hn.algolia.com/?dateRange=all&page=0&prefix=false&sort=byDate&type=comment&query=diffs%20by:dang https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so... Edit: I posted a related comment at https://news.ycombinator.com/item?id=27439412 https://news.ycombinator.com/item?id=27439412.

sillysaurusx 5y ago
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.