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_maxfor each reaction. This indicates the CD devs' best guess for how long that reaction is relevant for.t_maxcan 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 …
9mo ago
Argument against Quite simply, none of the available reactions has a clear and pressing need for such a marking …
9mo 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 …
9mo ago
Post
Wary of trying to be too general
Although I like the idea of this for making sure indications of interest don't last indefinitely on Codidact Proposals, trying to find a general use for expiring reactions on existing Codidact communities might end up stretching one tool across too many use cases. Perhaps we would be better with several different solutions for different problems.
Alternative solutions for proposals
This has made me think about how else we could measure interest in a proposal without needing to modify the reactions system.
Measuring activity rather than intentions
Even with expiring reactions, a user who claims they will be a user of the proposed community may turn out to not be interested enough to interact often. Keeping a reaction on a proposal up to date by regularly visiting is much less effort than making meaningful interactions like voting, posting, and editing. Perhaps we should focus more on measuring directly how much activity a proposal is seeing.
Now that proposals are in a community of their own, with questions and answers and their own Meta category, we get a much better impression of the activity a finished community would see, because much of that activity can already happen in the proposal. Could we add statistics to proposals that show how much of each activity type is happening? This would show what people are already doing for that proposal, rather than what they claim they will do in the future.
Charts in the Descriptions post
This could be hosted in the Descriptions post for a proposal, as a collection of charts showing different types of activity. Possible charts could be:
- Number of views (of questions attached to the proposal, the proposal's tag, and the proposal's Descriptions post).
- Number of questions.
- Number of answers.
- Number of unanswered questions.
- Number of votes cast.
Each of these could be shown against time, so we can easily see if a proposal has steady activity or just a spike in the first month and then less (or a steady increase over time).
1 comment thread