Building Usable Privacy Tools
summary
Argues that privacy must be privacy by default and that current strategy over-relies on educating each user, not improving tooling; Bitcoin private-use requires a 37 hours course while Monero works with zero setup for most threat models. Shows usable examples: Monero, Cake Wallet, Signal, Tor Browser Bundle, Librewolf, ProtonMail, Briar, CryptPad, and notes Matrix has potential but needs UX work. Urges developers to match mainstream polish and urges honest recommendations and expectation-setting for users.
AI-written summary · about
chapters (23)
- 0:00Intro
- 0:55Welcome
- 1:40Demo
- 2:40Privacy is a pain
- 3:47Two solutions
- 5:30Educating users
- 6:32Telegram
- 7:38Matt ODonnell
- 8:32Simplicity
- 8:51The Way of Thinking
- 9:13What Needs to Change
- 11:26Other Examples
- 12:56Improved Work is Done
- 14:13Geometric Weather App
- 14:49Privacy can be beautiful
- 15:57We are fortunate
- 16:21We need to keep striving
- 16:42People wont switch to a platform unless its 10 times better
- 17:32Setting the narrative
- 19:00Embrace the suck
- 19:36Praise the good things
- 20:44Questions
- 22:25List of tools
related talks
28mMaking Your Privacy Software Usable
33mDesigning and Building With Privacy In Mind
40mCreative Ways to Champion Privacy Engineering Awareness
11mEvaluating the Usability of Privacy Choice Mechanisms
21mTuesday Lightning Talks 2
40mLessons Drawn From Cybersecurity In The Rise of Privacy Tech
28mBuild Privacy into Your Products and Gain User Trust
53mDesigning for Privacy in Mobile and Web Apps