Live data from Hacker News

Add Reactions to Pull Requests, Issues, and Comments

github.com

81–90 of 238 posts

Re: Add Reactions to Pull Requests, Issues, and Comments

#81

Earlier quoted context omitted.

>you never ever ever implement a downvote button of any kind. People who don't agree with something should have a way of expressing their views. Why is it acceptable to have a +1 button but not a -1 button? Why can people agree without giving any reason for their agreement but they can't disagree without giving any reason for their agreement? It's crazy that society works in this way and that people have such an irra…

> People who don't agree with something should have a way of expressing their views. Why is it acceptable to have a +1 button but not a -1 button? Why can people agree without giving any reason for their agreement but they can't disagree without giving any reason for their agreement? Because when you agree, that means the argument has already been presented - specifically, it's the argument that you are agreeing with…

>That is not the case for disagreement

The reason why Github added these votes in the first place is so that people can give a signal of how welcome or not a certain change is to the project. If you only provide the signal for agreement but remove the signaling for disagreement and make it costly, then you'll get more people voting one way than the other. If it costs more to disagree then you're already rigging the game towards agreement.

Re: Add Reactions to Pull Requests, Issues, and Comments

#82

-1 or the thumbs down reaction, I think is a mistake. They aren't usually that constructive, because most of the time they are used as retaliation against a specific user, instead of constructive criticism. If someone downvotes you, you tend to downvote them. At the least, it should be a privilege to down vote, like SO and HN do. http://stackoverflow.com/help/privileges/vote-down

I just want to elaborate on this a bit more: Implementing a downvote button is inviting baseless disagreement . It makes it socially acceptable to say that you disagree, without ever providing an argument or being expected to do so - this is precisely what you don't want, on what is supposed to be a constructive platform. This will (indirectly and directly) lead to populism, where unpopular opinions get dismissed out…

Very many HN threads would be improved if people would just downvote for disagreement and shut the fuck up.

Those downvotes would soon be corrected by other people reading the thread, and we wouldn't have to read bad tempered bickering.

Re: Add Reactions to Pull Requests, Issues, and Comments

#83

Earlier quoted context omitted.

> People who don't agree with something should have a way of expressing their views. Why is it acceptable to have a +1 button but not a -1 button? Why can people agree without giving any reason for their agreement but they can't disagree without giving any reason for their agreement? Because when you agree, that means the argument has already been presented - specifically, it's the argument that you are agreeing with…

>That is not the case for disagreement The reason why Github added these votes in the first place is so that people can give a signal of how welcome or not a certain change is to the project. If you only provide the signal for agreement but remove the signaling for disagreement and make it costly, then you'll get more people voting one way than the other. If it costs more to disagree then you're already rigging the g…

Sure, but that is already the case - posting a :+1: costs much less effort than writing a counter-argument (and is already widely socially accepted, spammy-ness aside). The addition of an upvote button doesn't change this.

That's not to say that I wouldn't like that bias resolved, but it's a bias that exists precisely because of the difference between 'agreement' and 'disagreement' that I described, and I'm not sure it can be solved in a technical manner.

Re: Add Reactions to Pull Requests, Issues, and Comments

#84
post #79
post #70

Am I missing something or is there still no way to +1 issues? All I see are ways to react to comments. Whenever I feel the urge to "+1" something it's for the issue, not a specific comment. Can someone explain how to add a reaction to an issue?

You are missing something :) e.g., top right corner on https://github.com/facebook/react/issues/6239

I still only see it for the comment and not the issue itself.

Re: Add Reactions to Pull Requests, Issues, and Comments

#85

Earlier quoted context omitted.

Coincidentally you're being downvoted for stating this.

Yeah, I thought that was funny. Guess I wrote a horrible comment.

This comment is now getting downvoted. To be clear, so people stop downvoting this comment, this parent comment was initially downvoted to -1, it obviously isn't anymore.

Re: Add Reactions to Pull Requests, Issues, and Comments

#86

Earlier quoted context omitted.

