dandri/simplex-chat
1
0
Fork 0
mirror of https://github.com/simplex-chat/simplex-chat.git synced 2026-04-28 21:26:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

deploy: 9c44ff404e

Browse Source
This commit is contained in:
epoberezkin
2025-01-14 19:50:05 +00:00
parent 4f270e345c
commit 855d5853d5
4 changed files with 4 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
blog/20250114-simplex-network-large-groups-privacy-preserving-content-moderation.html
+1 -1
View File
@@ -434,7 +434,7 @@ window.addEventListener('scroll',changeHeaderBg);
<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>
blog/index.html
+1 -2
View File
@@ -434,8 +434,7 @@ window.addEventListener('scroll',changeHeaderBg);
14 Jan 2025
</p>
<p class="dark:text-white mb-4">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.</p>
<p class="dark:text-white mb-4">This post explains how server operators can moderate end-to-end encrypted conversations without compromising user privacy or <span data-glossary="tooltip-end-to-end-encryption" class="glossary-term">End-to-end encryption</span>.</p>
</div>
<a class="block text-primary-light dark:text-[#70F0F9] text-base font-medium tracking-[0.03em] mt-auto" href="/blog/20250114-simplex-network-large-groups-privacy-preserving-content-moderation.html">Read More</a>
feed.atom
+1 -1
View File
@@ -3332,7 +3332,7 @@ A few bugs and UX issues but great foundation. Love that it’s public domain.&l
&lt;p&gt;Once the servers receive the file identifiers, they can now block the file.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;File servers cannot look inside end-to-end encrypted files, and they don&#39;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.&lt;/p&gt;
&lt;p&gt;File servers cannot look inside end-to-end encrypted files, and they don&#39;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&#39;t allow us to access any other user data or files.&lt;/p&gt;
&lt;p&gt;In this way, the moderation is possible without any content scanning, preserving privacy and security of end-to-end encryption.&lt;/p&gt;
&lt;h2 id=&quot;privacy-preserving-content-moderation&quot; tabindex=&quot;-1&quot;&gt;Privacy preserving content moderation&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
feed.rss
+1 -1
View File
@@ -59,7 +59,7 @@
&lt;p&gt;Once the servers receive the file identifiers, they can now block the file.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;File servers cannot look inside end-to-end encrypted files, and they don&#39;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.&lt;/p&gt;
&lt;p&gt;File servers cannot look inside end-to-end encrypted files, and they don&#39;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&#39;t allow us to access any other user data or files.&lt;/p&gt;
&lt;p&gt;In this way, the moderation is possible without any content scanning, preserving privacy and security of end-to-end encryption.&lt;/p&gt;
&lt;h2 id=&quot;privacy-preserving-content-moderation&quot; tabindex=&quot;-1&quot;&gt;Privacy preserving content moderation&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;