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 Suggestion for allowing to mark answers as "accepted", "outdated" or "dangerous"

Parent

Suggestion for allowing to mark answers as "accepted", "outdated" or "dangerous"

+26
−1

Currently, it is possible to upvote and downvote answers. That's likely enough in most situations, but there are some cases where you might want to have more than one way to react to a post.

For example, imagine you are on Software Development and an answer suggests a solution that drastically impedes your system's security. Or you are on Electrical Engineering and the answer suggests something that might electrocute you. In these cases, a downvote might not be enough of a signal to warn users of such possible dangers.

Another possible situation is "accepting answers", a concept that exists on most common Q&A sites. Unlike other sites, we decided quite early that a single vote from the asker shouldn't impact answer sort order.

And yet another feature suggested and strongly advocated for by some users is the option of "signed votes", mostly seen as a way for experts or highly reputable community members to give more weight to their votes by publicly endorsing (or refuting) a specific answer.

I think I've got a solution, one that might provide a framework for commmunities to solve all these use cases. We discussed this in chat and tossed some ideas around, and I must say that I absolutely love the current proposal:


Communities will be able to define a small set of "reactions", which can be applied to posts. Default (or recommended) reactions would likely be:

  • ☑ This post works for me (= accepting an answer, but not only by OP)
  • ⏳ This post is outdated
  • ⚠ This post is dangerous

However, communities might want to have different reactions. For example, Cooking might want to have

  • 😋 This is tasty
  • 🤮 This doesn't taste good

Once applied to answers, there would be a little box/badge above the answer, which contains the selected reaction and a list of users who have chosen that reaction. I used the developer tools in my browser to simulate what this might look like. Imagin, that the tooltip on the first badge says the names of the users choosing that reaction.

Mockup showing two badges (works for many users & found dangerous by one user) above a post

Users will be able to choose reactions from a modal that can be opened from a button below the voting buttons. When choosing a reaction, users will be encouraged to add comments, giving details to their vote. This is especially neccessary for marking a post as "dangerous", because other users need to know what exactly is dangerous.

Here are two mockups for how the reactions modal might be presented:

Mockup showing a modal with the label "This post ..." and the options "works for me", "is outdated" and "is dangerous (add comment)" and an optional comment box

Same mockup as above, but some icons similiar to the emojis in the list above have been added

Additionally, when entering a comment into the comment box in the modal, a comment will be posted on the user's behalf, which contains the chosen reaction and comment. (Also seen in the screenshots.)

What do you think of this suggested feature? Do you have any other use cases we should consider if we chose to implement this suggestion?

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

1 comment thread

General comments (7 comments)
Post
+6
−1

Proposal: Integrate the voting system into the reactions feature. Let users react with "this is a good post" or "this is a bad post," with the prompt for an optional comment, and continue weighing post score as you have, based solely on these two reactions.

This has the benefits of:

  1. Potentially less confusing (for a sufficient formulation instead of "this is a good/bad post") to new users to distinguish between votes and reactions ("what's the point of downvoting when I can instead label this 'dangerous' or 'outdated'?")
  2. A problem Somewhere Else was that users would often downvote without giving their constructive criticism. Now, sometimes there isn't anything to add other than "this is a bad post," but sometimes it's a bit head-scratching why someone felt it was a bad post. By prompting them to comment, rather than simply leaving it as an option, users may be more inclined to share their thoughts.
  3. Why should point #2 be limited to downvotes? For exactly the opposite of the same reasons, it may be beneficial to prompt users to share what they found great about the post.
History
Why does this post require moderator attention?
You might want to add some details to your flag.

1 comment thread

Something like 2. and 3. didn't work on SE (or the beginning of SO, IIRC; ). Forcing people to fill f... (1 comment)
Something like 2. and 3. didn't work on SE (or the beginning of SO, IIRC; ). Forcing people to fill f...
Lorenzo Donati‭ wrote over 2 years ago

Something like 2. and 3. didn't work on SE (or the beginning of SO, IIRC; ). Forcing people to fill fields when they are in a hurry will lead to lot of wqweqekj comments. It is a feature just asking for clutter. Comments should always be optional, IMO.