> People who don't agree with something should have a way of expressing their views. Why is it acceptable to have a +1 button but not a -1 button? Why can people agree without giving any reason for their agreement but they can't disagree without giving any reason for their agreement? Because when you agree, that means the argument has already been presented - specifically, it's the argument that you are agreeing with…

>That is not the case for disagreement The reason why Github added these votes in the first place is so that people can give a signal of how welcome or not a certain change is to the project. If you only provide the signal for agreement but remove the signaling for disagreement and make it costly, then you'll get more people voting one way than the other. If it costs more to disagree then you're already rigging the g…

If there is such a strong counter argument, someone will make it (see XKCD 386) and it will be possible to upvote the dissenting opinion.

Re: Add Reactions to Pull Requests, Issues, and Comments

#87
post #82

Earlier quoted context omitted.

I just want to elaborate on this a bit more: Implementing a downvote button is inviting baseless disagreement . It makes it socially acceptable to say that you disagree, without ever providing an argument or being expected to do so - this is precisely what you don't want, on what is supposed to be a constructive platform. This will (indirectly and directly) lead to populism, where unpopular opinions get dismissed out…

Very many HN threads would be improved if people would just downvote for disagreement and shut the fuck up. Those downvotes would soon be corrected by other people reading the thread, and we wouldn't have to read bad tempered bickering.

If that was the case, then this would be accomplished constructively by people upvoting a strong argument rather than downvoting an argument they have a disagreement with but either a lack of will or ability to articulate the reason they disagree.

Re: Add Reactions to Pull Requests, Issues, and Comments

#88

-1 or the thumbs down reaction, I think is a mistake. They aren't usually that constructive, because most of the time they are used as retaliation against a specific user, instead of constructive criticism. If someone downvotes you, you tend to downvote them. At the least, it should be a privilege to down vote, like SO and HN do. http://stackoverflow.com/help/privileges/vote-down

Agreed 100% for Facebook or even Hacker News, however on GitHub it would be really useful for voting.

If you ask "Should we add this feature?", it's hard to understand what favorites mean if you don't have an anchor. Does 10 thumbs-up mean unanimous support, or is it just a small minority? It'd be nice to say "Oh, 10 upvotes... but there's 90 downvotes, so we won't do it."

FB and Hacker News are a marketplace of relatively-inconsequential ideas and thoughts. However, changes discussed on GitHub Issues can potentially have an impact on your company and livelihood.

Re: Add Reactions to Pull Requests, Issues, and Comments

#89

-1 or the thumbs down reaction, I think is a mistake. They aren't usually that constructive, because most of the time they are used as retaliation against a specific user, instead of constructive criticism. If someone downvotes you, you tend to downvote them. At the least, it should be a privilege to down vote, like SO and HN do. http://stackoverflow.com/help/privileges/vote-down

Agreed 100% for Facebook or even Hacker News, however on GitHub it would be really useful for voting. If you ask "Should we add this feature?", it's hard to understand what favorites mean if you don't have an anchor. Does 10 thumbs-up mean unanimous support, or is it just a small minority? It'd be nice to say "Oh, 10 upvotes... but there's 90 downvotes, so we won't do it." FB and Hacker News are a marketplace of rela…

on facebook they say "like if you want A and share if you want B" obviously this is a 'viral marketing' ploy, but something similar would be simple for github

just write:

thumbs up if you want A smile if you want B

problem solved

Re: Add Reactions to Pull Requests, Issues, and Comments

#90

Earlier quoted context omitted.

Agreed 100% for Facebook or even Hacker News, however on GitHub it would be really useful for voting. If you ask "Should we add this feature?", it's hard to understand what favorites mean if you don't have an anchor. Does 10 thumbs-up mean unanimous support, or is it just a small minority? It'd be nice to say "Oh, 10 upvotes... but there's 90 downvotes, so we won't do it." FB and Hacker News are a marketplace of rela…

on facebook they say "like if you want A and share if you want B" obviously this is a 'viral marketing' ploy, but something similar would be simple for github just write: thumbs up if you want A smile if you want B problem solved

Or they could just have a thumbs-down button, and expect a higher level of discourse than Facebook.
Post reply on HN