Live data from Hacker News

GitHub: Block the Bullies

github.com

111–120 of 151 posts

Re: GitHub: Block the Bullies

#111
post #53
post #52

Earlier quoted context omitted.

Given the choice between a private dashboard vs a public repo list being spammed, I'll take the former, any day. I don't want either, but the former is an annoyance to me and only me . The latter is something that can (potentially) give a bad impression of me to others . Remember that reputation is important. Always.

I'm not sure how many times I have to say it: Adding someone as a collaborator is not publicly visible until you collaborate (make commits) on the project. At that point we show the activity on your public profile.

In a different thread jmaygarden said:

I got "dong markup" in my RSS reader from pull requests to zedshaw/mongrel2 today. So, the trolling was very much in public view.

So, there are ways to publicly troll someone on GitHub, even if not in this precise way.

Re: GitHub: Block the Bullies

#112
post #67
post #26

Background: http://sheddingbikes.com/posts/1306816425.html In all fairness, the guy was being a dick (no pun intended) to Zed. However, Zed should have kept the insults to the troll and left Github, Powerset, Engine Yard, and the Ruby community out.

How does anyone in the Ruby "community" have the time to get any actual work done? No other language community in the world behaves like this.

I've been trolled by people in lots of different "communities." PHP, Postgres, Java, Perl and Lua just to name a few. IMHO if a software community doesn't have jerks and trolls, it's because nobody is using the software. Ruby has its share but I don't find it any worse than the others.

Re: GitHub: Block the Bullies

#113
post #27

Earlier quoted context omitted.

As it stands, when you are added as a collaborator to a project it shows up in exactly one place — your private, logged in dashboard. It doesn't show up publicly anywhere. You must make a contribution to a project before you show up in any kind of public fashion.

I got "dong markup" in my RSS reader from pull requests to zedshaw/mongrel2 today. So, the trolling was very much in public view.

As Zed mentions in the article, he contributed to the project, which is why it showed up in your RSS feed.

Re: GitHub: Block the Bullies

#114
post #103
post #91

Earlier quoted context omitted.

But where are the Erlang trolls or the C++ trolls? They don't exist!

I don't know about the Erlang trolls, but the C++ trolls are out writing shitty internal corporate apps for Windows, leaving no source and forcing a company to use the buggy app in perpetuity. Real trolls ship.

But they are presumably not bitching about each other on the Interwebs?

Re: GitHub: Block the Bullies

#115
post #53
post #52

Earlier quoted context omitted.

Given the choice between a private dashboard vs a public repo list being spammed, I'll take the former, any day. I don't want either, but the former is an annoyance to me and only me . The latter is something that can (potentially) give a bad impression of me to others . Remember that reputation is important. Always.

I'm not sure how many times I have to say it: Adding someone as a collaborator is not publicly visible until you collaborate (make commits) on the project. At that point we show the activity on your public profile.

>I'm not sure how many times I have to say it:

How long until you get clued in that maybe the problem is not with the end users but with your UI?

Re: GitHub: Block the Bullies

#117
post #26

Background: http://sheddingbikes.com/posts/1306816425.html In all fairness, the guy was being a dick (no pun intended) to Zed. However, Zed should have kept the insults to the troll and left Github, Powerset, Engine Yard, and the Ruby community out.

That's a pretty lucid and well written account. I would like to know more about the connection between HackerNewsTips and Github though. Github employees have denied it here on HN.

As a paying customer of github, I'd like to know, too. If there is a link, I am deeply disappointed and believe this is exceedingly unprofessional.

Re: GitHub: Block the Bullies

#118
post #58

Earlier quoted context omitted.

Up until just now, I didn't know that. And if you didn't reply to my comment just now, I still wouldn't know it. And you explicitly telling people about how being a collaborator works isn't a scalable way for people to find out. And it sounds like this question/issue has come up before. Perhaps it can be made clearer somehow? In any case, thanks for clarifying when you become visible as a collaborator, even if only i…

Your comment [1] is a direct reply to one where kneath explicitly states it [2]. [1]: http://news.ycombinator.com/item?id=2606063 [2]: http://news.ycombinator.com/item?id=2605804 For me, it was pretty obvious because it doesn't show up on the profile under 'Public Repositories', only on the dashboard in a list of projects you have access to.

I think he means making it clearer in the UI. It would be weird for Github to depend on HN to inform users.

Re: GitHub: Block the Bullies

#120

Earlier quoted context omitted.

Your comment [1] is a direct reply to one where kneath explicitly states it [2]. [1]: http://news.ycombinator.com/item?id=2606063 [2]: http://news.ycombinator.com/item?id=2605804 For me, it was pretty obvious because it doesn't show up on the profile under 'Public Repositories', only on the dashboard in a list of projects you have access to.

I think he means making it clearer in the UI. It would be weird for Github to depend on HN to inform users.

The thing is that this is amazingly rare. The handful of times it's happened, the 'victim' most likely just removes the repo (which has always been possible) and that's the end of it. Others might say to their friends on IRC "Hey, can you see dongml in my projects list on github?" and sure enough the answer will be 'no'.

It's easy to say "oh just add it to the UI", but to actually do it is another story. Before you know it you've got hundreds of preferences, and then people will be complaining that there's too many options and it's too confusing (a-la facebook privacy settings). Honestly, GitHub's preference pages already need some work, so I for one am glad they don't add drop downs for every person's pet feature.

Regardless, it doesn't matter now. Now you just remove the project and block the user (or, presumably, just blocking the user might remove the repo... either way), so that's that.

Post reply on HN