Live data from Hacker News

Safari 14 added WebExtensions support, so where are the extensions?

sixcolors.com

21–30 of 224 posts

Re: Safari 14 added WebExtensions support, so where are the extensions?

#21
post #8

In addition to the money argument raised in another comment, the Apple development experience is a major annoyance when all you need is a couple lines of JS. I have an extension idea; it's literally a single line of JS. However, to get it into Safari, I need to create a (useless, and empty) Mac app with a specific configuration in Xcode that'll allow it to appear in the "extensions" list in Safari. Then I need to dea…

I agree with your point on a whole, I do want to add that tamper monkey does indeed work on Safari so you could just add that line of JS there

Thanks. I've been wanting to check it out but put it on the back burner. I'll revisit it at some point.

Re: Safari 14 added WebExtensions support, so where are the extensions?

#22
post #12
post #8

In addition to the money argument raised in another comment, the Apple development experience is a major annoyance when all you need is a couple lines of JS. I have an extension idea; it's literally a single line of JS. However, to get it into Safari, I need to create a (useless, and empty) Mac app with a specific configuration in Xcode that'll allow it to appear in the "extensions" list in Safari. Then I need to dea…

Do you know why the app did not appear in Safari’s preferences? And how did you fix it?

I don't fully remember, this was over a year ago. But the entire process put me off making Safari extensions for a long while.

Re: Safari 14 added WebExtensions support, so where are the extensions?

#23

I wonder if the bigger hurdle here is that you have to spend money to get into the developer program (unless this is waived for these kinds of apps, I couldn’t tell when trying to dig up an answer) I don’t know that effectively slapping an app shell around an extension is a big hurdle, but no other web extension store charges for entry, so that very well could be the real barrier here.

Yeah. The $99/year is big enough to pretty much block out all hobby devs and open-source projects, so what's left are generally commercial and closed-source. Apple says that they do their own vetting of extensions, but I don't trust Apple to prevent extensions from reading my browsing history, especially considering spyware extensions like Honey are served on the App Store without warning.

> especially considering spyware extensions like Honey are served on the App Store without warning.

You have to explicitly grant permissions as a user for safari extensions.

Re: Safari 14 added WebExtensions support, so where are the extensions?

#24
We finally ported Wappalyzer across to Safari. The process was fairly straight-forward but Safari doesn't implement every API that Chrome, Firefox and even Edge support, so we had to do a bunch of work to get a single version of the extension to work consistently in all four browsers. I'm glad it's finally here though.

https://apps.apple.com/app/wappalyzer/id1520333300

Re: Safari 14 added WebExtensions support, so where are the extensions?

#25
post #8

In addition to the money argument raised in another comment, the Apple development experience is a major annoyance when all you need is a couple lines of JS. I have an extension idea; it's literally a single line of JS. However, to get it into Safari, I need to create a (useless, and empty) Mac app with a specific configuration in Xcode that'll allow it to appear in the "extensions" list in Safari. Then I need to dea…

> I have an extension idea; it's literally a single line of JS.

That's better suited as a userscript.

Re: Safari 14 added WebExtensions support, so where are the extensions?

#26
I use Safari on the laptop because it's most efficient but it doesn't block all ads like ublock origin does. Particularly for YouTube so I need to use Firefox with ublock for viewing videos.

I tend to not trust extensions otherwise and would really prefer Safari to have built in total ad blocking - zero tolerance for any ads at all.

Re: Safari 14 added WebExtensions support, so where are the extensions?

#27
We are working on a new native macOS browser based on Webkit with native web extension API support built in.

We have uBlock origin and many others extensions working already. By doing this we get best of both worlds - performance and energy use of Webkit and extensions from chrome/firefox.

Screenshot: https://ibb.co/7V8sfyX

We are open for beta testers. Please email me if interested with short background and area of your interest.

Re: Safari 14 added WebExtensions support, so where are the extensions?

#28

We are working on a new native macOS browser based on Webkit with native web extension API support built in. We have uBlock origin and many others extensions working already. By doing this we get best of both worlds - performance and energy use of Webkit and extensions from chrome/firefox. Screenshot: https://ibb.co/7V8sfyX We are open for beta testers. Please email me if interested with short background and area of…

Interesting, is this planned to be an open source project?

Re: Safari 14 added WebExtensions support, so where are the extensions?

#29
So this is is a MAJOR flaw with WebExtension design.

Each uses a separate URI scheme.

So Chrome uses chrome-extension:

Firefox uses firefox-extension:

... etc.

which means web extensions for Firefox won't work with Google Firebase because they only support chrome-extension.

Why the heck isn't it web-extension: ???

Re: Safari 14 added WebExtensions support, so where are the extensions?

#30
The most popular web extensions are those that deprive sites of direct and indirect revenue, which necessarily means they can’t charge for the service or their userbase would revolt and steal their rule sets (which is easy to do for a web extension). Having to pay money for such things goes against the grain of those users, and the sort of breakage that people think is acceptable for content blockers isn’t quite as acceptable in the wider Safari userbase as it is for the pi-hole folks. Imagine pi-hole charging a monthly subscription or else it allows ads through, and you can see immediately why this category is dead on arrival in revenue terms.

And, for the content blocker extensions market, there’s essentially no point in releasing it as a paid web extension for iOS/macOS users, because there’s already better paid app competitors that do this, like 1Blocker or Guardian VPN or etc, that are full native apps on the platform with the appropriate hooks to be performant and such.

Therefore: What valuable browser extension ideas other than content blockers exist, that could have any significant user base and value, that isn’t already met by better and more capable native apps on macOS and iOS, and somehow could charge people money for the extension with their willing cooperation? They’d obviously have to use a subscription model, so factor that into consideration when assessing the market.

I’m unable to come up with anything that would make this segment of the App Store market worth my time to invest code into, and I already have a developer account for other reasons, so I don’t even have the annual fee barrier to consider. I remain hopeful that I’m wrong, but no one’s made a convincing argument yet. Prove me wrong, HN.

(I see most people taking the “wrap WebKit” route instead, which makes more sense since it provides the capabilities an extension can’t offer, and is dead simple by virtue of the platform’s capabilities. Makes more sense to me, anyways, and then too. So: now what?)

Post reply on HN