Difference between revisions of "The Great Hack workshop wiki"
Jump to navigation
Jump to search
Line 9: | Line 9: | ||
=== Lessons from "The Great Hack" === | === Lessons from "The Great Hack" === | ||
* David Carroll's actions have helped go beyond the usual (lack of) data protection enforcement. | * David Carroll's actions have helped go beyond the usual (lack of) data protection enforcement. | ||
− | * Authorities | + | * Authorities often need complaints and evidence, their investigative and injunctive powers augment then. |
− | * | + | * Anyone can change things by pushing their rights through. |
− | * Journalists dropped the ball | + | * Journalists dropped the ball on David Carroll's case. |
* Time for action. | * Time for action. | ||
Revision as of 13:26, 23 September 2019
Item
The Great Hack workshop (Q1096)
Practicalities
- Day 1 4.45pm-5.45pm
Introduction
Some examples
Lessons from "The Great Hack"
- David Carroll's actions have helped go beyond the usual (lack of) data protection enforcement.
- Authorities often need complaints and evidence, their investigative and injunctive powers augment then.
- Anyone can change things by pushing their rights through.
- Journalists dropped the ball on David Carroll's case.
- Time for action.
Youtubers' Union
Youtubers are affected by algorithms demonetizing their content, based on unclear criteria. In the FairTube campaign, they are demanding better working conditions, mostly through transparency. They are exercising these demands collectively in an alliance with IG Metall (one of Europe's largest labor unions), with a threat of going individual(!) through the GDPR.
By now they got out of their ultimatum to Youtube some formal sitdown encounter.
Uber drivers
Transparency surface
- Black hat hackers use the so-called "attack surface" of a system to figure out its weaknesses, for their own profit.
- White hats do the same, but for the collective benefit.
- concept
- examples (recent complaint)
- rights associated to it
- expansion
Plan
- Right of access: why it exists
- Overall strategy: think, request/demand, argue, amplify, pressure; rinse and repeat
Use case
- Lumascape