12

I agree with those who would prefer an addon from avast! that didn’t require us to maintain a cookie for the addon inside the browser itself. I mean, this isn’t a site that we’re trying to retain settings for - it’s just an addon/extension for the bowser, which is installed by software that already has full access in the operating system. Why should I have to turn off Private Browsing Mode or use a 3rd party cookie managing addon/extension to retain this one cookie, when the application could easily retain the information using the numerous other storage options that exist with its level of access. It could have the settings for the browser-specific addons in the existing avast! UI (which already has the page for enabling the per-browser extensions), or it could keep the settings in the Add-ons Manager tab which has been part of Firefox for… years?

Seriously, all the comments about cookie management are missing the point for the simple fact that the avast! developers are not some silly know-nothing kids who don’t know any better. They’re experienced developers who are fighting the black-hat world in exchange for a little profit. That being said, they don’t need us to make excuses for them and work-arounds in a situation like this (talking about the usage of browser cookies to store persistent data - what is this, the 90’s?). Say it plainly. “I’d like an addon that doesn’t make me give up my existing and beloved settings”. From there, they’ll either indulge you or they won’t. But let’s not pretend that there are no other options on their end.