Blog ·
The 800-character rule: why long reviews beat thumbs
RepoRanker enforces a minimum of 800 characters on every review. That number was chosen deliberately, not arbitrarily, and the reasoning is worth writing down because it is the most important rule on the platform. Everything else (the 48-hour dispute window, the credit economy, the published ranking rules) follows from it.
What 800 characters actually looks like
Most internet feedback is well under 100 characters. A Twitter reply averages 50. A GitHub thumbs-up is zero. A Hacker News comment that says "interesting!" is 12. The median Product Hunt comment is around 80.
800 characters is roughly two short paragraphs. It is also, not coincidentally, about the minimum length needed to:
- Describe what a project does in your own words
- Note who you think it’s for
- Say what you tried and what happened
- Identify at least one thing that worked and one thing that didn’t
- Land a verdict
Anything shorter than that and you are skipping at least one of the five. Anything longer is welcome (the average review on RepoRanker is closer to 1,400 characters), but 800 is the floor for "this person actually used the project."
Why the minimum exists
Three reasons, in order of weight.
1. It filters drive-by reviews
The single biggest predictor of low-quality feedback on every platform that has tried review systems is low effort cost to write a review. When the cost is zero (an upvote, a thumb, a star), the system is dominated by people clicking on launch day and then never coming back. The signal-to-noise ratio collapses inside a week.
Raising the floor to 800 characters is not a fence against criticism. It is a fence against contribution-free opinion. If you have an honest negative review of a project, 800 characters is easy. If you don’t actually have anything to say, 800 characters is hard. The system selects for the first.
2. It calibrates the credit economy
RepoRanker pays 10 credits for each released review. Credits buy boosts on your own projects starting at 20 credits for 24 hours of leaderboard pinning. The economy is supposed to reward contribution proportionate to its value. If reviews could be one-liners, the credit-per-character math would be wildly inflated and the system would devolve into a karma farm. With 800 characters as the floor, the economy stays calibrated: you put in real work, you get real visibility back.
3. It’s the unit AI doesn’t fake well
This is the part that matters in 2026. AI-generated reviews of arbitrary repos are now a five-second prompt away. Most of them are mediocre to bad: paragraph-pattern matching with no grounding in the actual code, generic platitudes that could apply to any project, no specific file paths or function names because the AI didn’t look at the source.
An 800-character minimum doesn’t stop AI-generated reviews on its own. But it makes them identifiable: AI reviews padded to 800 characters read like AI reviews padded to 800 characters, and they are dispute-eligible under our content policy. The minimum forces the question: did you actually engage with this code, or did you outsource the engagement?
What 800 characters does NOT do
The minimum is a floor, not a ceiling. It does not:
- Guarantee a review is good (you can pad 800 characters of nothing if you really try)
- Prevent dishonest reviews (the dispute window does that)
- Replace moderation (the content policy does that)
- Stop drive-by upvotes (we just don’t have upvotes)
It does, however, raise the bar enough that the median review on RepoRanker is more useful than the median comment on any of the platforms we’re positioned against. That is the whole point.
Other platforms’ floors, for comparison
- Product Hunt: no minimum on comments, mostly emoji reactions
- GitHub Trending: no review system, just stars (zero characters)
- Hacker News: no minimum, but moderation is real and karma matters
- Awesome lists: no review, just maintainer-curated inclusion
- RepoRanker: 800 characters, GitHub-verified, 48-hour dispute window
None of those other platforms is wrong for what they’re trying to do. They are just trying to do different things. Stars and upvotes are great for "what is hot right now." 800-character peer reviews are great for "is this project worth my time, six months after the launch hype faded."
Try writing one
The fastest way to internalize the 800-character rule is to write one. Pick a project you’ve actually used. Open the{" "} leaderboard, find it (or a similar one), and write 800 characters of honest peer review. You’ll get 10 credits when it releases after the dispute window. You’ll also discover that writing a real review is harder than you thought and more useful to the maintainer than you expected.
Sign in with GitHub to start.
Related: How it works · Trust & moderation · Content policy.
