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.
Post History
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...
#3: Post edited
by
matthewsnyder
·
2023-08-08T17:36:39Z (about 1 year ago)
- 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: An answer accepted in 2013 may be obsolete, but the asking account is inactive, and basically it will never get corrected - 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.
- 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.
#2: Post edited
by
matthewsnyder
·
2023-08-08T17:34:13Z (about 1 year ago)
- 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: An answer accepted in 2013 may be obsolete, but the asking account is inactive, and basically it will never get corrected - 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. `t1` 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.
- 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: An answer accepted in 2013 may be obsolete, but the asking account is inactive, and basically it will never get corrected - 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.
#1: Initial revision
by
matthewsnyder
·
2023-08-08T16:44:26Z (about 1 year ago)
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: An answer accepted in 2013 may be obsolete, but the asking account is inactive, and basically it will never get corrected - 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. `t1` 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.