AdSweep serves a different purpose from ad blocking. It's not an ad blocker, it simply hides page elements using CSS selectors. Not really what I'm after, sadly.
On Sat, Dec 5, 2009 at 4:43 PM, John McCabe-Dansted <[email protected]>wrote: > On Sat, Dec 5, 2009 at 2:06 PM, Chen Yong <[email protected]> wrote: > > AFAIK ad-blocking is currently impossible in Chrome due to the lack of an > > API that prevents URL requests. Given how Google's revenue comes from > ads, I > > think it's pretty obvious why Google has refused to implement such an API > so > > far. What I'd like to know is: is there any point waiting for such a > > function to be implemented some time in the foreseeable future, or would > > this waiting be an act of futility? > > I know the chrome API doesn't support "noscript", but there is already > an adblocker of sorts: > http://www.mychromeaddons.com/chrome-addon-adsweep-a-chrome-ad-blocker/ > > Additionally, I understand that the Chrome devs do want noscript and > Flashgot to be supported: > http://forums.informaction.com/viewtopic.php?f=10&t=1676 > > If AdSweep is insufficient, the Chrome API is still being extended so > waiting for a more powerful adblocker does not seem futile. > > -- > John C. McCabe-Dansted > -- Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss
