The True Cost of Unmoderated Collaboration: A Story from the Trenches
summary
An API named suicide API in the node cluster module sparks a huge moderation crisis when random users and raids from 4chan amplify debate into targeted harassment, stalking and job threats; community leaders craft step-by-step moderation guidelines, deploy an Aleks linter idea to flag language, and create a semi-private moderation repo (open to ~500–600 org members) to track incidents and coordinate responses, proving swift, documented procedures stop escalation where vague codes of conduct fail.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:47About speaker
- 2:51Early open source
- 4:14Leading Node.js
- 5:41Hate in tech
- 7:30Myth of meritocracy
- 8:35People over code
- 9:22Node.js ‘suicide’ API
- 10:46Backlash over language
- 13:38Attacks on women
- 15:25Fear and intolerance
- 16:49Codes of conduct fail
- 17:59Moderation guidelines
- 19:01Private moderation repo
- 20:24United against raids
- 21:09‘Suicide’ API update
- 22:54Still figuring moderation
- 24:19Moderation and leadership
- 26:06Prevent burnout
- 27:56Moderation support
- 28:39No single protector
- 30:26Future of safe communities
- 36:51Actionable steps
- 38:37Q&A
related talks
27mWhy Open Source Fails to Protect Under-Represented Minorities
30mOccupy Ruby: Why We Need to Moderate the 1%
52mLeading the way towards implicitly safe communities
33mBuilding Compassionate Communities in Tech
12mOnline community and safety in software engineering
25mThe Source of Change: Bettering Online Open Source Communities... with Kattni
33mIncluding People
17mBuilding Open Source Communities with Tierney Cyren