From Voting Machines to Discord: A Path to Technological Activism
summary
A forensic look at US voting machines finds only a SHA-256 per file and a linter for source review, about 100 ballots tested per machine, and mixed C/C++/Java/C#/COBOL/SQL stacks — meaning a developer could flip every thousandth vote without detection. The narrative traces escalation from online harassment to real-world violence: a torch march of ~300–350 people, six militias present, a car attack that injures ~30 and kills one, and an organizer later arrested for online harassment. Calls for paper ballots, random audits, and better platform tools for blocking and reporting.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:31Topics
- 1:05The Wreck 25
- 3:08The Election
- 5:45Voting Machine Code
- 6:24A Duty to Preserve Democracy
- 7:28Industry Hit List
- 7:59Milo Yiannopoulos
- 10:30How to focus your activism to make real change
- 11:06How to speak out against sexism racism
- 11:40What does activism look like
- 12:07Local activism
- 12:41The worst that can happen
- 13:13Unite the Right
- 17:05Rally Proper
- 18:09Online Trolling
- 21:53The Good News
- 22:33technologists have a duty
related talks
45mFrom Ballots to Code: Exploring Election Security
22mBuilding a Voting Machine Everyone Can Trust
01h 01mPrinting Votes — Is It a Hack?
48mElection Security The post pandemic acceleration of secure web based voting
49mThe Return of Software Vulnerabilities in the Brazilian Voting Machines
51mBuilders and Breakers: Partnering for Secure Elections
55mReturn of the Insecure Brazilian Voting Machines
20mVerifiable Elections—Now Is the Time