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
I would like this functionality to extend to 'questions' as well as answers. This was influenced by the post I cannot understand the meaning of some downvotes In my opinion, downvoting some kinds ...
Answer
#2: Post edited
by
Moshi
·
2020-09-09T20:27:16Z (about 4 years ago)
fixed grammatical errors
- # I would like this functionality to extend to 'questions' as well as answers.
- This was influenced by the post *[I cannot understand the meaning of some downvotes](https://meta.codidact.com/questions/277573)*
- > In my opinion, downvoting some kinds of posts is meaningless.
- >
- > For example, why should anyone downvote a bug report, like [this post](https://meta.codidact.com/q/277379)? If someone has the same problem, they can upvote the bug report; otherwise, they can skip it. Quite the contrary, I think bug report posts should be heavily upvoted to encourage other users to report bugs of the system.
- >
- > Another example, why should anyone downvote a community proposal, like [this post](https://meta.codidact.com/q/277345)? If someone is interested in contributing to such a community, they can upvote the proposal; otherwise, they can skip it.
- If reactions are able to be added to these sort of 'questions', we can have "Reproduced"/"Not Reproduced" for bug reports instead of the odd
and frankly non-constructive upvotes/downvotes we have for them right now, and people can their OS and browser information in the additional comments.For community proposals, this can also replace the current awkward system of Monica creating an 'answer' for people to comment their interest/possible activity on; instead, people will react with "Interested", "Would be active on", or "Not-interested", for example.- ---
- This wasn't discussed in the linked post, but [feature-request]s also get downvoted for reasons that I can't understand.
- I have had my feature requests downvoted for reasons such as: 'It is probably difficult to implement', 'There exist workarounds', or 'there are more important things to do, so I'll downvote to decrease this suggestion's priority' (???). However, I, personally do not think those are valid reasons to downvote a suggestion - I would only downvote if I think that a suggestion is *harmful* in some way.
- Reactions would help by letting people react "Non-essential", for example, instead of flat out downvoting, the latter of which signals (to me, and I assume others) a *bad* suggestion, not a *low-priority* one.
- # I would like this functionality to extend to 'questions' as well as answers.
- This was influenced by the post *[I cannot understand the meaning of some downvotes](https://meta.codidact.com/questions/277573)*
- > In my opinion, downvoting some kinds of posts is meaningless.
- >
- > For example, why should anyone downvote a bug report, like [this post](https://meta.codidact.com/q/277379)? If someone has the same problem, they can upvote the bug report; otherwise, they can skip it. Quite the contrary, I think bug report posts should be heavily upvoted to encourage other users to report bugs of the system.
- >
- > Another example, why should anyone downvote a community proposal, like [this post](https://meta.codidact.com/q/277345)? If someone is interested in contributing to such a community, they can upvote the proposal; otherwise, they can skip it.
- If reactions are able to be added to these sort of 'questions', we can have "Reproduced"/"Not Reproduced" for bug reports instead of the odd
- and frankly non-constructive upvotes/downvotes we have for them right now, and people can add their OS and browser information in the additional comments.
- For community proposals, this can also replace the current awkward system of Monica creating an 'answer' for people to comment their interest/possible activity on; instead, people would react with "Interested", "Would be active on", or "Not-interested", for example.
- ---
- This wasn't discussed in the linked post, but [feature-request]s also get downvoted for reasons that I can't understand.
- I have had my feature requests downvoted for reasons such as: 'It is probably difficult to implement', 'There exist workarounds', or 'there are more important things to do, so I'll downvote to decrease this suggestion's priority' (???). However, I, personally do not think those are valid reasons to downvote a suggestion - I would only downvote if I think that a suggestion is *harmful* in some way.
- Reactions would help by letting people react "Non-essential", for example, instead of flat out downvoting, the latter of which signals (to me, and I assume others) a *bad* suggestion, not a *low-priority* one.
#1: Initial revision
by
Moshi
·
2020-09-07T23:21:33Z (about 4 years ago)
# I would like this functionality to extend to 'questions' as well as answers. This was influenced by the post *[I cannot understand the meaning of some downvotes](https://meta.codidact.com/questions/277573)* > In my opinion, downvoting some kinds of posts is meaningless. > > For example, why should anyone downvote a bug report, like [this post](https://meta.codidact.com/q/277379)? If someone has the same problem, they can upvote the bug report; otherwise, they can skip it. Quite the contrary, I think bug report posts should be heavily upvoted to encourage other users to report bugs of the system. > > Another example, why should anyone downvote a community proposal, like [this post](https://meta.codidact.com/q/277345)? If someone is interested in contributing to such a community, they can upvote the proposal; otherwise, they can skip it. If reactions are able to be added to these sort of 'questions', we can have "Reproduced"/"Not Reproduced" for bug reports instead of the odd and frankly non-constructive upvotes/downvotes we have for them right now, and people can their OS and browser information in the additional comments. For community proposals, this can also replace the current awkward system of Monica creating an 'answer' for people to comment their interest/possible activity on; instead, people will react with "Interested", "Would be active on", or "Not-interested", for example. --- This wasn't discussed in the linked post, but [feature-request]s also get downvoted for reasons that I can't understand. I have had my feature requests downvoted for reasons such as: 'It is probably difficult to implement', 'There exist workarounds', or 'there are more important things to do, so I'll downvote to decrease this suggestion's priority' (???). However, I, personally do not think those are valid reasons to downvote a suggestion - I would only downvote if I think that a suggestion is *harmful* in some way. Reactions would help by letting people react "Non-essential", for example, instead of flat out downvoting, the latter of which signals (to me, and I assume others) a *bad* suggestion, not a *low-priority* one.