A DEV comment streak can lose an old qualifying week
I expected a streak counter to remember which weeks had qualified. Reading Forem's Community Wellness code showed me a different design: it rebuilds the active streak from the comment and reaction rows that exist when the calculation runs. That means an old week can stop qualifying after the activity in that week is over. This is a source-code finding, not a claim that I have watched DEV revoke a…
The Community Wellness streak on DEV can be lost if an old qualifying week fails to meet the new criteria. The streak is not based on saved records, but is instead rebuilt from comment and reaction data at each calculation. This means that if a week's activity stops, or a qualifying reaction disappears, the streak can shorten even if the user continues to earn comments later.
The system looks back seven days at a time, with each seven-day period grouped into buckets. A bucket is qualified if it contains at least two comments within a fourteen-day window. The consecutive sequence of qualifying buckets determines the length of the streak. If a previously qualifying bucket loses its only qualifying reaction, it can fall below the threshold, breaking the streak. DEV's badge awarding system does not remove previously earned badges when the streak shortens.
This means that a loss of a single reaction can cause a streak to stop advancing. The streak is not preserved once calculated, so the awarding system is sensitive to changes in old data. To maintain a Community Wellness streak, users should actively participate throughout the week, responding to relevant comments. Participants should also avoid treating a streak of exactly two qualifying weeks as a guarantee, as the streak can be affected by changes to older data.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
