Live data from Hacker News

Hacker News Ranking Algorithm

vigneshwarar.substack.com

51–60 of 82 posts

Re: Hacker News Ranking Algorithm

#51
post #49

I think the article ranking is probably good enough. Where I have more trouble with is with comment-ranking within an article. The interface makes it hard to understand conversational flow, and of course that flow changes over time according to whatever the algorithm does. This makes it very hard to catch up later on an article’s comments and get a view of what has changed since my last view. Maybe there is a way to…

> This makes it very hard to catch up later on an article’s comments My biggest complaint related to this is that all threads are dead within 24 hours, which kills a lot of interesting discussion. And commenters have no incentive to reply to dead threads. This discourages in depth back and forth conversation which I usually find is the most interesting.

Admittedly, it varies, but I tend to look back for responses to older discussions if it was an interesting engagement to me. I agree with you that long form discussion suffers from current format, but I think it is part of the deal. It is hacker news and not hacker discussions.

TBH, I am not sure if there is a good non-invite-only forum that facilitates that.

Re: Hacker News Ranking Algorithm

#52

I don't understand this blog post. The authors says that HN is great for discussions. Then they go on to suggest a different ranking algorithm? Why? To answer the authors question: I would change absolutely nothing about HN. It's great for discussions as is. Edit: I suppose there is some insinuation that HN doesn't really use the original algorithm, and this is the author's attempt to reconstruct what's going on. Is…

Well, the article is something of an ad. The author discusses current ranking and effectively proves that it could be gamed to an extent ( author links his non-SEO search engine, which obviously you cannot do unless you are deep into SEO stuff, which includes HN ranking algorithm ). The complaint is mildly self-serving, but only mildly so. FWIW, it worked on me.

Still, I will echo what others said. Despite my grievances with HN at times, don't change what ain't broken.

Re: Hacker News Ranking Algorithm

#53
post #45
post #27

Earlier quoted context omitted.

Is it working? Post ranking works pretty well, but as far as discussions go I often see insightful responses sent into low-contrast oblivion whilst a glib comment or quip gets accolades.

Two big issues I've noticed with post ranking are: 1. There seems to be a group of people that abuse the flag button to get stories downvoted. You notice this when highly upvoted stories with a lot of points suddenly drop from the top and fall quickly beyond older stories with many fewer votes. For instance, there seems to be a group that was mass flagging submissions about Rob Lee's recent death until one was made t…

> There seems to be a group of people that abuse the flag button…until one was made that didn't mention his cause of death

I’m not sure that I’d characterize this as abuse. HN stays interesting by avoiding flame bait topics and part of the realization of the community guidelines happens via this flag feature.

One way to reframe #1 is that the community’s self-moderation features are working as designed, and that any post about Bob Lee’s death that somehow editorializes it or positions it in a way that is likely to lead to political debates is against the site guidelines and thus were removed appropriately.

Regarding #2, this has happened to me more than once, and while frustrating, it made me think more about posts I encounter before commenting. When a post fits the criteria for “potential flame war” or “clearly outside of site guidelines”, I flag it instead of commenting, even if I know that at the core, the topic could be an interesting one. Most things get posted more than once, and usually at least one of the posts is within guidelines.

When I do lose a comment to a flagged post, I’ll reuse it in a more level headed discussion about the topic.

Re: Hacker News Ranking Algorithm

#54
I am often faced with a dilemma when trying to decide whether to vote on a particular post or comment. There are times when it is very informative, well written, and you can tell a lot of thought went into it; but I happen to disagree with the author's point of view. The same occurs when I agree with the author's sentiment, but the comment itself is poorly written and not well argued.

There is only a single up/down vote. You can't upvote a thoughtful comment for its quality, while also downvoting its conclusion. Sometimes I have strong opinions about something; but I also try to educate myself with the other side of the issue by reading thoughtful articles and/or comments from people with different points of view.

It would be nice if you could choose between two different 'modes' in the interface. One where the highest quality comments are near the top. The other where the most popular viewpoints are prioritized.

Re: Hacker News Ranking Algorithm

#55
post #53
post #45

Earlier quoted context omitted.

Two big issues I've noticed with post ranking are: 1. There seems to be a group of people that abuse the flag button to get stories downvoted. You notice this when highly upvoted stories with a lot of points suddenly drop from the top and fall quickly beyond older stories with many fewer votes. For instance, there seems to be a group that was mass flagging submissions about Rob Lee's recent death until one was made t…

> There seems to be a group of people that abuse the flag button…until one was made that didn't mention his cause of death I’m not sure that I’d characterize this as abuse. HN stays interesting by avoiding flame bait topics and part of the realization of the community guidelines happens via this flag feature. One way to reframe #1 is that the community’s self-moderation features are working as designed, and that any…

> that any post about Bob Lee’s death that somehow editorializes it or positions it in a way that is likely to lead to political debates is against the site guidelines and thus were removed appropriately.

