On some websites this integration glitched and the filtering was performed by the less powerful browser extension. There was a problem: they could hamper each other’s work. Basically, when AdGuard for Windows was installed along with AdGuard browser extension, the extension icon was taking the role of the Assistant. AdGuard for Windows is required for the proper functioning, of course, but technically the new Assistant can be installed without the app.Īnother reason to develop an alternative to the old Assistant was the so-called integration mode. Putting it simply, it is more autonomous and it doesn’t depend on the main AdGuard app. On the contrary, the new Browser Assistant is independent: it’s installed in a browser, and you don’t need to wait for the userscript to be injected into the filtered web page. Former AdGuard Assistant was a dependent userscript able to communicate with the main app using a certain protocol. The new Browser Assistant has the same functions, so what's the difference and why all this fuss in the first place?įirst of all, the name Browser Assistant suggests that it's a browser extension (which it is). A quick reminder for the new users: it hovered right on the web page, in the corner, and served to manage filtering without having to leave your browser. Wait a minute, wasn't there already an AdGuard Assistant? True, it was an extension (or a userscript, whichever term you prefer) incorporated into AdGuard for Windows app. However, there's one new feature that takes all the attention and saves the day. Many of you might ask, what took us so long? Unfortunately, a lot of changes were made under the hood, so frankly it won't be that easy for us to explain, or that interesting for an average user to read about. It took us almost half a year to come up with a new AdGuard for Windows release.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |