

- #Better ad blocker than adblock plus code#
- #Better ad blocker than adblock plus plus#
- #Better ad blocker than adblock plus download#
#Better ad blocker than adblock plus download#
Not sure about anybody else but I immediately felt the urge to download the source archives and check what changes have been implemented there.
#Better ad blocker than adblock plus code#
The source code archives are only left around to keep pretending that AdBlock is still an open source project, these are hard to find and the project owners are clearly hoping that nobody will be able to extract the individual changes from them. Users were neither informed about that decision nor the reasons behind it. To conclude: AdBlock covertly moved from an open development model towards hiding changes from its users. The discussion concludes with “AdBlock won’t have public Git repo in near future” without any explanation why the workflow suggested in some comments (separating public and private changes into different repositories) won’t work. From the discussion, it sounds like it is all about April Fools jokes and the like that shouldn’t become public before their time has come. All of the sudden, the support staff is talking about changes they want to keep private which is why they cannot make the repository public. Several other discussions brought up this topic, in particular this one from January 2014. It seems to have been marked as private however. I indeed found a reference to this repository so it must have been public at some point. AdBlock support staff promised that the situation was only temporarily and that a new source code repository would be created on GitHub soon. So you can still see the source code but extracting individual changes requires significant effort. The new project description points people to source code packages that they can download. However, that code repository was abandoned in August 2013.

They used Google Code hosting to make sure people can see their source code and contribute.

The AdBlock project started out as an open project. So next time somebody asks me about AdBlock and the difference to Adblock Plus, I can point them to this blog post.
#Better ad blocker than adblock plus plus#
There is certainly lots of room for improvement in Adblock Plus for Chrome, so my answer typically goes along the lines of: “These projects have different approaches but the resulting products are roughly comparable.” Recently, I looked over to the AdBlock for Chrome project and was shocked to discover that things changed, a lot actually. I am in charge of the latter, yet people will occasionally ask me whether I would recommend AdBlock or Adblock Plus to them. Despite the confusingly similar names, they are completely unrelated projects. On Chrome, two popular ad blockers are currently available: AdBlock and Adblock Plus. If you are here for Adblock Plus bashing and don’t care enough to read the post, please make sure to read the edit at the bottom nevertheless. It is likely unwise to rant about a competing project but I just don’t want to keep my findings to myself. This post represents my own opinion only. Note: This is explicitly posted in my private blog rather than the Adblock Plus blog.
