Add "Redirect AMP to HTML" to FF addons #585

Closed
opened 2018-11-13 12:36:06 +00:00 by ghost · 4 comments
ghost commented 2018-11-13 12:36:06 +00:00 (Migrated from github.com)

I believe we should consider adding Redirect AMP to HTML to the addons section.

It was previously discussed in this reddit thread

I believe we should consider adding [Redirect AMP to HTML](https://www.daniel.priv.no/web-extensions/amp2html) to the [addons](https://www.privacytools.io/#addons) section. It was previously discussed in [this reddit thread](https://www.reddit.com/r/privacytoolsIO/comments/9slnf5/redirect_amp_to_html)
ghost commented 2019-04-05 14:17:01 +00:00 (Migrated from github.com)

Why was this closed? Also I dun goofed on the URL it's supposed to be:

https://www.daniel.priv.no/web-extensions/amp2html.html

Why was this closed? Also I dun goofed on the URL it's supposed to be: https://www.daniel.priv.no/web-extensions/amp2html.html

I don't know, I agree this should probably be discussed.

I don't know, I agree this should probably be discussed.
blacklight447 commented 2019-08-09 20:00:03 +00:00 (Migrated from github.com)

to continue discussion: i would say this would be a bit out of scope, we already recommend a lot of extensions, and we cant just keep adding more to fix every single issue on the web. the more extensions a user has to install, the more likely they wont install them at all because they get overwhelmed. furthermore, adding tons of addons can also slow down your browser, increase browsing fingerprint, and add more attack surface. seeing how this addon doesn't even have any direct privacy benefits, i do not think we should add it.

to continue discussion: i would say this would be a bit out of scope, we already recommend a lot of extensions, and we cant just keep adding more to fix every single issue on the web. the more extensions a user has to install, the more likely they wont install them at all because they get overwhelmed. furthermore, adding tons of addons can also slow down your browser, increase browsing fingerprint, and add more attack surface. seeing how this addon doesn't even have any direct privacy benefits, i do not think we should add it.

Thank you @blacklight447-ptio.

At another glance I’m going to close this again. Seeing as you’re hitting Google’s servers anyways, even if you’re immediately redirected after, this tool doesn’t appear to add a privacy benefit to the user. The actual privacy solution is to stop using Google.

Thank you @blacklight447-ptio. At another glance I’m going to close this again. Seeing as you’re hitting Google’s servers anyways, even if you’re immediately redirected after, this tool doesn’t appear to add a *privacy* benefit to the user. The actual privacy solution is to stop using Google.
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#585
No description provided.