Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Cloudflare is doing this AMP crap too. If a cloudflare user enables AMP on his site then links from their domain to yours will trigger a visit of Mozilla/5.0 (compatible; Cloudflare-AMP/1.0; +https://amp.cloudflare.com/bot) AppleWebKit/534.34" which then mirrors the content from your domain and re-hosts it on Cloudflare servers.

Then whenever someone goes to the Cloudflare user's website and clicks a link to your website they'll instead be fed a version of the page from Cloudflare and you'll never see that traffic.

And since you (or me, in this case) don't have a Cloudflare account you can't get any response from Cloudflare support to get them to stop re-hosting and serving your content from their servers.



Requests from non-user accounts do still get responses, just not quickly. You may have more luck with Twitter.


Publisher's see AMP traffic since they are in control of ads and analytics used in amp page.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: