Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AMP breaks url-based content filters #19170

Closed
duane opened this issue Nov 7, 2018 · 2 comments
Closed

AMP breaks url-based content filters #19170

duane opened this issue Nov 7, 2018 · 2 comments

Comments

@duane
Copy link

duane commented Nov 7, 2018

This applies to all url-based content filters, but I am writing specifically based on firefox focus.

For instance, if you block reddit.com, it is still easily accessible via searches from engines which integrate AMP, which rather defeats the point of content filters.

Possible solution: allow an opt-out that either links to the search result or redirects to it. Alternatively, make AMP opt-in, or somehow allow loading AMP results from the domain of the content.

Either way, this makes search engines that enable AMP integration problematic in the current state.

@duane
Copy link
Author

duane commented Nov 7, 2018

Another option would be to allow blacklisting urls at the AMP or search engine level.

@jpettitt
Copy link
Contributor

jpettitt commented Nov 7, 2018

This is not an AMP bug, it's a content filter bug. All url based content filters are going to be trivially bypassed via proxy or cache servers.

AMP cache urls are deterministic and contient filters can can easily add code to map canonical -> camp cache urls if they want to filter AMP pages. See AMP Cache URL format

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants