Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Comments on Indicate stale reactions based on user activity
Parent
Indicate stale reactions based on user activity
Reactions are currently used on CD to:
- Confirm an answer worked (similar to accepting an answer on SO)
- Show that an answer is dangerous
- Indicate interest in participating in a proposed CD site
Some of these have enduring meaning. For example, if rm -rf *
was dangerous 50 years ago, it is still dangerous now. Others go stale. For example, if I indicate that I would be a casual user of a proposal, and then forget CD exists for the next 3 years, that reaction is not as meaningful as a fresh one. Another example: A Python 2 answer may have been accepted in 2010, with the asking account now inactive, and basically it will never get corrected even though Python 2 is now obsolete - this became a significant occasional problem on SO after some years.
My solution:
- Define a time horizon
t_max
for each reaction. This indicates the CD devs' best guess for how long that reaction is relevant for.t_max
can be infinity. - When displaying reactions, check
t_age
: how long it's been since the user's last login. - If the
t_age > t_max
, display the reaction as "stale" or "old" and grey it out in the UI (halve the saturation?). Each stale reaction should also have mouse over text like "Reactions made by accounts which have not been active in over 30 days".
This is a live calculation, in that stale reactions can become fresh again when the user logs in after a long hiatus.
This system can be gamed by writing a script that logs in every day, to artificially keep your own reactions fresh indefinitely. I don't think anybody will bother for a long time.
I would prefer to give readers information rather than infer conclusions (sometimes right, sometimes not). We have an ex …
1y ago
Argument against Quite simply, none of the available reactions has a clear and pressing need for such a marking …
1y ago
Wary of trying to be too general Although I like the idea of this for making sure indications of interest don't last in …
1y ago
Post
I would prefer to give readers information rather than infer conclusions (sometimes right, sometimes not). We have an existing request to show reactions in history somehow -- specifically, readers need to know if that outdated/dangerous reaction was before or after a substantial edit.
Maybe we can add the timestamp of the newest reaction (of a type) to the tooltip when viewing the reaction?
1 comment thread