From 855d5853d5eb8c948ce3fbffef67559f7d43f263 Mon Sep 17 00:00:00 2001 From: epoberezkin Date: Tue, 14 Jan 2025 19:50:05 +0000 Subject: [PATCH] deploy: 9c44ff404ee8ab6f1c25dcce3666fdf8ca73db88 --- ...ork-large-groups-privacy-preserving-content-moderation.html | 2 +- blog/index.html | 3 +-- feed.atom | 2 +- feed.rss | 2 +- 4 files changed, 4 insertions(+), 5 deletions(-) diff --git a/blog/20250114-simplex-network-large-groups-privacy-preserving-content-moderation.html b/blog/20250114-simplex-network-large-groups-privacy-preserving-content-moderation.html index 43ae77ab1b..5a452d2320 100644 --- a/blog/20250114-simplex-network-large-groups-privacy-preserving-content-moderation.html +++ b/blog/20250114-simplex-network-large-groups-privacy-preserving-content-moderation.html @@ -434,7 +434,7 @@ window.addEventListener('scroll',changeHeaderBg);

Once the servers receive the file identifiers, they can now block the file.

-

File servers cannot look inside end-to-end encrypted files, and they don't even know file sizes – they are securely locked, and sent in chunks, across multiple servers. But if file recipient gives us the keys to some file, we can unlock it and look inside. If it violates conditions of use, we can remove or block this file.

+

File servers cannot look inside end-to-end encrypted files, and they don't even know file sizes – they are securely locked, and sent in chunks, across multiple servers. But if file recipient gives us the address and decryption key of the particular file (each file is encrypted by a different set of keys), we can receive this file. If it violates conditions of use, we can remove or block this file. It doesn't allow us to access any other user data or files.

In this way, the moderation is possible without any content scanning, preserving privacy and security of end-to-end encryption.

Privacy preserving content moderation

Right now, when we act on user complaints, we delete uploaded files or the links to join the groups from our servers, and to the users it looks as if something stopped working.

diff --git a/blog/index.html b/blog/index.html index 061ed79db2..dea877e6c7 100644 --- a/blog/index.html +++ b/blog/index.html @@ -434,8 +434,7 @@ window.addEventListener('scroll',changeHeaderBg); 14 Jan 2025

-

How can server operators moderate end-to-end encrypted conversations? -File servers can't look inside files – they are securely locked. But if file recipient gives us the keys to some file, we can unlock it and look inside. If it violates conditions of use, we can remove or block this file.

+

This post explains how server operators can moderate end-to-end encrypted conversations without compromising user privacy or End-to-end encryption.

Read More diff --git a/feed.atom b/feed.atom index f1a64e2f05..1bcc74c606 100644 --- a/feed.atom +++ b/feed.atom @@ -3332,7 +3332,7 @@ A few bugs and UX issues but great foundation. Love that it’s public domain.&l <p>Once the servers receive the file identifiers, they can now block the file.</p> </li> </ol> -<p>File servers cannot look inside end-to-end encrypted files, and they don't even know file sizes – they are securely locked, and sent in chunks, across multiple servers. But if file recipient gives us the keys to some file, we can unlock it and look inside. If it violates conditions of use, we can remove or block this file.</p> +<p>File servers cannot look inside end-to-end encrypted files, and they don't even know file sizes – they are securely locked, and sent in chunks, across multiple servers. But if file recipient gives us the address and decryption key of the particular file (each file is encrypted by a different set of keys), we can receive this file. If it violates conditions of use, we can remove or block this file. It doesn't allow us to access any other user data or files.</p> <p>In this way, the moderation is possible without any content scanning, preserving privacy and security of end-to-end encryption.</p> <h2 id="privacy-preserving-content-moderation" tabindex="-1">Privacy preserving content moderation</h2> <p>Right now, when we act on user complaints, we delete uploaded files or the links to join the groups from our servers, and to the users it looks as if something stopped working.</p> diff --git a/feed.rss b/feed.rss index c81857ae0a..350f33b92f 100644 --- a/feed.rss +++ b/feed.rss @@ -59,7 +59,7 @@ <p>Once the servers receive the file identifiers, they can now block the file.</p> </li> </ol> -<p>File servers cannot look inside end-to-end encrypted files, and they don't even know file sizes – they are securely locked, and sent in chunks, across multiple servers. But if file recipient gives us the keys to some file, we can unlock it and look inside. If it violates conditions of use, we can remove or block this file.</p> +<p>File servers cannot look inside end-to-end encrypted files, and they don't even know file sizes – they are securely locked, and sent in chunks, across multiple servers. But if file recipient gives us the address and decryption key of the particular file (each file is encrypted by a different set of keys), we can receive this file. If it violates conditions of use, we can remove or block this file. It doesn't allow us to access any other user data or files.</p> <p>In this way, the moderation is possible without any content scanning, preserving privacy and security of end-to-end encryption.</p> <h2 id="privacy-preserving-content-moderation" tabindex="-1">Privacy preserving content moderation</h2> <p>Right now, when we act on user complaints, we delete uploaded files or the links to join the groups from our servers, and to the users it looks as if something stopped working.</p>