Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

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 More answer feedback -- Reactions are coming to Codidact

Parent

More answer feedback -- Reactions are coming to Codidact

+13
−0

A bit over a year ago, I proposed to add a “reactions” like feature on Codidact, which would allow marking answers as “accepted”, “outdated” or “dangerous”, providing more detailed feedback to users seeing the answer than simple votes. For example, a upvote could mean “this works for me” or “this sounds plausible” or “I like the method used in this post”, and a downvote could mean “this didn’t work”, “this is dangerous”, “this is outdated” or “I just don’t like the method used in this post” or anything else.

Well, I’m happy to say that we implemented that proposal and built reactions as a way for more specific feedback. Here’s how it works:

When you look at a post for which reactions are enabled (which depends on the post type and community), you’ll see a little “react” button below the voting arrows. If you click on that button, a drop out panel will open, in which you can select the reaction you want to add and, required for some reactions, optionally for the others, a comment text. Click on the “Add reaction” button to apply the reaction and post the comment (if not there already, a new thread named like the reaction will be added).

Reactions added to a post are shown above it; the display includes a list of people who have added this type of reaction. If more than 3 people reacted in the same way, further names will be cut off. More details, including a full list of people using that reaction on that post, will be shown in a dialog window if you click on the reaction.

By default, all communities will have the following reaction types [1]:

  • Works for me

    Use this reaction on answers (or, for example, explanatory articles) that provide a solution you have tested and confirmed to work for you.

  • Outdated

    Use this reaction on answers which contain an outdated solution that is either not working anymore or which only works with older versions of a system used.

  • Dangerous

    Use this reaction on answers that propose to do something which is dangerous and should either not be done at all or only by people with the necessary practice and experience. A comment is required explaining the danger.

Moderators on any community can configure these reaction types and also add more if deemed necessary. There are some things to consider though:

  • Reaction types, once created, cannot be deleted, only deactivated.

  • Reactions are designed as an addition to voting, not as a substitute; communities should therefore refrain from adopting reaction types that are not providing any substantial value aside from marking a post as “good” or “bad” (good example: difficulty reactions on a Cooking site, bad example: “I like that” or “I don’t like that” reactions).

  • Reactions, in order to be used effectively, need to be used sparingly. There is no good in thousands of “emoji reactions” that some other places on the Internet have (at least not for a Q&A site); hence only reactions that are absolutely needed should be added.

  • Therefore, Reaction types should only be added after some discussion in the community Meta category

Reaction types can be limited to a post type (such as Questions, Answers, Articles, Wiki, …) and post types can be limited to only specific reactions. This should provide enough flexibility while also preventing too much complexity. If mods need support with the configuration, we’re happy to help, please contact us via email or, preferably, in the mod lounge of the community chat server. If it’s nothing sensitive, you could also ask on Meta.

As always: Try it out and, if you find bugs or have feedback, reply in an answer to this post or write a new question. We’ll also observe how this affects comment and voting activity.


  1. There's a rumor that someone added a secret reaction called “too many commas” in order to make fun of me. I’m neither confirming nor denying that rumor. ↩︎

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

Does these options make sense in Meta? (9 comments)
Post
+6
−0

Bug

There is no way to cancel/discard reaction's box after it was opened.

reaction's box


Edit:

Feature-request

This is not a bug as I thought initially, that's good but the way it's implemented isn't obvious in a current form indeed.

I think an additional button with clear "Close"/"Dismiss" will make ui/ux better. Or least add an hover effect to see a "response" from the toggle.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

"React" control is a toggle. (4 comments)
"React" control is a toggle.
Monica Cellio‭ wrote about 3 years ago

You can dismiss it by clicking on the "react" link under the voting buttons again. This is like flags, close, the inbox, etc -- not super-obvious, but yes you can get rid of it again.

FoggyFinder‭ wrote about 3 years ago

Monica Cellio‭ Thank you. I've updated my answer accordingly

fedorqui‭ wrote over 2 years ago

Oh, I just learned the button is a toggle, thanks Monica Cellio‭. It is not obvious, but I don't know what is the best way to make it easier to understand. Most probably, a x in the modal would help.

Monica Cellio‭ wrote over 2 years ago

fedorqui‭ yeah, all our modals are like that, and it's confused me too. (Somewhere here I have a question about how to dismiss search.) The 'x' suggestion has come up; I don't know what blocks that (some design principle I'm not aware of, some Ruby thing, something about how our code is structured, something else...).