JFYI, it jumped out again. What is difference between this download link https://chrome.google.com/webstore/detail/adguard-adblocker/gfggjaccafhcbfogfkogggoepomehbjl and this http://chrome.adtidy.org/app.html?app=main.crx I ask because the first shows v2.0.7 and the second, I have installed from, shows v2.0.6? Which one do you recommend to use to keep up with the latest betas?
Thanks, I'll start reading rss again and will try to block it. It's just takes time to publish new beta to the Chrome WebStore. Btw, changelog for the latest betas:
No, it is right opposite. On the Chrome Store there is 2.0.7 and on the second link there is 2.0.6. Download from the both links and you will see. Installed from the Chrome store and now I'm having the latest beta 2.0.7.
Ops, my bad then. Also crx file is almost unusable in the latest Chrome versions (they disable all extensions not from Chrome store).
When a malware is detected, GOBACK does not work, ADVANCED does work. No other extensions on Chrome 42.0.2311.90.m Disable only third party software MBAE free, result is the same. De-installed MBAE and issue remains.
With Chrome, Yandex and Wot in the malware protection section, AdGuard also get Sophos URL filtering (Yandex) and Phistank (Wot) plus some other community IP-blocklists feeding their results into Wot. So in terms of URL protection, you could well have the broadest base. Thanks for confirming
Today's update of Opera (v29) makes Adguard again slower to start. In my case it is observed that all favicons on the bookmarks toolbar aren't filtered. Up to version 28 they were all blocked.
Heh, @pegas, you are doing everything to make me give you a special build which only additional feature will be blocking favicons We'll soon release a patch for AG extension slightly changing the initialization, it may help.
@avatar RE: Goback hangs after malware warning issue Goback now returns to about:blank ==> hang is solved (webpage becoming unresponsive after clickig goback) ==> goback does not returns to previous webpage, but redirects to about:blank
Are you sure? Maybe cache? Initialization speed was improved significantly, from 400ms to 100ms. Heh, that's really more "stable" way to hide favs
That's possible if the page is opened in a new tab. What do you think is the right behavior in this case?
Confirmed, it opened in a new tab. My preference is: A. website --> B. user clicks to open bad link in new tab --> C. block link --> goback to website A on which initial bad link was clicked. Regards Kees
Hello. Perhaps this is mere open wishful thinking but script blocking functionality would perhaps be the proverbial icing on the cake...Just wondered if avatar has any ideas on this.
@Windows_Security, got it, thank you! We'll do it if it's possible. Do you mean NoScript functionality?