For those of us that use AdSweep I (and anyone else who subscribes) have received the following today from Charles ...

Hello,

Due to lack of time, lack of technical support, and despite repeated requests with no feedback, I sadly had to discontinue the AdSweep project. You can still download it and tweak the source code to your needs if you know how to do so. I will no longer remove ads on demand. Thanks to those who have helped me.

Charles.

Have we got anyone who can take up the gauntlet ?

Sucks he left before he could implement a UI, and allowing the user to add websites to whitelist and stuff (which is in there, but not active for Chrome, at least).
It's not too hard to edit though it seems.
All the ad data starts at line 51 with the whitelist setting.
I don't really know what the difference between the whitelist and the adPatternExceptions is. :S I think it's just that adPatternExceptions can have custom ad string removals and whitelist sites can't.

Anyways:
ALL of these are comma separated lists unless otherwise noted.
*whitelist and adPatternExceptions are just urls, no special syntax.
*sites, css_exceptions, and common_ad_patterns are CSS Rules without the style (which is what's in the {}), slightly explained here
*sites_custom_css is CSS Rules with the style.
*scriptSrcMatch, scriptTxtMatch are RegEx patterns that aren't actually separated, they use the RegEx operator "or" | However these only seem to be active for Opera.
* scriptSrcMatchExceptions and scriptTxtMatchExceptions are RegEx patterns that are ", " (that's comma followed by a space) separated. However these only seem to be active for Opera.

That's all you really need to know to add your own.

What are people who don't know anything about CSS going to do? How are we going to get an updated adblocking utility, now that AdSweep is no more? Are there any other adblocking userscripts or extensions for Chrome out there?

Before AdSweep I used a thing called Privoxy which set your Internet Proxy settings ...

The good thing about it was that it was system wide so applied to all your browsers ...

The bad thing (as far as I was concerned) was that all though it blocked the ad it left a placeholder on the page (normally a big white space) ...

Hopefully one of our more technically aware contributors can take up the challenge ...

I don't think it would need to be updated as often as Charles did ...

Because of the success of AdSweep I guess a less frequent update would be totally acceptable to people here, as long as they had something to replace it ...

Comments Gents please :-D

Less frequent updates are fine with me, as long as AdSweep gets updated at all, and someone can keep updating the extension itself. I don't want to install Privoxy, and I hate that white space issue, which is why I'll be sticking to the current version of AdSweep for now.

I think that's the best bet and start worrying when Ads start appearing again ...

Well I don't really want to take up the entire thing alone was really what I was getting at.
The more technically aware users can make additions as needed when they can and post the edits for everyone else.
I think it's kind of a public extension now.

Although I'm not sure how that will fit in with the new signing requirements on extensions.

What exactly is this signing thingy ?

Originally Posted by devilslackey

Although I'm not sure how that will fit in with the new signing requirements on extensions.

We can always post the .pem file for people to use.

@StevePaul; it's some odd sense of a security measure, giving each extension a public key that's generate from a random private key stores in a .pem file, that's made when you pack it. This verifies that the update is actually from the author, rather than someone trying to impose as the author who's actually releasing some malicious code or something.