5 ms·
The internet in general has problems with this, but I suspect it's much worse in the open source world where unmoderated forums are standard. If you look at the
by mike_hearn 12y ago
The internet in general has problems with this, but I suspect it's much worse in the open source world where unmoderated forums are standard. If you look at the moderation tools available in something like mailman, they're very poor. It's just not been a priority for technical discussion forums at all. And the social convention is to leave forums largely unmoderated anyway, so it's easy to get into a downward spiral where behaviour gets more and more extreme as people try to make their opinions stand out amongst the crowd.
What's worse, the fact that this scares off contributors is hard to spot, because you by definition cannot easily measure contributions that would have happened but didn't because of a community problem.
If you look at non-technical forums like Facebook, newspaper comment sections etc there's usually some form of moderation that imposes house rules like "be civil". This sort of thing can clean up individual forums but the wider problem remains: some people are just nasty and they often believe they can influence the development of their favourite project by being sufficiently nasty to developers they disagree with. If they can't do that in the project's own forums they'll do it elsewhere.
The Bitcoin community has pretty severe problems with this too, it's not just a Linux thing.
- _delirium 12y agoThey're smaller communities, but I've been on a few developer lists that are fairly strict about the dev list being only for developers. That doesn't solve the "dev who's a jerk" problem, but it does raise the barrier to entry by excluding people who want to only argue and not develop: if you subscribe and immediately start arguing, without having contributed anything, you get booted.
- kazinator 12y agoYou cannot moderate mailing lists because they are not centralized. When you hit "reply all" in a mailing list, the replies go directly to everyone who is on the To: or Cc: list. The list robot is just one of those parties. And of course, private replies are possible that the list robot doesn't even see. Some lists try to fix this by abusing Reply-to: to try to steer discussion replies to the list address, but that is fundamentally broken. About all you can do in a mailing list is to cull the junk from the permanent web archive. [Edit: look, you can downvote all you like. I know how mailing lists work and stand by what I wrote. I have used mailing lists for almost a quarter century, and I run mailing lists of my own. I know the ins and outs, and ways they can be configured.]
- kibwen 12y agoI've never used a mailing list that didn't possess a centralized address like foo-discuss@example.com. And these all require explicit approval to submit messages to the list, in order to keep out spam.
- kazinator 12y agoNo, they do not all require explicit approval to keep out spam. In GNU Mailman, this is a config option: you can allow non-subscribers to post or not. All of the mailing lists that I operate on my own mailing list server allow non-subscribers to post. Due to my anti-spam configuration, this isn't a problem. Traditional mailing lists, before the rise of spam, were usually this way. And anyway, this is a separate issue. A list which does not re-mail postings from non-subscribers can nevertheless not do Reply-to: munging. So once you are on the list and participate in discussions, you're still sending messages to the list, as well as directly to those in the discussion. Earlier this year I was involved in a mailing list discussion in which one of the parties was actually (unbeknownst to me for a while) a "persona non grata": someone banned from posting to the mailing list. His postings were not being seen by the subscribers, but only those in the debate. This list does use Reply-to:; he just (trivially) circumvented it.
- lallysingh 12y agoWhat's wrong with changing Reply-To?
- JoshTriplett 12y agohttp://www.unicom.com/pw/reply-to-harmful.html http://www.unicom.com/pw/reply-to-harmful.html http://woozle.org/~neale/papers/reply-to-still-harmful.html http://woozle.org/~neale/papers/reply-to-still-harmful.html
- kazinator 12y agoYou mean, what is wrong with setting Reply-To. Reply-To is a special header that is normally not present. It has a valid use case (what it is designed for). It's used when someone composes a message on behalf of someone else (like a secretary on behalf of the boss). It says that another person is the real author; please reply directly to that person. When it's added by a mailing list robot, it wrecks the traditional operation of the mailing list. For one thing, it becomes hard to reply privately. You hit "reply", and the message is composed to the mailing list. A mailing list non-subscriber is not able to get a reply to a question posted to a mailing list. So the Reply-to trick is only compatible with subscriber-only mailing lists, which are a pain in the butt. Reply-To is a wrongheaded solution to a mailing list problem: and that problem is people using "reply" instead of "reply all", generating private discussions that do not go to the list, but unintentionally. Today, a feature is showing up in mail clients (at least open source ones): "reply to list". This addresses the problem in a better way. The mail client recognizes, from the headers, that the message being replied to is a mailing list item, and presents this clear way of replying. Furthermore, the mail client extracts the correct list address from the headers. Unfortunately, "reply to list" implementations are still not kind to non-subscribers. The feature assumes the subscribe-only style of mailing list. (What is needed is a list header by which the re-mailing robot can tag the message as being from a non-subscriber, so the mail client can know to keep that person in the loop.) Also, the direct, back-channel replies sent among participants do not carry the list headers, so "reply to list" does not work for those: it's back to "reply" or "reply all".
- artagnon 12y agoYou make it sound like moderated development is the best style; if you preselect people through a standardized interview process (like a software firm), or prune messages based on some algorithmic filter, you trade off diversity. In the extreme case, the community can be caught up circle-jerking on the same set of ideas. The key idea in an open community is organic moderation. The currently influential people in the community "bless" the threads with interesting ideas/ patches; they decide how much deviation from "civil" behavior they can put up with. In a good community, attention-seeking behavior would be condemned by the influential people in the community. The health of the community depends a lot on the initial contributors. It's true that this kind of model scares of a lot of contributors, but it also attracts many others who would have been eliminated in a pre-selection. The main takeaway from Lennart's post is that more community building work is required: they don't automatically become good communities.