I’ve never seen the !0 and !1, it is dumb and indicates either young or terrible devs.

Boolean(window.chrome) is the best, !!window.chrome is good, no need to test if it’s equal to true if you make it a boolean beforehand.

Be careful and keep a backup, I’ve read so many stories of Apple deleting people music randomly.

While the code being open is good you still have to rely on trust.

I certainly don’t have the time to review to code of each extension I use. And even then, we have no garanties that the extension distributed through the browser stores has the same code.

You can see the issue was opened on august 18th but the responsible commit was only made on the 19th. So the code was pushed the extension users before it was made available on the repository. Open code is of no help here.

It just showed the developer is not to be trusted.

This seems sketchy : https://github.com/brookhong/Surfingkeys/issues/1796

I agree, there are a bunch of annoying limitations. But it’s better than nothing. To me the best vim based browser is qutebrowser, too bad it’s using chromium.

I don’t think it’s the same source code (uBOL vs uBO). And it’s definitely not the same logic, that’s the whole point, blocking with MV3 must be done in a declarative way.

They do kill uBlock Origin. The Lite version is a different extension.

Yes but that’s not the same. Because of Chrome limitation it can’t update it’s blocklist directly. You have to update the whole extension to update the blocklist and that goes through Google validation in the Chrome store. It adds delay and Google could even refuse some updates. The blocklist is also shorter because not all filter rules are supported.

How does it compare to tridactyl?

Ditch oh my zsh, install the plugins directly.

Because zsh is very fast and light. I’m using it with only a handful of plugins, manually installed, and starship