De-AMP links tainted by Google

[Gymcap]

As many know, Googles attempt to rehost websites and normalize the AMP framework is a threat to not only our privacy, but the open internet as a whole.

It would be nice to have the extension make this a non-issue by automatically de-amp-ing any tainted links I happen to click on.

[SimonBrazell]

Hi @Gymcap I can certainly look into it, do you have some examples of an AMP and de-Amp'd links I can look at?

[cloudrac3r]

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

https://github.com/da2x/amp2html

[SimonBrazell]

Thanks for the links @cloudrac3r, this feature seems like a worthy addition to the extension.

[seniorm0ment]

+1 to this, Fuck AMP. Although I do believe uBlock can redirect AMP, I could be wrong. Worth noting though.

[DJCrashdummy]

perhaps worth mentioning here: Redirect AMP to HTML

---

sorry for bothering, haven't checked the other links mentioned above. :facepalm:

[SimonBrazell]

Thanks, I want to do this and some of the other suggestions but I have no time lately unfortunately, maybe next month.

[DJCrashdummy]

please @SimonBrazell, absolutely no pressure!

as written, i just thought it may be worth mentioning it (to take ideas/code or even show it to other interested users), although i should have taken a better look at already posted links! :stuck_out_tongue_winking_eye:

but still i'm not 100% sure if it is a good idea to pack additional functions into this one addon as mentioned at https://github.com/SimonBrazell/privacy-redirect/issues/43#issuecomment-627383827. :thinking:

[cloudrac3r]

I also think that since amp2html already exists as an extension, there's no need to copy its behavior into this extension. We can just do one thing and do it well.

[SimonBrazell]

@cloudrac3r makes a good point, if there is already an existing extension that is actively maintained then perhaps we shouldn't over complicate things here? I can see it targets all major browsers too so there doesn't seem to be any gaps that we can fill.

[polzon]

To play devil advocate here: I would rather have an all-in-one extension, rather then two extensions. Currently I'm able to replicate most of Privacy Redirect's functions using just the HTTPS-Everywhere extension, but stick with it since it provides a lot of convenience, like toggling specific redirect on and off.

Also, as a user, installing more extensions into my browser adds additional attack surface leaving me more potentially vulnerable. In theory, it's easier for me to audit one extension the two.

In my opinion, an AMP redirect still fits under the category of privacy redirection, so I'd love it if I could have that all in one extension. I don't think adding De-AMP would go against the project goal of "doing one thing well".

[theotheroracle]

on the other hand it makes extensions more modular and lets users pick what functionality they want from different extensions