Git-Mirrors/privacyguides.org
1
0
Fork 0
mirror of https://github.com/privacyguides/privacyguides.org.git synced 2025-04-18 06:26:09 -04:00
Code Issues Packages Projects Releases Wiki Activity

style: Subject-verb agreement

Browse Source 
Signed-off-by: redoomed1 <redoomed1@privacyguides.org>
This commit is contained in:
redoomed1 2025-03-20 14:24:52 -07:00 committed by GitHub
parent 638107018e
commit 828e90755a
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/real-time-communication.md
View File

@ -276,11 +276,11 @@ Session has a [white paper](https://arxiv.org/pdf/2002.04609.pdf) describing the
Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page.
- Should supports forward secrecy[^1]
- Should support forward secrecy[^1]
- Should support Future Secrecy (Post-Compromise Security)[^2]
- Should have open-source servers.
- Should use a decentralized network, i.e. [federated or P2P](advanced/communication-network-types.md).
- Should uses E2EE for all messages by default.
- Should use E2EE for all messages by default.
- Should support Linux, macOS, Windows, Android, and iOS.
[^1]: [Forward secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) is where keys are rotated very frequently, so that if the current encryption key is compromised, it does not expose **past** messages as well.