A lot of discussions on HN lead to discussions of government policies (both U.S. and foreign) when there's a connection to the story, including saying that certain policies lead to the death of individuals. There's only a subset that gets mass flagged. If he was shot to death by police at a protest, killed by a U.S. military strike in another country, died as a result of a mass Covid surge, stories mentioning the reason for his death wouldn't be mass flagged. People wouldn't be forbidden from mentioning the causes of death on the only one that isn't, and it wouldn't be dismissed as "political flamebait."

If Hacker News decides that discussion about government policies is off limits, that's fine. It might even make discussions better. But allowing it in some situations and having it "removed appropriately" in others is only reinforcing bias. I think characterizing that as abuse is appropriate.

Edit: If you want to see an example, look at the Hacker News discussion about the death of Aaron Swartz. The cause of death isn't hidden, and there's a lot of criticism of the government, none of which is getting dismissed as editorializing or political flamebait[1].

[1] https://news.ycombinator.com/item?id=5046845

Re: Hacker News Ranking Algorithm

#56
post #15

I don't understand this blog post. The authors says that HN is great for discussions. Then they go on to suggest a different ranking algorithm? Why? To answer the authors question: I would change absolutely nothing about HN. It's great for discussions as is. Edit: I suppose there is some insinuation that HN doesn't really use the original algorithm, and this is the author's attempt to reconstruct what's going on. Is…

If it works, don't fix it. You'll most likely break it.

This is Hacker News. Over engineering things is part of our cultural heritage.

Re: Hacker News Ranking Algorithm

#57
We may be getting to the point where we can directly predict the quality, interestingness, and originality of a comment before it has a chance to receive viewer feedback. This would be similar to how we can now rank historical chess players according to how chess bots evaluate their moves. A forum could then start comments off where it approximates their rank will end up, and then potentially let viewer feedback take over from there.

What's more: if you can't stop bots from dominating your signal, then directly predicting things like quality may be one of the only good options left.

Re: Hacker News Ranking Algorithm

#58
Two obvious points: why not machine learning, and a more explicit mix of exploration and exploitation

Meaning give more posts a chance, a certain number of views to determine the upvote rate.

Conventional wisdom would apply spam filter, boost new users (e.g. first post), detect blatant manipulation (or more sophisticated manipulation using clustering).

Re: Hacker News Ranking Algorithm

#59
post #5

Using page rank as suggested by OP, would provide weird incentives like frequent comments, or higher volume, could rank a person higher than if they had occasional comments further down the thread. If OP is interested in the most influential commenters, people who write frequently and have a posse, then PR would be a good way to do it. What would happen to a helpful comment from a throwaway account? If there's more o…

"…would provide weird incentives like frequent comments, or higher volume, could rank a person higher than if they had occasional comments further down the thread."

I know I'll be out of step with most who comment on HN but I question the necessity of having a ranking/voting system at all. All it seems to do is to act as an ego booter for commentators and it messes up orderly discussion when people insist on posting replies to the first commentator.

As a news aggregator, no doubt HN needs some method of ranking stories to set their listing lifetimes and their importance (page ranking) but that could be accomplished by the number of clicks a storey receives and or how long a visitor/commentator stays on a story (or the time between link clicks).

I also question aspects of the voting system as currently implemented. It's not unusual for me to receive down-votes on comments to controversial stores but not receive a comment from the down-voter. Why bother with this system if the voter hasn't the gumption to say why he/she disagrees with one's views? (One could discuss the psychology and social philosophy behind this but here is not the place).

Another annoyingly aspect of the voting system is the lack of stats. The time I take from posting to checking to see if someone has replied varies wildly—from minutes to days to never. This wide variation is significant when I post to controversial stores. Days later I can check back to see if there's been any votes or replies only to find there has been none.

At other times, I've monitored the incoming votes almost in realtime and watched them oscillate around 0 or 1, that is I've received many up and down votes but the long-term average is zero. Come back and check days later and one hasn't a clue from the stats if anyone at all has actually read one's comment let alone the fact that it was equally controversial to both sides of a polarized audience. HN should allow users access to these long-term stats.

Re: Hacker News Ranking Algorithm

#60

I am often faced with a dilemma when trying to decide whether to vote on a particular post or comment. There are times when it is very informative, well written, and you can tell a lot of thought went into it; but I happen to disagree with the author's point of view. The same occurs when I agree with the author's sentiment, but the comment itself is poorly written and not well argued. There is only a single up/down v…

I upvoted your comment on both criteria. It would be very useful to have 2 dimensions. It's amazing nobody does afaik!

@dang, as a Arc expert, let me assure it's only 4 lines of code, 1 field on db, 52 bytes of js, css, and html, and it won't cause performance, security, accessibility, privacy, or usability issues /s

Post reply on HN