id
gotchas/sent-vote-counts-are-a-popularity-proxy-not-a-measurement
Concepts
upvotehn-pointspopularity-proxymethodologysampling-bias
Symptom
Every quantitative claim about community sentiment in this slice carries an upvote or Hacker News point count, and the risk is that a reader treats those numbers as results. They are not. A 182-upvote one-line reply on a 103-upvote post is not 'the community prefers X by a factor of 1.8'. Vote counts measure who has the time to write a comment that ranks, they drift after access, they are adversarially gameable, and on a subreddit like r/LocalLLaMA they are correlated with posting frequency rather than with operator experience. Hacker News points have the same property with different mechanics. Every source record in this slice carries kind: forum, status: verified only in the sense that the quoted text was read at the cited URL on the cited date.
Root cause
The fix is procedural rather than statistical. Preference claims are recorded as attributed quotes with a date and an observed vote count, the count is labelled a proxy in the record's notes, and where sentiment is divided the record states the shape of the split instead of a share. No record in this slice converts a vote count into a percentage, and no record claims a vote count is representative.
Workaround
Read a vote count as 'this argument was visible to a lot of people on this date', which is a real signal about which arguments practitioners are actually arguing about. Do not use it to weight advice, and do not use this slice to make a quantitative claim about the community's beliefs. Where a practitioner states a number - five concurrent users, four users, twelve patches - that number is recorded as their statement with the caveat that it is a rule of thumb, not a measurement this repo has verified.
notes
This is the record that makes the rest of the slice honest, and the one most likely to be needed by a future slice. Two places where it already changed what was written: the Strix Halo split records the shape rather than a share, and the engine records record the refusal of a ranking as the finding rather than inventing a ranked list from scattered votes. Sampling caveat stated plainly: the corpus is heavily weighted to r/LocalLLaMA, because that is where practitioner buy/sell reasoning about hardware is discussed in public. r/MachineLearning was searched and returned no hardware-buying threads in the access window; its high-scoring threads are link shares and career discussion. So 'the community' in this slice means the self-hosted-inference community, and the bias toward hobbyist-scale builds is real.