mirror of
https://github.com/privacyguides/privacyguides.org
synced 2024-11-28 05:53:30 +01:00
Move articles to blog.privacyguides.org (#985)
This commit is contained in:
Jonah Aragon
parent
a1a20eeeb0
commit
834d30ac8c
@ -1,66 +0,0 @@
|
||||
---
|
||||
title: "Write for us!"
|
||||
icon: material/currency-usd
|
||||
---
|
||||
Have some privacy knowledge? We would love your contributions! We are offering bounties between $100 and $300 per article on a variety of privacy-related topics and guides.
|
||||
|
||||
If you are interested, please email [jonah@privacyguides.org](mailto:jonah@privacyguides.org) with the topic(s) you'd like to write about. **Written content must be original**, accurate, well-referenced, and meet a number of criteria prior to payout. Articles should typically be around 1000-2000 words, you want to get the point across entirely, but not overfilled with unnecessary information that makes it difficult for beginners to follow. Familiarity with GitHub and Markdown is not a must, but will make the process significantly easier for both of us.
|
||||
|
||||
These are some topic ideas. If you want to write about something not in this list that you feel is important, suggest it via email. If you want clarity on any of these topics, please ask. Prices indicated are estimates.
|
||||
|
||||
We can not accept articles about closed-source software, paid software, or promotional content. We can’t reprint content that has already been published elsewhere. All payouts are at editorial discretion. We publish all content under the [CC0 1.0 Universal License](https://github.com/privacyguides/privacyguides.org/blob/main/LICENSE), this means you are releasing your work to the public domain to the greatest extent legally possible.
|
||||
|
||||
We strongly encourage submitting a strong outline before writing a full article, with enough detail for our editorial team to assess the quality and scope of the article.
|
||||
|
||||
## Introductory Articles (\$100-$200)
|
||||
|
||||
### Introduction to Privacy / Privacy Overview
|
||||
|
||||
A well sourced article on why privacy matters; how your privacy is invaded by big tech companies, malicious actors, and state-sponsored organizations; and why people should care.
|
||||
|
||||
### Mass Surveillance
|
||||
|
||||
A well sourced article on mass surveillance programs. This should primarily focus on state-sponsored programs but could cover corporate surveillance as well.
|
||||
|
||||
### Differentiating Security, Privacy, and Anonymity
|
||||
|
||||
These are three distinct but often conflated topics:
|
||||
|
||||
- **Security** generally refers to how protected you are from unauthorized users accessing your data. You can be secure without privacy by giving your data to Google, for example. Google has never had a data breach, but they still might have deep personal info on you themselves.
|
||||
- **Privacy** generally refers to the prevention of your personal data from being observed. This ranges on a per-person basis, consider it the ability to control the information people know about you.
|
||||
- **Anonymity** generally refers to your identity being completely unknown/untraceable. This is sometimes but not always desirable, depending on the context.
|
||||
|
||||
### Open Source
|
||||
|
||||
A well sourced article on why open-source tools are important in building a more privacy-friendly future.
|
||||
|
||||
### Security Basics
|
||||
|
||||
A well sourced overview of security best-practices, such as:
|
||||
|
||||
- Password manager use (and how they protect you from data breaches)
|
||||
- MFA/2FA
|
||||
- Masking Emails/Payments
|
||||
- etc.
|
||||
|
||||
We are not suggesting specific tools here necessarily, just going over the concepts in detail.
|
||||
|
||||
## "How Things Work" Articles ($100)
|
||||
|
||||
750-1500 word explainers on a variety of topics.
|
||||
|
||||
- How HTTPS/TLS works
|
||||
- How websites usually secure your data
|
||||
- How disk encryption works
|
||||
- How Tor works
|
||||
- etc.
|
||||
|
||||
## Advanced Topics (\$200-$300)
|
||||
|
||||
### Identity Theft/Damage Control
|
||||
|
||||
A guide on the steps to take after being a victim of identity theft
|
||||
|
||||
### Internet Cleanup
|
||||
|
||||
A guide on scrubbing the internet/social media of personal information to the greatest extent possible.
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 1.6 MiB |
Binary file not shown.
|
Before Width: | Height: | Size: 1.9 MiB |
Binary file not shown.
|
Before Width: | Height: | Size: 440 KiB |
17
docs/blog.md
17
docs/blog.md
@ -1,17 +0,0 @@
|
||||
---
|
||||
title: Blog Index
|
||||
hide:
|
||||
- toc
|
||||
---
|
||||
|
||||
## 2022
|
||||
|
||||
- **April 4:** ["Move Fast and Break Things"](blog/2022/04/04/move-fast-and-break-things.md)
|
||||
|
||||
## 2021
|
||||
|
||||
- **December 1:** [Firefox Privacy: 2021 Update](blog/2021/12/01/firefox-privacy-2021-update.md)
|
||||
- **November 1:** [Virtual Insanity](blog/2021/11/01/virtual-insanity.md)
|
||||
- **September 14:** [Welcome to Privacy Guides](blog/2021/09/14/welcome-to-privacy-guides.md)
|
||||
|
||||
|
||||
@ -1,62 +0,0 @@
|
||||
---
|
||||
title: 'Welcome to Privacy Guides'
|
||||
author:
|
||||
- Daniel
|
||||
- Freddy
|
||||
- Jonah
|
||||
template: overrides/blog.html
|
||||
excerpt: The team formerly known as PrivacyTools welcomes you to join a new community focused around privacy and security education.
|
||||
---
|
||||
|
||||
We are excited to announce the launch of [Privacy Guides](https://www.privacyguides.org/) and [r/PrivacyGuides](https://www.reddit.com/r/PrivacyGuides/), and welcome the privacy community to participate in our crowdsourced software recommendations and share tips and tricks for keeping your data safe online. Our goal is to be a central resource for privacy and security-related tips that are usable by anybody, and to carry on the trusted legacy of PrivacyTools.
|
||||
|
||||
As we [announced](https://web.archive.org/web/20210729184422/https://blog.privacytools.io/the-future-of-privacytools/) on the PrivacyTools blog in July, we made the decision to migrate off our former privacytools.io domain for various reasons, including an inability to contact the current domain holder for over a year and [growing](http://www.thedarksideof.io/) [issues](https://fortune.com/2020/08/31/crypto-fraud-io-domain-chagos-islands-uk-colonialism-cryptocurrency/) [with the .IO top-level domain](https://github.com/privacytools/privacytools.io/issues/1324). As attempts to regain ownership of the domain have proven fruitless, we found it necessary to make this switch sooner rather than later to ensure people would find out about this transition as soon as possible. This gives us adequate time to transition the domain name, which is currently redirecting to [www.privacyguides.org](https://www.privacyguides.org/), and it hopefully gives everyone enough time to notice the change, update bookmarks and websites, etc.
|
||||
|
||||
We chose the name Privacy Guides because it represents two things for us as an organization: An expansion beyond simple recommendation lists, and a goal of acting as the trusted guides to anyone newly learning about protecting their personal data.
|
||||
|
||||
As a name, it moves us past recommendations of various tools and focuses us more on the bigger picture. We want to provide more _education_ — rather than _direction_ — surrounding privacy-related topics. You can see the very beginnings of this work in our new page on [threat modeling](/threat-modeling), or our [VPN](/vpn) and [Email Provider](/email) recommendations, but this is just the start of what we eventually hope to accomplish.
|
||||
|
||||
### Website Development
|
||||
|
||||
Our project has always been community-oriented and open-sourced. The source code for PrivacyTools is currently archived at [https://github.com/privacytools/privacytools.io](https://github.com/privacytools/privacytools.io). This repository will remain online as an archive of everything on PrivacyTools up to this transition.
|
||||
|
||||
The source code for our new website is available at [https://github.com/privacyguides/privacyguides.org](https://github.com/privacyguides/privacyguides.org). All updates from PrivacyTools have been merged into this new repository, and this is where all future work will take place.
|
||||
|
||||
### Services
|
||||
|
||||
PrivacyTools also runs a number of online services in use by many users. Some of these services are federated, namely Mastodon, Matrix, and PeerTube. Due to the technical nature of federation, it is impossible for us to change the domain name on these services, and because we cannot guarantee the future of the privacytools.io domain name we will be shutting down these services in the coming months.
|
||||
|
||||
We strongly urge users of these services to migrate to alternative providers in the near future. We hope that we will be able to provide enough time to make this as seamless of a transition as possible for our users.
|
||||
|
||||
At this time we do not plan on launching public Matrix, Mastodon, or PeerTube instances under the Privacy Guides domain. Any users affected by this transition can get in touch with [@jonah:aragon.sh](https://matrix.to/#/@jonah:aragon.sh) on Matrix if any assistance is needed.
|
||||
|
||||
Other services being operated by PrivacyTools currently will be discontinued. This includes Searx, WriteFreely, and GhostBin.
|
||||
|
||||
Our future direction for online services is uncertain, but will be a longer-term discussion within our community after our work is complete on this initial transition. We are very aware that whatever direction we move from here will have to be done in a way that is sustainable in the very long term.
|
||||
|
||||
### r/PrivacyGuides
|
||||
|
||||
PrivacyTools has a sizable community on Reddit, but to ensure a unified image we have created a new Subreddit at [r/PrivacyGuides](https://www.reddit.com/r/PrivacyGuides/) that we encourage all Reddit users to join.
|
||||
|
||||
In the coming weeks our current plan is to wind down discussions on r/privacytoolsIO. We will be opening r/PrivacyGuides to lots of the discussions most people are used to shortly, but encouraging general “privacy news” or headline-type posts to be posted on [r/Privacy](https://www.reddit.com/r/privacy/) instead. In our eyes, r/Privacy is the “who/what/when/where” of the privacy community on Reddit, the best place to find the latest news and information; while r/PrivacyGuides is the “how”: a place to share and discuss tools, tips, tricks, and other advice. We think focusing on these strong points will serve to strengthen both communities, and we hope the good moderators of r/Privacy agree :)
|
||||
|
||||
### Final Thoughts
|
||||
|
||||
The former active team at PrivacyTools universally agrees on this direction towards Privacy Guides, and will be working exclusively on Privacy Guides rather than any “PrivacyTools” related projects. We intend to redirect PriavcyTools to new Privacy Guides properties for as long as possible, and archive existing PrivacyTools work as a pre-transition snapshot.
|
||||
|
||||
Privacy Guides additionally welcomes back PrivacyTools’ former sysadmin [Jonah](https://twitter.com/JonahAragon), who will be joining the project’s leadership team.
|
||||
|
||||
We are not accepting sponsorships or donations at this time, while we work out our financial plan. We will be in touch with existing sponsors on PrivacyTools’ OpenCollective to determine what the best way forward is soon.
|
||||
|
||||
We are all very excited about this new brand and direction, and hope to have your continued support through all of this. If you have any questions, concerns, or suggestions, please reach out to us. We are always happy to receive guidance and input from our community! ❤
|
||||
|
||||
----------
|
||||
|
||||
**_Privacy Guides_** _is a socially motivated website that provides information for protecting your data security and privacy._
|
||||
|
||||
* [Join r/PrivacyGuides on Reddit](https://www.reddit.com/r/privacyguides)
|
||||
* [Follow @privacy_guides on Twitter](https://twitter.com/privacy_guides)
|
||||
* [Collaborate with us on GitHub](https://github.com/privacyguides/privacyguides.org)
|
||||
* [Join our chat on Matrix](https://matrix.to/#/#privacyguides:aragon.sh)
|
||||
|
||||
The contact for this story is Jonah, who is reachable on Twitter [@JonahAragon](https://twitter.com/JonahAragon), Matrix [@jonah:aragon.sh](https://matrix.to/#/@jonah:aragon.sh), or Signal 763-308-5533.
|
||||
@ -1,32 +0,0 @@
|
||||
---
|
||||
title: 'Virtual Insanity'
|
||||
author: Freddy
|
||||
background: virtual-insanity.jpg
|
||||
background_src: 'https://unsplash.com/photos/5psJeebVp9o'
|
||||
template: overrides/blog.html
|
||||
excerpt: Facebook is dead. Long live Facebook.
|
||||
---
|
||||
|
||||
Not so long ago, the world was predicting the end for Facebook. Now it is no more. Gone from the face of the planet - never to be seen again. Except it isn't.
|
||||
|
||||
Facebook has not disappeared. No, not even the damning 'Facebook Papers' can shut it down. Mark Zuckerberg stood up on stage, and announced that it had changed its name to: Meta.
|
||||
|
||||
A key part of this new vision for the company is the idea of the metaverse. If it sounds like something out of a sci-fi movie or novel, that's because it is. The term was first coined by author Neal Stephenson in his 1992 book *Snow Crash*. Zuckerberg's only problem is that novel was dystopian. Here's a brief snippet of Stephenson's description of the metaverse:
|
||||
|
||||
> "Your avatar can look any way you want it to, up to the limitations of your equipment. If you're ugly, you can make your avatar beautiful. If you've just gotten out of bed, your avatar can still be wearing beautiful clothes and professionally applied makeup. You can look like a gorilla or a dragon or a giant talking penis in the Metaverse. Spend five minutes walking down the Street and you will see all of these."
|
||||
|
||||
In fairness, that doesn't seem unlike the sort of content you see on Facebook today. Compare this to what Zuckerberg [wrote](https://about.fb.com/news/2021/10/founders-letter/) in his 2021 Founders Letter:
|
||||
|
||||
> "In this future, you will be able to teleport instantly as a hologram to be at the office without a commute, at a concert with friends, or in your parents' living room to catch up. This will open up more opportunity no matter where you live. You'll be able to spend more time on what matters to you, cut down time in traffic, and reduce your carbon footprint."
|
||||
|
||||
The similarities are uncanny.
|
||||
|
||||
This wouldn't be the first time that Facebook has been described as dystopian. One *Mashable* article [called](https://mashable.com/article/facebook-dystopia) the social media giant 'Orwellian and Huxleyan at the same time.' Quite a feat.
|
||||
|
||||
The 'Facebook Papers' have some pretty shocking - though not entirely surprising - revelations as well. The leaked documents demonstrate the extent to which Facebook values engagement above all else (including a good experience). For instance, we learnt that the algorithm is [optimised](https://www.wired.com/story/facebook-transparency-biggest-sites-pages-links/) for low quality content, [prioritises](https://www.washingtonpost.com/technology/2021/10/26/facebook-angry-emoji-algorithm/) rage over happiness for profit, and [promotes](https://www.theatlantic.com/ideas/archive/2021/10/facebook-papers-democracy-election-zuckerberg/620478/) extremist content. Most alarming was that the firm [failed](https://apnews.com/article/the-facebook-papers-covid-vaccine-misinformation-c8bbc569be7cc2ca583dadb4236a0613) to reduce disinformation during the pandemic even when given the opportunity. Zuckerberg said no to this, presumably because it would reduce engagement and, in turn, Facebook's advertising revenue.
|
||||
|
||||
Let's not forget all Facebook's previous scandals. From the Cambridge Analytica kerfuffle to [conducting](https://www.theregister.com/2014/06/29/researchers_mess_with_facebook_users_emotions/) manipulative social experiments in secret.
|
||||
|
||||
In light of this, the name change makes sense. It deceives you into thinking the company has evolved into a benevolent corporation, when it simply hasn't. Zuckerberg would much prefer you to think about Meta as a playful universe where you can meet with friends across the globe in virtual reality. Where humans train themselves to sound like heavily discounted robots. Where Facebook is not a Horrid Company.
|
||||
|
||||
Despite all this: Meta *is* Facebook, just worse. It doesn't matter about the new name, the company has not changed. It will still be violating our privacy, daily, on an unprecedented scale. It will still be as reliably scandalous as a Carry On film. It will still be terrible. Plus it will have all the added claptrap of a sub-par holographic universe attached.
|
||||
@ -1,61 +0,0 @@
|
||||
---
|
||||
title: 'Firefox Privacy: 2021 update'
|
||||
author: Daniel Gray
|
||||
background: firefox-privacy-2021.png
|
||||
template: overrides/blog.html
|
||||
excerpt: A lot changed between 2019 and now, not least in regards to Firefox.
|
||||
---
|
||||
|
||||
A lot changed between 2019 and now, not least in regards to Firefox. Since our last post, Mozilla has [improved](https://blog.mozilla.org/en/products/firefox/latest-firefox-rolls-out-enhanced-tracking-protection-2-0-blocking-redirect-trackers-by-default/) privacy with [Enhanced Tracking Protection (ETP)](https://blog.mozilla.org/en/products/firefox/firefox-now-available-with-enhanced-tracking-protection-by-default/). Earlier this year Mozilla introduced [Total Cookie Protection](https://blog.mozilla.org/security/2021/02/23/total-cookie-protection/) (Dynamic First Party Isolation dFPI). This was then further tightened with [Enhanced Cookie Clearing](https://blog.mozilla.org/security/2021/08/10/firefox-91-introduces-enhanced-cookie-clearing/). We're also looking very forward to [Site Isolation](https://blog.mozilla.org/security/2021/05/18/introducing-site-isolation-in-firefox/) (code named Fission) being enabled by default in the coming releases.
|
||||
|
||||
Now that so many privacy features are built into the browser, there is little need for extensions made by third-party developers. Accordingly, we have updated our very outdated [browser](/browsers) section. If you've got an old browser profile we suggest **creating a new one**. Some of the old advice may make your browser *more* unique.
|
||||
|
||||
#### Privacy Tweaks "about:config"
|
||||
|
||||
We're no longer recommending that users set `about:config` switches manually. Those switches need to be up to date and continuously maintained. They should be studied before blindly making modifications. Sometimes their behaviour changes in between Firefox releases, is superseded by other keys or they are removed entirely. We do not see any point in duplicating the efforts of the community [Arkenfox](https://github.com/arkenfox/user.js) project. Arkenfox has very good documentation in their [wiki](https://github.com/arkenfox/user.js/wiki) and we use it ourselves.
|
||||
|
||||
#### LocalCDN and Decentraleyes
|
||||
|
||||
These extensions aren't required with Total Cookie Protection (TCP), which is enabled if you've set Enhanced Tracking Protection (ETP) to **Strict**.
|
||||
|
||||
Replacing scripts on CDNs with local versions is not a comprehensive solution and is a form of [enumeration of badness](https://www.ranum.com/security/computer_security/editorials/dumb/). While it may work with some scripts that are included it doesn't help with most other third-party connections.
|
||||
|
||||
CDN extensions never really improved privacy as far as sharing your IP address was concerned and their usage is fingerprintable as this Tor Project developer [points out](https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/22089#note_2639603). They are the wrong tool for the job and are not a substitute for a good VPN or Tor. Its worth noting the [resources](https://git.synz.io/Synzvato/decentraleyes/-/tree/master/resources) for Decentraleyes are hugely out of date and would not be likely used anyway.
|
||||
|
||||
#### NeatURLs and ClearURLS
|
||||
|
||||
Previously we recommended ClearURLs to remove tracking parameters from URLs you might visit. These extensions are no longer needed with uBlock Origin's [`removeparam`](https://github.com/gorhill/uBlock/wiki/Static-filter-syntax#removeparam) feature.
|
||||
|
||||
#### HTTPS Everywhere
|
||||
|
||||
The EFF announced back in September they were [deprecating HTTPS-Everywhere](https://www.eff.org/deeplinks/2021/09/https-actually-everywhere) as most browsers now have an HTTPS-Only feature. We are pleased to see privacy features built into the browser and Firefox 91 introduced [HTTPS by Default in Private Browsing](https://blog.mozilla.org/security/2021/08/10/firefox-91-introduces-https-by-default-in-private-browsing/).
|
||||
|
||||
#### Multi Account Containers and Temporary Containers
|
||||
|
||||
Container extensions aren't as important as they used to be for privacy now that we have [Total Cookie Protection](https://blog.mozilla.org/security/2021/02/23/total-cookie-protection/).
|
||||
|
||||
Multi Account Container will still have some use if you use [Mozilla VPN](https://en.wikipedia.org/wiki/Mozilla_VPN) as it is going to be [integrated](https://github.com/mozilla/multi-account-containers/issues/2210) allowing you to configure specified containers to use a particular VPN server. Another use might be if you want to login to multiple accounts on the same domain.
|
||||
|
||||
#### Just-In-Time Compilation (JIT)
|
||||
|
||||
What is "Disable JIT" in Bromite? This option disables the JavaScript performance feature [JIT](https://en.wikipedia.org/wiki/Just-in-time_compilation). It can increase security but at the cost of performance. Those trade-offs vary wildly and are explored in [this](https://microsoftedge.github.io/edgevr/posts/Super-Duper-Secure-Mode/) publication by Johnathan Norman from the Microsoft Edge team. This option is very much a security vs performance option.
|
||||
|
||||
#### Mozilla browsers on Android
|
||||
|
||||
We don't recommend any Mozilla based browsers on Android. This is because we don't feel that [GeckoView](https://mozilla.github.io/geckoview) is quite as secure as it could be as it doesn't support [site isolation](https://hacks.mozilla.org/2021/05/introducing-firefox-new-site-isolation-security-architecture), soon to be coming in desktop browsers or [isolated processes](https://bugzilla.mozilla.org/show_bug.cgi?id=1565196).
|
||||
|
||||
We also noticed that there isn't an option for [HTTPS-Only mode](https://github.com/mozilla-mobile/fenix/issues/16952#issuecomment-907960218). The only way to get something similar is to install the [deprecated](https://www.eff.org/deeplinks/2021/09/https-actually-everywhere) extension [HTTPS Everywhere](https://www.eff.org/https-everywhere).
|
||||
|
||||
There are places which Firefox on Android shines for example browsing news websites where you may want to *partially* load some JavaScript (but not all) using medium or hard [blocking mode](https://github.com/gorhill/uBlock/wiki/Blocking-mode). The [reader view](https://support.mozilla.org/en-US/kb/view-articles-reader-view-firefox-android) is also pretty cool. We expect things will change in the future, so we're keeping a close eye on this.
|
||||
|
||||
#### Fingerprinting
|
||||
|
||||
Firefox has the ability to block known third party [fingerprinting resources](https://blog.mozilla.org/security/2020/01/07/firefox-72-fingerprinting/). Mozilla has [advanced protection](https://support.mozilla.org/kb/firefox-protection-against-fingerprinting) against fingerprinting (RFP is enabled with Arkenfox).
|
||||
|
||||
We do not recommend extensions that promise to change your [browser fingerprint](https://blog.torproject.org/browser-fingerprinting-introduction-and-challenges-ahead/). Some of those extensions [are detectable](https://www.cse.chalmers.se/~andrei/codaspy17.pdf) by websites through JavaScript and [CSS](https://hal.archives-ouvertes.fr/hal-03152176/file/style-fingerprinting-usenix.pdf) methods, particularly those which inject anything into the web content.
|
||||
|
||||
This includes **all** extensions that try to change the user agent or other browser behaviour to prevent fingerprinting. We see these often recommended on Reddit and would like to say that they will likely make you more unique and can be circumvented. Arkenfox has [a good list](https://github.com/arkenfox/user.js/wiki/4.1-Extensions#small_orange_diamond-%EF%B8%8F-anti-fingerprinting-extensions-fk-no) of extensions you shouldn't be using. They also have [another list](https://github.com/arkenfox/user.js/wiki/4.1-Extensions#small_orange_diamond-dont-bother) of extensions you needn't bother with either. We also like to say testing sites which show you how unique you are in a set of users are often using hugely tainted results that are not indicative of real-world usage.
|
||||
|
||||
---
|
||||
|
||||
*Special thanks to [Thorin-Oakenpants](https://github.com/Thorin-Oakenpants) and [Tommy](https://tommytran.io) for their help with providing advice and further documentation during the research phase.*
|
||||
@ -1,31 +0,0 @@
|
||||
---
|
||||
title: '"Move Fast and Break Things"'
|
||||
author: Freddy
|
||||
background: move-fast-and-break-things.jpg
|
||||
template: overrides/blog.html
|
||||
excerpt: "If someone has to tell you that they care about your privacy, they probably don't."
|
||||
---
|
||||
|
||||
Mark Zuckerberg does not look comfortable on stage. Yet, there he was proclaiming that "the future is private". If someone has to tell you that they care about your privacy, they probably don't.
|
||||
|
||||
For someone trying not to appear like a cartoon villain, Zuckerberg doesn't do a great job. He gives the impression of some strange cyborg algorithmically attempting to impersonate human life. His movements are not quite robotic, but he lacks the charisma you might expect from one of the most powerful people on the planet. A *New Yorker* [profile](https://www.newyorker.com/magazine/2018/09/17/can-mark-zuckerberg-fix-facebook-before-it-breaks-democracy) of him revealed that he had an affinity for Emperor Augustus, an ancient Roman tyrant. 'Through a really harsh approach, [Augustus] established two hundred years of world peace,' he said.
|
||||
|
||||
It's the first part of that sentence that is worrying.
|
||||
|
||||
Is this what Zuckerberg sees himself as: a modern-day emperor hellbent on using any means he can to gain world peace? Probably not, but it would have been reassuring if he just told us he liked doing Sudoku and dad-dancing with his daughter (interestingly named August).
|
||||
|
||||
The Zuck once [joked](https://www.esquire.com/uk/latest-news/a19490586/mark-zuckerberg-called-people-who-handed-over-their-data-dumb-f/) to a friend that he could get them 'info' about anyone in Harvard. He had email addresses, pictures, real addresses: the lot. When the friend asked how, this was his repost: 'People just submitted it. I don't know why. They trust me. Dumb f*cks.' We now live in a reality where Zuckerberg can get 'info' about almost anyone in the world.
|
||||
|
||||
Like a depraved tabloid journalist fishing through a minor celebrity's trash, Facebook collects everything it can about its users. Even if it means sifting through garbage, they want that data. But Facebook is not technically in the data business. It is in what author and professor Carissa Véliz [terms](https://aeon.co/essays/privacy-matters-because-it-empowers-us-all) 'the business of power' - which sounds rather more sinister than flogging off mildly irritating adverts.
|
||||
|
||||
Véliz argues that privacy is a form of power. It is the power to influence you, show you adverts and predict your behaviour. In this sense, personal data is being used to make us do things we otherwise would not do: to buy a certain product or to vote a certain way. Filmmaker Laura Poitras [described](https://www.washingtonpost.com/news/the-switch/wp/2014/10/23/snowden-filmmaker-laura-poitras-facebook-is-a-gift-to-intelligence-agencies/) Facebook as 'a gift to intelligence agencies'. It allows governments to arrest people planning to participate in protests before they have even begun.
|
||||
|
||||
The social media giant is tip-toeing ever closer into our personal lives. When Facebook encountered competition it just bought it, adding Instagram and WhatsApp to its roster. The company even tried to make its own cryptocurrency so that one day the Facebook would control all our purchases too. Earlier this year, the project was [killed](https://www.ft.com/content/a88fb591-72d5-4b6b-bb5d-223adfb893f3) by regulators. It is worth noting that when Zuckerberg purchased WhatsApp and Instagram, they had no revenue. Author Tim Wu notes in his book *The Attention Merchants* that Facebook is 'a business with an exceedingly low ratio of invention to success'. Perhaps that is a part of Zuck's genius.
|
||||
|
||||
'Move fast and break things' was the old company motto. When there were a few too many scandals, they moved fast and [rebranded](/blog/2021/11/01/virtual-insanity) to Meta. No one expected online privacy to be the 'thing' they broke.
|
||||
|
||||
Before it became a global behemoth, Facebook started out as a dorm-room project. Zuckerberg sat at his keyboard after a few drinks and built it mainly because he could. It now has nearly three billion users. In the same way, Facebook [conducted](https://www.theguardian.com/technology/2014/jul/02/facebook-apologises-psychological-experiments-on-users) social experiments seemingly just for fun. Why he did it doesn't really matter. As John Lanchester [put it](https://www.lrb.co.uk/the-paper/v39/n16/john-lanchester/you-are-the-product): he simply did it *because*.
|
||||
|
||||
It is unfair to say that Zuckerberg does not care about privacy - he does. That's why he [spared](https://www.theguardian.com/technology/2013/oct/11/mark-zuckerberg-facebook-neighbouring-houses) no expense buying the houses that surrounded his home. Zuckerberg knows the power of privacy, which is painfully ironic given he has built his career on exploiting it. For Zuckerberg, at least, the future is private. It's the rest of us that should be worried.
|
||||
|
||||
Cover Image: [Anthony Quintano](https://flickr.com/photos/22882274@N04/47774201581) / [Wikimedia Commons](https://commons.wikimedia.org/wiki/File:Mark_Zuckerberg_F8_2019_Keynote_(47774201581).jpg)
|
||||
@ -8,4 +8,3 @@ plugins:
|
||||
- privacy:
|
||||
externals_exclude:
|
||||
- cdn.jsdelivr.net/npm/mathjax@3/*
|
||||
- giscus.app/*
|
||||
|
||||
14
mkdocs.yml
14
mkdocs.yml
@ -63,21 +63,9 @@ nav:
|
||||
- 'Video Streaming': 'video-streaming.md'
|
||||
- 'About Us':
|
||||
- 'Privacy Guides': 'about.md'
|
||||
- 'Write for us!': 'about/bounty.md'
|
||||
- 'Notices': 'about/notices.md'
|
||||
- 'Privacy Policy': 'about/privacy-policy.md'
|
||||
- 'Blog':
|
||||
- 'Blog Index': 'blog.md'
|
||||
- '2022':
|
||||
- 'April':
|
||||
- '"Move Fast and Break Things"': 'blog/2022/04/04/move-fast-and-break-things.md'
|
||||
- '2021':
|
||||
- 'December':
|
||||
- 'Firefox Privacy: 2021 Update': 'blog/2021/12/01/firefox-privacy-2021-update.md'
|
||||
- 'November':
|
||||
- 'Virtual Insanity': 'blog/2021/11/01/virtual-insanity.md'
|
||||
- 'September':
|
||||
- 'Welcome to Privacy Guides': 'blog/2021/09/14/welcome-to-privacy-guides.md'
|
||||
- 'Blog': 'https://blog.privacyguides.org/'
|
||||
|
||||
theme:
|
||||
name: material
|
||||
|
||||
@ -1,25 +0,0 @@
|
||||
/* Blog hero section */
|
||||
.mdx-container {
|
||||
background-color: white;
|
||||
padding-top: 1rem;
|
||||
}
|
||||
|
||||
.mdx-hero {
|
||||
color: var(--md-primary-bg-color);
|
||||
margin: 0 0.8rem;
|
||||
text-align: center;
|
||||
}
|
||||
.mdx-hero h1 {
|
||||
color: currentcolor;
|
||||
font-weight: 700;
|
||||
margin-bottom: 1rem;
|
||||
font-size: 2rem;
|
||||
}
|
||||
@media screen and (max-width: 29.9375em) {
|
||||
.mdx-hero h1 {
|
||||
font-size: 1.4rem;
|
||||
}
|
||||
}
|
||||
.mdx-hero__content {
|
||||
padding-top: 1rem;
|
||||
}
|
||||
@ -1,71 +0,0 @@
|
||||
{% extends "base.html" %}
|
||||
{% block extrahead %}
|
||||
<link rel="stylesheet" href="{{ 'overrides/blog.css' | url }}">
|
||||
{% endblock %}
|
||||
{% block tabs %}
|
||||
{{ super() }}
|
||||
<style>.md-content > .md-typeset h1{visibility:hidden;font-size:0;}</style>
|
||||
<section class="mdx-container" {% if page.meta.background %}style="background-image:linear-gradient(to bottom, rgba(0, 0, 0, 0.5), rgba(0, 0, 0, 0.9)), url(/assets/img/blog/{{ page.meta.background }});padding-top:8rem;padding-bottom:4rem;background-size:cover;background-position:center;"{% endif %}>
|
||||
<div class="md-grid md-typeset">
|
||||
<div class="mdx-hero">
|
||||
<div class="mdx-hero__content" style>
|
||||
<h1 {% if page.meta.background %}style="color:white"{% endif %}>{{ page.meta.title }}</h1>
|
||||
{% if page.meta.excerpt %}<p {% if page.meta.background %}style="color:white"{% endif %}>{{ page.meta.excerpt }}</p>{% endif %}
|
||||
<nav class="md-tags">
|
||||
<span {% if page.meta.background %}style="color:white"{% endif %} class="md-tag">Author: {{ page.meta.author }}</span>
|
||||
</nav>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
{% endblock %}
|
||||
{% block content %}
|
||||
{{ super() }}
|
||||
|
||||
<!-- Giscus -->
|
||||
<h2 id="__comments">{{ lang.t("meta.comments") }}</h2>
|
||||
<script src="https://giscus.app/client.js"
|
||||
data-repo="privacyguides/privacyguides.org"
|
||||
data-repo-id="MDEwOlJlcG9zaXRvcnkzMTg0MDE5MDY="
|
||||
data-category="Blog"
|
||||
data-category-id="DIC_kwDOEvptcs4COX5p"
|
||||
data-mapping="title"
|
||||
data-reactions-enabled="1"
|
||||
data-emit-metadata="0"
|
||||
data-input-position="top"
|
||||
data-theme="light"
|
||||
data-lang="en"
|
||||
crossorigin="anonymous"
|
||||
async>
|
||||
</script>
|
||||
|
||||
<!-- Reload on palette change -->
|
||||
<script>
|
||||
var palette = __md_get("__palette")
|
||||
if (palette && typeof palette.color === "object")
|
||||
if (palette.color.scheme === "slate") {
|
||||
var giscus = document.querySelector("script[src*=giscus]")
|
||||
giscus.setAttribute("data-theme", "transparent_dark")
|
||||
|
||||
|
||||
}
|
||||
|
||||
/* Register event handlers after documented loaded */
|
||||
document.addEventListener("DOMContentLoaded", function() {
|
||||
var ref = document.querySelector("[data-md-component=palette]")
|
||||
ref.addEventListener("change", function() {
|
||||
var palette = __md_get("__palette")
|
||||
if (palette && typeof palette.color === "object") {
|
||||
var theme = palette.color.scheme === "slate" ? "transparent_dark" : "light"
|
||||
|
||||
/* Instruct Giscus to change theme */
|
||||
var frame = document.querySelector(".giscus-frame")
|
||||
frame.contentWindow.postMessage(
|
||||
{ giscus: { setConfig: { theme } } },
|
||||
"https://giscus.app"
|
||||
)
|
||||
}
|
||||
})
|
||||
})
|
||||
</script>
|
||||
{% endblock %}
|
||||
@ -14,7 +14,7 @@
|
||||
<a href="{{ 'tools/' | url }}" title="Recommended privacy tools, services, and knowledge" class="md-button md-button--primary">
|
||||
Recommended Tools
|
||||
</a>
|
||||
<a href="{{ 'blog/' | url }}" title="Blog posts from Privacy Guides contributors" class="md-button">
|
||||
<a href="https://blog.privacyguides.org/" title="Blog posts from Privacy Guides contributors" class="md-button">
|
||||
Read our blog
|
||||
</a>
|
||||
</div>
|
||||
|
||||
Loading…
Reference in New Issue
Block a user