* Fix some typos, grammar, etc. on the site Fixes some issues with typos, capitalization, grammar, and et cetera. * Fix typo, grammar, etc. in repository * Update README.md Mention Discourse community earlier, add missing period * Update CONTRIBUTING.md i.e. is used for equivalence or clarification while e.g. is for examples. For instance, we shouldn't say that IMAP is equivalent or an explanation to all open-source software used to access email (e.g. there's POP3, open-source clients to access when there isn't IMAP such as Tutanota, etc.). We also shouldn't call IMAP open-source software since it's a protocol. * Change "socially motivated * Apply suggestions from code review Co-Authored-By: Jonah Aragon <jonah@triplebit.net> * Suggestion from code review with extras * 'Kill switch' to 'Killswitch" * Consistency and minor additions to details - More parallel sentence structures, following <Name> <Verb phrase> for the first sentence of cards. Related to issue #1420. - Make Njalla parallel to the others, and mention Njalla is based in Nevis with VPS in Sweden - Don't use "us" when talking about external services - Orange Website also provides domain registration - Update capitalization and add more hyphens - Mention that TOS;DR evaluations are done by the community and that they also evaluate privacy policies (see https://edit.tosdr.org/about) - "E2EE encryption" is redundant since "E2EE" already has "encryption" in it. Might as well expand it since full term is used later on. - <Name> <Verb phrase> structure for Magic Wormhole - For consistency, don't start Worth Mentioning entries with the name - https://english.stackexchange.com/questions/27707/post-hyphenation-of-split-compound-words - All the other "alert alert-warning" don't repeat the generic name and we also don't say 'a software' * instant-messenger: Remove <em>, more cleanup * voice-video-messenger: Hyphens and cleanup - We don't say "a software" so replace it with something that works * paste-services: Cleanup & change cryptography info As per CryptPad's whitepaper and FAQ: https://cryptpad.fr/faq.html#security-crypto https://blog.cryptpad.fr/images/CryptPad-Whitepaper-v1.0.pdf Fixes #1417. * encryption: "open-source" * Page descriptions and other cleanup
3.7 KiB
Encryption Against Global Mass Surveillance.
Contributing
It's important for a website like privacytools.io to be up-to-date. Keep an eye on software updates of the applications listed here. Follow recent news about providers that are recommended. We try our best to keep up but we're not perfect and the internet is changing fast. So if you find an error, or you think a provider should not be listed here, or a qualified service provider is missing or a browser plugin is not the best choice anymore or anything else...
Talk to us please. Join our subreddit or our Discourse community and start a discussion. This is a community project and we're aiming to deliver the best information available for a better privacy. Thank you for participating.
You can submit your suggestions here on GitHub (Issues) and also in our subreddit. Please refer to the Contributing Guidelines before submitting. Thank you.
Building
- Install Ruby
- Install bundler by running
gem install bundler
. - Run
bundle install
to install the required dependencies. - Use
bundle exec jekyll build
to build the website. The output can be found in the_site
directory. Live preview is also possible by runningbundle exec jekyll serve
Support privacytools.io
- Donate.
- Liberapay or Patreon.
- Spread the word.
- Join our Discourse community.
- Make suggestions on reddit.
- View and edit our website source code here on GitHub.
Community Translations
- 繁体中文 / Chinese - GitHub
- Español / Spanish - GitLab
- Polski / Polish - Gitea
- Deutsch / German - GitHub
- Français / French - GitLab
- Italiano / Italian - GitHub
- Русский / Russian - GitHub
- Português / Portuguese - GitHub
License
The content and original technology of this website is made available under the Creative Commons Zero v1.0 Universal license text. Some files or folders may include works from other projects with separate licenses, and will be marked as such. By contributing to this repository, contributors do not necessarily agree to sign a CLA or legally transfer their copyright to the project, but they do at a minimum agree to license their work under the current license of this repository: In this case, the Creative Commons Zero v1.0 Universal.