Assume Worst Intent (Designing for the Abusive Ex)
summary
Describes concrete harms and fixes: a payments app (Square Cash) exposes victims to messages until a block function added in two weeks, Git bakes immutable commit names that out trans or divorced people, and a game (Hearthstone) avoids free text with pre-canned responses to stop abuse. Recommends reducing user-to-user surface area, granular privacy controls, not storing unnecessary data, human moderators with support, and asking for each feature “how could an abusive ex weaponize this?”
AI-written summary · about
chapters (6)
- 0:00Introduction
- 1:50Content Warning
- 9:15Who is doing it
- 12:54How do we make it better
- 19:07Safety
- 23:29Summary
related talks
57m(Ab)user Experience: The Dark side of Product and Security
50mYou, Ex. Breaking up with bad design
24mAlgorithms aren't neutral Making UX inclusive
20mMicrointeractions for the System: Design in the Age of Techlash
35mDesigning for Trust
37m(Ab)User Experience.
28mIntentionally Unintended: Redefining Dark Patterns
33mDesigning and Building With Privacy In Mind