Brave Is Bypassing Google AMP Pages Because They're 'Harmful To Users'

Brave announced a new feature for its browser on Tuesday: De-AMP, which automatically jumps past any page rendered with Google's Accelerated Mobile Pages framework and instead takes users straight to the original website. The Verge reports: "Where possible, De-AMP will rewrite links and URLs to prevent users from visiting AMP pages altogether," Brave said in a blog post. "And in cases where that is not possible, Brave will watch as pages are being fetched and redirect users away from AMP pages before the page is even rendered, preventing AMP / Google code from being loaded and executed." Brave framed De-AMP as a privacy feature and didn't mince words about its stance toward Google's version of the web. "In practice, AMP is harmful to users and to the Web at large," Brave's blog post said, before explaining that AMP gives Google even more knowledge of users' browsing habits, confuses users, and can often be slower than normal web pages. And it warned that the next version of AMP -- so far just called AMP 2.0 -- will be even worse. Brave's stance is a particularly strong one, but the tide has turned hard against AMP over the last couple of years. Google originally created the framework in order to simplify and speed up mobile websites, and AMP is now managed by a group of open-source contributors. It was controversial from the very beginning and smelled to some like Google trying to exert even more control over the web. Over time, more companies and users grew concerned about that control and chafed at the idea that Google would prioritize AMP pages in search results. Plus, the rest of the internet eventually figured out how to make good mobile sites, which made AMP -- and similar projects like Facebook Instant Articles -- less important.

Read more of this story at Slashdot.