The Hacker News New Page Scroll of Death and Some Possible Solutions
almostinfinite.com
almostinfinite.com
So, for instance, let's say there are 9 new posts in the "queue" and there are 3 concurrent visitors to the front page. Visitor A will see links 1-3 from the new queue, visitor B will see links 4-6, etc. After being shown at least 3 times to front page visitors the link get's dropped from the new queue if it did not gather a single up vote. However, if it does get an up vote, that also resets it's show counter, and it has 3 more chances to gather another up vote.
The number of showings (lives) can be adjusted based on the ratio of new submissions to front page visitors. But I suspect that that ratio is more than high enough to accommodate 3-5 showings.
I feel like this would be a relatively easy system to implement, and could result in better overall content. Thoughts?
I would make one suggestion: On each page load, randomly select three stories to display from those submitted within the last 60 minutes, instead of selecting the stories using the algorithm outlined above. If there is a problem with too many people submitting too many garbage/spammy stories, perhaps that problem can be solved by considering downvotes or flags (i.e., an affirmative action that the story isn't good) rather than a simple lack of upvotes (which could happen from people simply not taking a look at the story).
Though it might also mean that scores will be more variable for new submissions, and that may have an impact on front-page/2nd-page variability and bounciness, which doesn't seem like it would be friendly to casual users.
We didn't roll this out to everybody, but we did enough to conclude that it isn't a good way for HN to solve this problem.
My simple reason: It doesn't have an RSS/Atom feed.
I have it open right now and I count: 5 [dead] stories; 2 stories about Microsoft following Netlix's lead on leave; 2 stories from linkedin.com; Captain America appears to be joining Twitter as head of security (I didn't know that Hydra had threatened them); and no headlines that interest me.
With the system outlined in my original post everyone could very easily contribute to HNs ranking system without spending too much time on it. Worst case, you have to look at 3 crappy article titles, that's not that bad.
A separate /new list won't make a difference because it won't improve the average content quality. Not everything submitted to HN "deserves" to receive upvotes, to be perfectly honest.
Personally, I've had a number of submissions get upvotes after it's fallen off the first page of /new. I admit it's counterintuitive, though.
This is certainly true. It is also the case that some things submitted to HN deserve upvotes and don't get them. A case in point, this very article:
Try #1: https://news.ycombinator.com/item?id=10007658
==> 4 points by curtis 17 hours ago | discuss
Try #2: https://news.ycombinator.com/item?id=10011219 (this submission)
==> 42 points by curtis 2 hours ago | 18 comments
The obvious conclusion is that the first submission didn't get upvotes just because it wasn't very good -- it simply didn't deserve them. And the second submission got upvotes because it was better. It was quality content. But of course in this example, they're the same article!Now let me be clear. I understand that it is the nature of this particular beast that there is simply going to be a lot of randomness. However, I believe we can make it noticeably less random with some fairly modest effort. And if we can make it less random, then I think that would be a good thing. Would the proposed "preview" page actually do that? I don't know. But I certainly think it's worth talking about.
It might be because of the experimental story-rescuing program I've written about at https://news.ycombinator.com/item?id=9866140 and https://news.ycombinator.com/item?id=8790134.
It's especially true on 'Show HN' and 'Ask HN' posts, since they appear for a longer period of time in the other sections.
Not entirely convinced that you can draw that conclusion from that plot. 10+ votes articles percentage might increase with the number of readers online, but so will the percentage of votes on other articles, hence 10+ voted articles != popular front page article. I think that 10+ votes may be a wrong way to look at it.
https://github.com/reddit/reddit/blob/c6f959504466333c0d7d51...
The HN algorithm has temporal-gravity to help pull down old content that wasn't hugely popular. Due to that algorithm if the content doesn't take off in the first hour, it likely won't take off.
Those 2 points point to a far simpler solution. Just show most of the items from the last hour on the new page. So instead of 30 items, you show 100 items on the new page, which should accommodate most of the recent posts without requiring any clicks.
(minimaxir's point is also very valid.)
Someone else suggested this recently, and we've heard it before, too. We're game to try it as an experiment.
What's the best way to measure whether it works?
That is, we know it's that "articles that should be on the front page get overlooked"—but votes are the main metric we have for what should be on the front page. How can we tell an article that fell off /new because it was bad from one that fell off because nobody saw it?
One way of evaluating this would be to exercise editorial discretion, pick out articles you (or some set of people) believe are good and compare how they progress with different versions of the page. However, this is rather labor intensive and risks biasing the experiment based on who picks the articles out.
I can't think of other approaches off-hand. Coming up with a concrete statement of the problem would probably help here.
Upvotes alone don't determine HN's front page. If they did, HN would be dominated by controversy, gossip, and fashion—those get the most reflexive upvotes, and there are more reflexive upvotes than reflective ones. Coutervailing mechanisms include flagging and moderation.
The fundamental difficulty is that HN cares most about quality and one can't easily measure that or automate it. Human curation is needed, plus humans don't always agree about what counts as high-quality.
Anyone who wants to know about our current approach to this problem should read https://news.ycombinator.com/item?id=9866140 and https://news.ycombinator.com/item?id=8790134.
If, as it seems, there's no objective standard for quality (since it can't be measured or defined) then maybe subjective filters are the way to go.
On the question of how objective vs. subjective HN's notion of quality is, I don't think it's completely subjective. Everyone has their personal tastes, but HN's standards are reasonably well-established too. So I still think we may be able to come up with a story curating mechanism to supplement upvoting that is open to any user who wants to put in the effort. The big question, again, is how to score the effort. It can't be just "vote for whatever you like," because we already have that.
That said, it seems that HN has grown so big, many "top stories" don't get enough time for discussion before completely disappearing from the front page. It might be time (shudder the thought) to introduce channels...
It would be also much easier to implement.
Why do you say that? We've put a ton of work into that problem, which is not quite as simple as you'd think.
Just wanted to first say that I absolutely have enjoyed your work and time on HN, but from my experience as a user (important distinction here), the mobile interface hasn't changed much in the last few years.
The only thing I see is a slightly bigger triangle button and a whole lot of tiny tiny text. I completely understand that my phone isn't the target audience (S3), and so I use an Android app to make up the difference, but when I saw your comment I reopened HN on my phone to see if had improved since I had last checked a year ago.
Here's what I saw: http://i.imgur.com/CRonP5c.png I am NOT a UX expert (or even novitiate) but if you would, compare the size of the refresh button to the size of the upvote or comments buttons and notice the vast difference in area.
I took the liberty of coloring in the comment link in red, and comparing it to the refresh button: http://i.imgur.com/GZEs7cN.png and that it is less than 1/10th of the same clickable area.
Now, I am 100% not saying you should be targeting this button size or that specifically, but that would be a reason I would make this type of comment.
Hopefully that isnt too frustrating of a response, I assume there are a lot of factors going on that I am not aware of.
Thanks.
We did make a couple attempts at quick fixes for HN on mobile that provoked howls of protest, so we rolled those back and have been working instead on rewriting HN's markup entirely. This is not a small project, and everyone working on it has other responsibilities, so it has taken a long time. It is, however, getting closer to being ready. That's why I objected to the statement that we "aren't even about to fix" it (and also that it's a "simple" problem)!
When we do have something ready, we'll release it for a while as a different set of URLs and start taking everyone's feedback about what still doesn't work right. I imagine there will be a long process of tweaking it, and we'll be happy to do that over time.
(Also, that was very nice of you to be so friendly even though it sounded like I was saying something silly.)
It's also worth noting that HN could interleave new submissions into the front page to get them more visibility, forgoing a preview type page altogether.