github.com
Glad they fixed it. They got my issue fixed as well.Update:
After my reporting the Adguard issue related to The Verge has been fixed today with a commit to Adguard Tracking Protection filter
Fix #54102 theverge.com · AdguardTeam/AdguardFilters@4356df9
AdGuard Content Blocking Filters. Contribute to AdguardTeam/AdguardFilters development by creating an account on GitHub.
The issue was related to google tag manager script that Adguard filters was having trouble blocking on that page. This is not DNS related and since DNS can't block scripts and googletagmanager(.)com the domain is not present in Adguard DNS, you're having the issue. Something like EasyList filter didn't have this issue. Edge with strict anti-tracking probably blocks googletagmanager so the page is loading fast for you there.
I guess it gets updated, once it gets updated in the official extension store?
Yes, it's the same for all extensions.
github.com
It's been a while since we published a blog post about the AdGuard Browser Extension release. But no worries, we're still developing it, as you can see by checking our Github repo. In this post, we'll tell you what's changed in the version 3.6.
In addition to "Do-Not-Track", another signal appeared in the Stealth Mode settings — "Global Privacy Control". These signals are sent to the websites you are visiting not to track you. Besides, we've added support for the $removeparam modifier and AdGuard URL Tracking filter that removes tracking parameters from page URLs — this filter is already in AdGuard for Windows and Mac, and now it's time to add it in AdGuard Browser Extension, too. Finally, we've updated scriptlets, redirects and extended CSS.
Global Privacy Control signal
Global Privacy Control (GPC) is a signal transmitted over HTTP. It sends a request to the websites or services visited by the user not to sell or share their (user's) personal data with third parties.
Why GPC appeared and why it is necessary
As you probably know, many companies abuse their capabilities: they violate users' privacy by collecting, analyzing and selling their data, or share it with third parties. And while there are legal frameworks that allow users to demand privacy protection, doing so is inconvenient and impractical — the user has to reassert their position at each visited website: reject cookie notices or ask a website/app not to track.
California Attorney General's Final Statement:
Given the ease and frequency by which personal information is collected and sold when a consumer visits a website, consumers should have a similarly easy ability to request to opt-out globally.
By enabling the GPC signal, you inform the websites of your privacy preferences. For instance, whether you want your personal information to be sold or shared (we have no doubt that you don't). Your browser sends signals to the websites you visit, and the ones that support GPC will respect your right to privacy. GPC is supported by many organizations, AdGuard included. You can see some of them on the official Global Privacy Control website.
GPC will soon be added to other AdGuard products with Stealth Mode.
AdGuard URL Tracking filter
Not so long ago we told about the new AdGuard URL Tracking filter, explaining what tracking parameters are, how they are used, and why they should be removed, but we can't help but describe the filter here as well.
AdGuard URL Tracking filter has incorporated all the most popular tracking parameters. The best part about it is that you can now remove tracking parameters simply by turning this filter on. Before it was created, there was a problem with the list of parameters: they were embedded into the program, and it wasn't easy to add new parameters to it. By creating the URL Tracking filter, we opened the door for its regular updating and augmenting, and we intend to augment it as actively as we do with the other filters.
By adding $removeparam modifier support, we managed to get rid of the former "Remove Tracking Parameters" setting and replace it with a new one that includes our URL Tracking Filter. This ensures that you'll always be using the most up-to-date database of tracking parameters, thanks to the standard filter update mechanism.
You are now familiar with the latest changes to the AdGuard Browser Extension. As always, we'd love to hear your impressions of the new version, please tell us if everything works well or what you especially like. Or maybe you'd like a new feature to be added in the extension? Any feedback is welcome, moreover, it helps us make our products better. So, waiting for your reviews
This is a huge disadvantage and not only provide false sense of privacy but also unique fingerprint.
Meet AdGuard Browser Extension v4.0! It’s not a mere update, but a major release that delivers a pack of new features to the users of the extension.
Code refactoring and new filtering engine
Refactoring has become sort of a buzzword that implies massive code rewriting, which we did to complicate our lives and make it easier in the long run. Besides, we added support for TSUrlFilter, our new filtering platform that implements AdGuard content blocking rules.
TSUrlFilter is a filtering engine. In AdGuard apps, its role is performed by CoreLibs, and if happen to read release notes, you must have heard about it more than once. TSUrlFilter is a rule application module that will be used in various projects, including AdGuard DNS.
Responsive design
We switched to responsive (or adaptive) design. That is to say, that interface elements will adapt to screen size both on desktop and mobile devices, redardless of the model.
This is convenient both for us, because we don't need to develop separate versions of the Browser extension, and for users — it's always nice when an app (or a browser extension, in the case given) looks good.
Redesign and new Filtering log
Now the filtering log not only сomplies with the principles of the responsive web design, its overall appearance has changed significantly. If you used the former filtering log, you'll be able to tell the difference: the new version presents searching in tabs, many new request statuses and filters that facilitate finding the needed requests. New filters and statuses are highlighted, and and tooltips explaining each one pop up when hovering a cursor over them. Apart from that, you can preview requests and format them in the same dialog — clicking the "Beautify" button makes it easier to read these requests.
The editor in the User rules section can now be opened in fullscreen mode, which makes working adding, editing, and deleting filter rules much more convenient. Finally, there is a new action on the AdGuard Browser Extension popup that allows to reset all the user rules for the currently opened website in one fell swoop.
Besides, now the AdGuard Browser Extension features dark theme that everybody loves so much.
Support for new modifiers after switching to TypeScript
"Still don't get what makes TSUrlFilter better than the previous filtering engine?" the most curious may ask. Probably, the main advantage is te new modifiers: $removeheader, $redirect-rule, $ping, $path, $noop, and $denyallow. And the $redirect modifier has been significantly improved, so now all the $redirect rules for a website can be cancelled by applying @@||example.org^$redirect.
Apart from the above-mentioned, Hebrew and Finnish localizations were added.
This version already has a hotfix for a rather severe bug of the initial v4.0 beta build. It blocked access to web pages misreporting them as phishing ones due to Safebrowsing bug:
- [Fixed] Extension v4.0 safebrowsing cache migration issue #1890.
How to install beta:
