News for hackers. Stuff that matters.
Re:MySQL man pages license change is a bug by pessimizer on Wednesday June 19, 2013 @01:50PM (#5907024)
More like Facebook is blocking Tor except it was an accident, and MySQL is now under a new license except it was an accident. The idea of shaming people away from pointing out, and yes, speculating on the motives for these changes is a terrible idea for a forum. And if these things hadn't surfaced on HN, do you think they would have been corrected so quickly? What would the the "newly-damned organizations" be posting a response to?

Will HN ever get past all of the whiny meta about what other people are posting or upvoting?

Re:MySQL man pages license change is a bug by freehunter on Wednesday June 19, 2013 @03:07PM (#5907538)
My criticism is on the authors of the articles, not on the HN voters. If the headline reads "Facebook blocks Tor, putting activists at risk", that's quite a damning claim. Maybe they author should check with Facebook. The commentors here at HN saying "it doesn't surprise me that Facebook doesn't care about activists" might not be constructive, but I'm not criticizing it because it's a forum like you said.

I'm not sure I agree that these things necessarily needed to be brought up on HN in order for them to be corrected. Just reaching out to FB may have done it. The author did not do this, instead issuing a retraction after the fact. Did anyone contact the MySQL team to see if this was a mistake before lighting the torches and grabbing the pitchforks?

The problem isn't the people here on HN. The problem is the authors of these irresponsible articles; authors who know that the more sensationalist of headline they write, the more likely the community will join their frenzy without question. It's meta on the tech journalist community, not the HN community.

Re:MySQL man pages license change is a bug by famousactress on Wednesday June 19, 2013 @05:19PM (#5908331)
The article headlines are not irresponsible. "Facebook blocks Tor, putting activists at risk" is true. The fact that the block was automated (and with luck, temporary) is also true but little help to the activists using it. Same logic goes for the man pages.

If you run a project that enjoys the wide-scale usership of Facebook or MySQL then grow thick skin cause people are gonna raise flags fast when things look fishy. Because your project really fucking matters to people and mistakes hurt, deal with it.

I'd wager that this helps your product more often than it hurts it.

Re:MySQL man pages license change is a bug by benbeltran on Wednesday June 19, 2013 @02:20PM (#5907243)
Kind of an aside, but still relevant to part of your post. Whining about the content and whining about the meta whining is part of any sufficiently old community. I can recall from communities I've managed, and from ones I've participated in there's /always/ metacommentary and metametacommentary. The best thing to do in these cases is not to engage it. But no, HN will never get past all the whiny meta and there's very little we can do about it except letting it slide :(

Quick Edit: This is one of the reasons why I love discourse, it encourages metadiscussion in a separate part, and while it doesn't keep it from contaminating, it seriously helps a lot to focus it and guide it.

Re:MySQL man pages license change is a bug by lsiebert on Wednesday June 19, 2013 @02:49PM (#5907418)
That's one of the reasons I like Metafilter :).
Re:MySQL man pages license change is a bug by jholman on Wednesday June 19, 2013 @05:25PM (#5908388)
benbeltrain: How does that work in Discourse?

lsiebert: How does that work on Metafilter?

Re:MySQL man pages license change is a bug by benbeltran on Thursday June 20, 2013 @08:39AM (#5911649)
Well, in discourse it's more convention than anything. But the first category created, is a `meta` category. But this explains it better: http://meta.discourse.org/t/what-is-meta/5249/2