Skip to content

Commit

Permalink
add topic on chrome surveillance
Browse files Browse the repository at this point in the history
  • Loading branch information
none committed Mar 24, 2019
1 parent 4d36b06 commit ca70175
Showing 1 changed file with 12 additions and 1 deletion.
13 changes: 12 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -469,11 +469,22 @@ There are other advantages that can be covered too:

<br>

## Should we be using chrome?

*event format: workshop/working session*

Explore together with others how privacy invasive chrome really is. The base for this session would the [chrome privacy whitepaper](https://www.google.com/intl/en/chrome/privacy/whitepaper.html), which is a document that details all the surveillance that chrome does (they must call it a "privacy paper" ironically).

At the end of 2018, google (the company that develops chrome) [silently pushed an update](https://mashable.com/article/google-chrome-69-forced-login/?europe=true) that automatically login in to chrome any user who had logged into a google account without consent or notification. We aready knew that having a company like google as owner of the browser we use could be a bad idea. I guess we just needed proof that it could lead to more privacy invasions.

But many more privacy invasions happen in chrome and we're not even aware of them. This will serve as an eye opener to what google really is seeking - our souls ;)

<br>

## Cooperate With Artists to create Awareness
*event format: ?*
Invite artists to brainstorm on ideas to raise awareness on privacy issues and also inform them.


<br>

## Using Facebook to get people out of there
Expand Down

0 comments on commit ca70175

Please sign in to comment.