mirror of
https://github.com/privacyguides/privacyguides.org.git
synced 2025-07-02 17:42:39 +00:00
style!: Make minor changes across recommendation pages for consistency (#2972)
- Grammar, Style, and Wording Changes - Remove commas where pauses or breaks in reading may not be needed - Reduce instances of comma splices by replacing commas with semicolons or em dashes where appropriate - Spell out abbreviations like E2EE for the first instance of the term on the page, then use the abbreviation for the subsequent instances - Add line breaks in card descriptions for a cleaner look, particularly for mentions of an accompanying blog review of a tool - Move more technical information from recommendation blurb to the description under the card - Format quotations from audits as block quotes - Standardize syntax for tooltips - Arrange download links according to the widely used order - Mobile app stores > alternative distribution methods (e.g., GitHub) > developer-owned or -operated F-Droid repositories >> desktop platforms > Flathub >> browsers >> web - Shorten Chrome extension links - Standardize icon for web download links - For "Repository" buttons, embed direct links to project's Readme to differentiate them from "Source Code" links - Other Changes - Add GitHub releases link for IVPN - Mention CryptPad's official public instance and add link to list of public instances - Replace current link to Miniflux docs with a direct link to the end user docs - Update version of Newsboat documentation link - Update and reword guidance on finding YouTube channel code for RSS feed - Remove F-Droid download link for Stingle since it is not owned by the developer or dev team Signed-off-by: Jonah Aragon <jonah@privacyguides.org> Signed-off-by: fria <fria@privacyguides.org> Signed-off-by: Daniel Gray <dngray@privacyguides.org>
This commit is contained in:
@ -149,5 +149,6 @@ Also, unlike Tor, every I2P node will relay traffic for other users by default,
|
||||
|
||||
There are downsides to I2P's approach, however. Tor relying on dedicated exit nodes means more people in less safe environments can use it, and the relays that do exist on Tor are likely to be more performant and stable, as they generally aren't run on residential connections. Tor is also far more focused on **browser privacy** (i.e. anti-fingerprinting), with a dedicated [Tor Browser](tor.md) to make browsing activity as anonymous as possible. I2P is used via your [regular web browser](desktop-browsers.md), and while you can configure your browser to be more privacy-protecting, you probably still won't have the same browser fingerprint as other I2P users (there's no "crowd" to blend in with in that regard).
|
||||
|
||||
[^1]: The `IsolateDestAddr` setting is discussed on the [Tor mailing list](https://lists.torproject.org/pipermail/tor-talk/2012-May/024403) and [Whonix's Stream Isolation documentation](https://whonix.org/wiki/Stream_Isolation), where both projects suggest that it is usually not a good approach for most people.
|
||||
Tor is likely to be more resistant to censorship, due to their robust network of bridges and varying [pluggable transports](https://tb-manual.torproject.org/circumvention). On the other hand, I2P uses directory servers for the initial connection which are varying/untrusted and run by volunteers, compared to the hard-coded/trusted ones Tor uses which are likely easier to block.
|
||||
|
||||
[^1]: The `IsolateDestAddr` setting is discussed on the [Tor mailing list](https://lists.torproject.org/pipermail/tor-talk/2012-May/024403) and [Whonix's Stream Isolation documentation](https://whonix.org/wiki/Stream_Isolation), where both projects suggest that it is usually not a good approach for most people.
|
||||
|
Reference in New Issue
Block a user