What prevents uBlock Origin from coming back to the Mac App Store?

In Safari 14, Apple made it much easier to port extensions from Google Chrome to Safari.

I believe some improvements were even made in Safari 13. I would much rather use uBlock Origin compared to AdGuard. What’s preventing Raymond Gorhill from porting his extension to Safari now that it’s much easier compared to a few years ago? After all, Safari is generally much more popular than its competition.

I don’t have a direct answer to your question but I’ll offer a couple of observations:

  1. Just because it’s (supposedly) easier to port extensions to Safari doesn’t mean that the App Store will accept them, and

  2. It seems that the “improvements” that were made to enable Safari extensions has been met with a giant collective yawn from the development community. Dunno why.

uBlock Origin was on the Mac App Store before though. Doesn’t that mean it could easily make a return?

The real reason is documented here. Basically the WebExtensions API that Apple implemented in Safari 14 fails to support the functionality that is needed by uBlock Origin.

1 Like

What does AdGuard do different that allows it to remain on the Mac App Store?

Evidently it contains a work-around to the missing functionality or, for some reason, doesn’t require that functionality. Your guess is as good as mine.

If you want to prompt a developer to port or create an extension for Safari, perhaps ask the developer? Odds are the developer is not reading this forum looking for new customers.

1 Like

I am not asking for an answer from the developer. It isn’t like he’d even answer me in the first place.

Worth a try. I have had plenty of small developers answer my questions. Usually quickly as well.

1 Like

Agree with @Leeabe51. The best you can get here at this point is wild supposition from everyone. Go to the source.

The answer is as simple as Adguard not using the unsupported APIs and being willing to make the performance and utility tradeoffs required by the workarounds. @jec0047 's link has the latest official response from the developer, commenting on the APIs, and another statement from the developer on why he won’t be changing the plugin to accommodate (essentially, AdGuard is a business that can justify it, uBlock Origin is not.) He recommends Adguard for Safari users in the project’s Github readme.


Ah, okay. Thanks for clarifying!

I ask developers what their plans are, frequently. They don’t bite. I always get an answer or get pointed to where the answer lies.

1 Like