This increases user privacy, helps publishers stay independent, and will often improve page-load time and memory performance, too. Brave’s default protections will circumvent AMP pages (or “de-AMP” them), and load the canonical version of the page instead. With AMP, instead of visiting the origin Web page on your browser, you load a version of the page that’s cached on Google’s servers, which gives Google unwarranted visibility into your browsing. But in practice, AMP strengthens Google’s monopoly, and gives Google an even broader view of the pages people view, and how they interact with those pages. In theory, AMP helps Web pages load faster and look cleaner. De-AMP-ing pages to add more protections against Googleįirst announced last week, 1.38 also includes Brave’s de-AMP-ing protections.Īccelerated Mobile Pages (AMP) are a non-standard publishing format, designed and pushed by Google. Just click / tap the in the address bar on any page you visit. With Shields you can see all the privacy threats that Brave blocked. The redesign also makes it more intuitive to adjust Shields settings if Brave’s protections stopped a page from loading as expected. Release 1.38 brings a refresh of the Brave Shields design, making it even easier to use. With Brave, you just download and browse. And Shields work out-of-the-box: there’s no extra download, no settings to configure. Shields help block the ads, cookies, fingerprinting, and other tracking techniques that allow you to be tracked online. Shields are an integral part of how Brave protects your privacy.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |