How Comments Get Ordered

Veridonia launched without a comments section. That was deliberate. We wanted to know whether a community-decided feed was worth building before we added the part of social platforms that tends to go wrong most reliably. People wanted to discuss what they read, which was no surprise, so we built comments. The harder question was not whether to have them, but how to order them.

Which comment sits at the top of a thread is a smaller version of the same problem as which post reaches the feed, and it deserves the same care. We were not going to spend a year improving the signal of the feed and then hand it back with a like button under every comment. The default everywhere is to sort comments by likes or upvotes. It looks fair and it is easy to build. It also fails in specific ways, and in comments those failures are sharper than almost anywhere else.

What likes and upvotes do to comments

The first failure is that early comments win regardless of quality. A comment posted in the first seconds of a thread gathers votes while everyone is looking. A better comment posted an hour later arrives to a page already sorted against it. Visibility earns votes and votes earn visibility, so the order mostly records who arrived first. This is the same path-dependence we describe for the feed in what makes our voting more democratic, and it is worse in a comment thread, where the good replies often come later, once people have had time to think.

The rest follow from the button itself. A like asks nothing definite: pressing it can mean you agree, that it amused you, or that you think more people should see it, and the system records the same signal each way. Anyone can like whatever they choose, which makes the order cheap to buy, since pointing enough accounts at your own comment is all it takes. And most systems show you the score before you vote, so when one comment already has five hundred likes and another has five, you stop judging the comments and start agreeing with a number.

And where a platform adds a downvote, the button turns into a way to punish rather than to sort. A downvote is disapproval aimed at the person, and with the count on display it becomes a public verdict: a comment does not just rank low, it gets dogpiled. The ordering mechanism itself hands people a tool for hostility.

What the order is supposed to mean

It helps to step back from the mechanism and ask what the order is meant to represent. It is not a count of how many people pressed a button. It is a claim about which comments the community finds more worth reading than the others. That is a statement about comments relative to each other, and the honest way to arrive at a relative order is to compare them, not to tally reactions to each one on its own.

Comparing, not counting

So that is what Veridonia does. Comments sit in a hierarchy, and when you open a level of a thread there is a chance you will be shown two of its comments and asked one question: which of these should more people see. You are not rating a comment on its own and you are not pressing a like. You are choosing between two. The pairs are drawn at random, with a slight preference for comments that have been compared the least, so a new comment is put in front of readers instead of waiting at the bottom for attention it would never get. The running scores stay hidden while you decide, so you are weighing the two comments in front of you and nothing else. Enough of these small comparisons settle, through a chess-style rating, into one stable order for the thread. For now you are asked to compare once per level, which keeps the request light.

What comparison buys

Each of the earlier problems has an answer in this. Because you cannot choose which comments you vote on, moving the result gets expensive: it is no longer enough to send accounts to like your own comment, because you would have to keep winning randomly drawn match-ups, which takes far more than a handful of votes. The same logic that makes the feed costly to manipulate is at work here, and we go through it in why bot attacks are more expensive here. Because the question is fixed, the vote means one thing, visibility, rather than agreement or applause. And because the pairs are random, weighted toward the less-seen, and scored behind a curtain, a strong late comment gets a fair hearing instead of losing to whatever was posted first.

It is also a quieter act. There is no downvote, and the tallies stay hidden, so you cannot punish a comment or pile onto it. You only choose, in private, which of two is more worth seeing. A comment that loses is simply not promoted, not publicly disliked for everyone to count. The ordering does its work without handing anyone a way to be hostile.

There is a cost, and it is worth saying plainly. A like takes one comment and one tap. A comparison takes two comments and a moment of judgement. That is more work. We think it is a small price for an order that reflects what people actually consider better rather than what they happened to see first, but it is a real tradeoff, and not everyone will make it the way we did.

Why posts are not decided this way

Comments are not ordered the way posts are published, and the difference is deliberate. A post faces a yes-or-no decision: a randomly selected panel votes on whether it belongs in the feed, and the result holds. Comments are not a yes-or-no question. They are a list that needs an order. A decision is the right tool for the first and a comparison is the right tool for the second, which is why the two halves of the system work differently on purpose. The post side is described in how our voting and rating work.

The aim is plain: the comments worth reading should rise because people compared them, not because they arrived first.