A score change on a public Reddit post is a displayed number at a moment in time, not a list of who voted or how. Reddit says it fuzzes some displayed votes, so differencing two snapshots cannot recover a voting sequence. The practical move is to capture the score with the time you saw it, note the fuzzing limit beside it, and treat the number as one observation rather than as a partner's approval or rejection.
Find public social profile clues with our TraceSeek app.
Start with a dated snapshot, not a vote count
Capture what is actually visible: the score as displayed, the time you observed it, and the public context of the post. Keep it as a single dated observation rather than a running total. This keeps the record accurate about what you saw, without implying you saw who acted. If you save a screenshot, note the time in the same step so the image and the clock stay connected. [Reddit: vote fuzzing]
- Record the displayed score, the date and the exact time you saw it
- Note the post title or a short description so the snapshot can be matched later
- Label the entry as a display reading, not a vote tally
Why differences between snapshots do not add up to votes
Reddit states that some displayed upvotes and downvotes are fuzzed, a deliberate perturbation intended to confuse spammers and cheaters. Because the display is intentionally unsettled, subtracting an earlier score from a later one does not reveal a clean sequence of individual votes. The arithmetic looks precise but rests on numbers the platform has said it adjusts. [Reddit: vote fuzzing]
| observation | limit | next step |
|---|---|---|
| Score was 41 at 9:10 and 44 at 9:40 | Fuzzing means the difference is not three verified votes | Record both readings with times and stop there |
| Score dropped by one after a reply appeared | Timing does not connect a reply to a vote | Keep the two facts separate; do not infer a reaction |
| Score held steady for a day | A steady display is not proof of stable interest | Note the reading; draw no conclusion about who read it |
Stop at the edge of what a score can show
A displayed score is not a record of identity, intent, or the state of a relationship. Treating a small change as approval or rejection by one particular person imports a claim the number cannot support. If you find yourself refreshing to watch the number move, that is a sign the snapshot has turned into a reconstruction attempt. Take one reading, write it down, and leave the refresh loop. [Reddit: vote fuzzing]
- Set one reading time instead of refreshing to watch changes
- Write the limit next to the number: displayed score, fuzzed, no voter detail
- Do not attribute the change to a specific person without a separate explicit statement
Keep observation, limit and decision on separate lines
A reader aid that separates these three keeps an inference check honest. On one line, write the observation exactly as displayed. On the second, write the limit that applies, such as the documented fuzzing. On the third, write the decision you can take without the missing vote detail. That third line is where the practical value sits: choosing what to do next does not require knowing who pressed a button. This worksheet is editorial guidance, not a platform feature.
- Observation: the score, the post, the date and time
- Limit: displayed scores can be fuzzed; no individual vote detail is available
- Decision: what you will do next, based only on what you actually need
When the public source is absent or ambiguous, record that and stop
Sometimes the post is deleted, the score is hidden, or the screenshot is cropped so the number and timestamp cannot be tied together. Write that precise limit instead of filling the gap with a guess. A missing score is not evidence of anything about voters, and an ambiguous one should not be stretched into a story about a partner's feelings. Stop the inference at the boundary of the visible artifact.
- Name the specific gap: score absent, time unknown, image cropped
- Do not substitute a later reading as though it were the original
- If no public artifact is available, end the exercise rather than seeking private access
Decisions that do not depend on the score
Most decisions a reader actually faces here can be made without the vote detail. If the question is whether to reply, wait for an explicit message rather than reading a score as a signal. If the question is whether a public post is being talked about, look at visible text, not at a shifting number. In each case, the decision rests on something stated or clearly visible, which is exactly what a fuzzed score is not. [Reddit: vote fuzzing]
A couple more questions
Can I work out who upvoted or downvoted by comparing two screenshots?
No. Reddit says some displayed votes are fuzzed to confuse spammers and cheaters, so adding and subtracting displayed scores cannot recover an individual voting sequence. Keep each reading as a dated display observation and do not use the difference as evidence about any person.
Is a small score drop a sign that someone disapproves of me?
A displayed score does not identify a voter or their intent, and fuzzing unsettles the number further. Treating a drop as one person's disapproval adds a claim the artifact cannot support. If you need to know how someone feels, rely on what they say directly.
What is the minimum useful record to keep?
The displayed score, the post it belongs to, and the date and time you saw it, plus a short note that displayed votes can be fuzzed. That record is honest about both what you observed and what the observation cannot establish.
Sources & editorial notes
Official references checked on October 24, 2026. Checklists, comparison tables and example wording are DateClues editorial tools, not official tests or validated risk scores.
General information. No guide or tool can certify a person’s identity, intentions or safety. Read our editorial standards.