Clarify source availability in MFA criteria (#2113)

This commit is contained in:
Jonah Aragon 2023-04-10 22:53:11 +00:00 committed by GitHub
parent b074ed9401
commit 0e457065a0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -132,7 +132,7 @@ We highly recommend that you use mobile TOTP apps instead of desktop alternative
We are working on establishing defined criteria for every section of our site, and this may be subject to change. If you have any questions about our criteria, please [ask on our forum](https://discuss.privacyguides.net/latest) and don't assume we didn't consider something when making our recommendations if it is not listed here. There are many factors considered and discussed when we recommend a project, and documenting every single one is a work-in-progress. We are working on establishing defined criteria for every section of our site, and this may be subject to change. If you have any questions about our criteria, please [ask on our forum](https://discuss.privacyguides.net/latest) and don't assume we didn't consider something when making our recommendations if it is not listed here. There are many factors considered and discussed when we recommend a project, and documenting every single one is a work-in-progress.
- Must be open-source software. - Source code must be publicly available.
- Must not require internet connectivity. - Must not require internet connectivity.
- Must not sync to a third-party cloud sync/backup service. - Must not sync to a third-party cloud sync/backup service.
- **Optional** E2EE sync support with OS-native tools is acceptable, e.g. encrypted sync via iCloud. - **Optional** E2EE sync support with OS-native tools is acceptable, e.g. encrypted sync via iCloud.