News for hackers. Stuff that matters.
Re:Adblock Plus for Safari released by applecore on Tuesday May 06, 2014 @08:52AM (#7704096)
Adblock Edge is a fork of Adblock Plus version 2.1.2, without the sponsored ads whitelist.
Re:Adblock Plus for Safari released by ihuman on Tuesday May 06, 2014 @09:10AM (#7704179)
Couldn't you just uncheck the sponsored ads whitelist?
Re:Adblock Plus for Safari released by r0h1n on Tuesday May 06, 2014 @09:26AM (#7704256)
AFAIK, the checks magically disappears each time the plugin updates. Given that their primary revenue channel must be Google, which pays them to whitelist their domains [0], such behaviour is to be expected.

It's why I switched permanently to Adblock Edge.

[0] http://www.theverge.com/2013/7/5/4496852/adblock-plus-eye-go...

EDIT: Downvoting doesn't change facts, although at times we wish it did.

(a) Acceptable ads always enabled after update - https://adblockplus.org/forum/viewtopic.php?t=17198

(b) Bug in Adblock Plus for Chrome and Opera caused acceptable ads setting to be reverted - https://adblockplus.org/blog/bug-in-adblock-plus-for-chrome-...

P.S. I've faced this issue numerous times on Firefox, so it wasn't just an issue on Chrome and Opera.

Re:Adblock Plus for Safari released by wallunit on Tuesday May 06, 2014 @10:40AM (#7704725)
This is not a fact. This is a conspiracy theory.

Indeed there was a bug on Chrome and Opera that re-enabled Acceptable Ads during an update. And of course it is tempting to believe that this was intended, given the controversy around Acceptable Ads. But believe it or not, every release of every software has bugs. And consider the complexity of the code initializing Adblock Plus, migrating old settings, setting up default filter lists and dealing with different storage APIs for almost every browser. Also a single setting being reset during update, is not a case you easily notice during testing. So it is no surprise that a bug like that made it into the release at some point.

Beside that there are several cases where browser profiles can be corrupted. That includes browser crashes, bugs in the browser itself, unreliable storage devices and a few other cases. You will realize that users of every extension that can be configured, occasionally report that their settings had been reset. Of course that don't bothers you if you use the default settings anyway. But also there is not much extension developers can do against that.

Re:Adblock Plus for Safari released by brymaster on Tuesday May 06, 2014 @01:03PM (#7705687)
The real point is that ABP originally pushed an update that enabled Google Ads by default.

That's not an ad blocker. The trust is gone.

In the future they can just push more updates with new "features" enabled by default that allows more kinds of ads from their whitelist.

Re:Adblock Plus for Safari released by r0h1n on Tuesday May 06, 2014 @11:36AM (#7705084)
There is no way I or you - as users - can either prove or disprove whether automatic unchecking of "allow acceptable ads" was a big or feature.

There's enough conversations on the web (and HN) on whether ABP "sold out" by white listing Google domains in return for cash. So when as a user you see a "bug" suspiciously and continously disregarding your choice of not wanting to see Google ads, the benefit of doubt ceases to rest with ABP. Especially when there are less compromised alternatives like Adblock Edge.

Re:Adblock Plus for Safari released by alayne on Tuesday May 06, 2014 @10:36AM (#7704694)
I've never had the whitelist checkbox revert its setting.
Re:Adblock Plus for Safari released by wallunit on Tuesday May 06, 2014 @09:23AM (#7704242)
Yes, you can in the options.

Adblock Edge just disabled Acceptable Ads by default and removed that option from the UI. Also considering that Adblock Edge is less maintained, it's not worth using it instead of Adblock Plus, if you ask me. You can just disable that option in Adblock Plus.

Re:Adblock Plus for Safari released by roeme on Tuesday May 06, 2014 @08:55AM (#7704106)
But Adblock Edge isn't available for Safari/Chrome though IIRC?
Re:Adblock Plus for Safari released by applecore on Tuesday May 06, 2014 @09:15AM (#7704203)
Extensions in Chrome and Safari are not as powerful as the ones in Firefox. There's no API in Chrome and Safari to prevent network requests, so extensions can't fully block ads like they do in Firefox. They're only capable of hiding ads on the page.
Re:Adblock Plus for Safari released by sirn on Tuesday May 06, 2014 @09:41AM (#7704343)
> They're only capable of hiding ads on the page.

This point is untrue, at least in Safari, there is beforeload event and canLoad[1] function for preventing content from being loaded at all, not just hiding it after it is loaded.

https://developer.apple.com/library/safari/documentation/Too...

Re:Adblock Plus for Safari released by wallunit on Tuesday May 06, 2014 @09:36AM (#7704314)
Chrome has a webRequest API [1], that lets you block any request initiated by your browser. Adblock Plus is using that API, and blocks everything that it blocks on Firefox also on Chrome.

But even on Safari Adblock Plus blocks requests loading images, frames, scripts and other resources, by cancelling the beforeload event. Though it is not possible to block XMLHttpRequests and requests initiated by third-party plugins like Flash.

[1] https://developer.chrome.com/extensions/webRequest

Re:Adblock Plus for Safari released by gorhill on Tuesday May 06, 2014 @09:39AM (#7704330)
> There's no API in Chrome and Safari to prevent network requests

Wrong (for Chromium-based browsers). I am genuinely curious about how you came to believe this. Trying to understand how come that myth is still so spread.

Here, the API:

https://developer.chrome.com/extensions/webRequest

Edit: To make it clear my comment is about chromium-based browsers.

Re:Adblock Plus for Safari released by _delirium on Tuesday May 06, 2014 @09:56AM (#7704435)
It used to be true (for years) that Chrome extensions couldn't block loading, so my guess is not everyone's realized that it's changed. Pre-2012, Chrome had no way to block a request, so you could write an ad-hiding extension, but not an extension that blocked web-bug/tracker loading. The webRequest API was added in 2012, so now extensions can do that.