Archived
EARN IT ACT, a workaround for banning E2EE #1677
Merged
dngray
merged 1 commits from 2020-02-01 02:52:40 +00:00
pr-earn_it_banning_e2ee into master
Labels
Clear labels
:mag:🤖 Search Engines
I2P
OS
Self-contained networks
Social media
Tor
WIP
XMPP
[m]
approved
dependencies
duplicate
feedback wanted
high priority
iOS
low priority
stale
streaming
todo
wontfix
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
🆕 software suggestion
🆘 critical
🇦🇶 translations
🌐 Social News Aggregators
🌐 hosting
🌐 website issue
🏠 housekeeping
🐛 bug
👁️ browsers
👥 team chat
💢 conflicting
💬 discussion
💻 hardware
📁 file storage
📝 correction
📧 email
🔎 research required
🔐 password managers
🔒 VPN
🔒 file encryption
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🚫 Windows
🤖 Android
🦊 Firefox
🧰 productivity tools
The Invisible Internet Project (I2P)
Operating Systems
Anything covering the Tor network
active work in progress, do not merge or PR (yet)!
Extensible Messaging and Presence Protocol
Matrix protocol
approved, waiting for a PR
Pull requests that update a dependency file
A label for stalebot if it gets added
Anything related to media streaming.
Issues or bugs that will not be fixed and/or do not have significant impact on the project.
Browser Extension related issues
Anything covering a translated version of the site
*Technical* issues with the website.
Anything primarily related to site cleanup.
Correction of content on the website
Virtual Private Network
Domain Name System
Firefox & forks, about:config etc.
No labels
Milestone
No items
No Milestone
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#1677
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I guess AG Barr is back from Christmas holidays!
Latest news on the war on end to end encryption.
Deploy preview for privacytools-io ready!
Built with commit
e056338adahttps://deploy-preview-1677--privacytools-io.netlify.com
okay done, now I'm waiting for my $11
Seems technical and would probably need more focusing than I am able to provide while attempting to focus on listening event around me, so I am mostly trusting you
The TLDR of it is that, companies like Facebook, Twitter etc have "safe harbor" meaning if someone uploads something illegal they are not held responsible for the possession of the content on their servers. They obviously do remove such content and report to law enforcement.
In this case they're talking about CSAM, (child pornography). The issue being here is they want to set up a "commission" that basically makes "best practices" in dealing with the content. The thing is if the company doesn't follow the "best practices" they lose their safe harbor protection.
The commission only requires 10 of the 15 members to agree, and none of them are civil liberties representatives. Language is extremely weak, for example they "shall consider" in "interests in privacy, data security, and product quality", which basically means nothing, they can consider it for 5 seconds and then go "nope".
They also say that the officers must "certify" regardless of if they know what they are saying is a lie. In the end all the "recommendations" are signed off by the AG unilaterally, which is currently William Barr.
So it will end up being very much law enforcement saying, ban all E2EE because child pornographers could use it, so it's a best practice that nobody has it. That document also says it won't really help with that because there is absolutely nothing stopping such criminals from either using self contained networks, (Tor, I2P, Freenet etc) or encrypting the files before they upload them.