The Firefox source tree has every tool available for cross-compilation from Linux → macOS, which is how Firefox is built for macOS.

Clerk is surely one of the biggest and allows you to do this.

Saying that, I always like adding extras on top - and I've spent a lot of time making sure users can tweak how they like. I didn't manage to squeeze everything into this final release, but the .1 release will re-expose a lot of customisations that are buried in `about:config` preferences.

Comments URL: https://news.ycombinator.com/item?id=48995277

Points: 2

# Comments: 0

Currently still in Waterfox stable but figured there’s not actual much advantage to supporting Chrome extensions as Firefox ones are more featureful, so have removed it in the final version based on ESR 153 - albeit would be trivial to add support back in.

[1] https://github.com/bnpoirier/foxify

Well, there are other drop-in GHA runner services, so I wouldn’t see why anyone would be tied into a specific provider.

Namespace.so are one and my experience with their support has been incredibly positive. Great team there.

Honourable mention to WarpBuild as well, who I used before them.

Weirdly enough, the same time this was added to Geckko is when I started implementing the adblock-rs library for Waterfox - I stumbled across the bindings by accident when using searchfox on the main branch instead of esr140! Quite the coincidence doing it at the same time.

I've mentioned in another comment, that I've tried other ways such as with subscription paid services, but unfortunately there's nowhere near enough traction for it to be sustainable.

Also bare in mind Waterfox currently comes with nothing, so this is just an extra layer of protection.

The only real mitigation is being selective about which extensions you install and what permissions you grant them (even then, ownership of extensions change hands, updates can change what they do... it's a never ending battle really).

[1] https://www.waterfox.com/docs/policies/revenue-model/

This is basically the only potential way I can keep this going, even then there may not be much uptake, but it's a hail Mary.

The upside of Librewolf being a community project is also IMO its downside - there isn't any accountability and with the current climate around the world becoming more hostile to online services, I think governance is hugely important, which is why I've tried to collate everything as much as I can: https://www.waterfox.com/docs/policies/company-information/

At the end of the day, if something goes wrong, at least with Waterfox I can be held accountable.

System1 is a search syndication company. Their business is contextual ads on search results - no PII, no tracking profiles, no behavioural targeting. It's functionally the same model as DuckDuckGo. If I'd sold to DDG, I don't think anyone would've batted an eyelid.

I get it, the timing (privacy browser sold to company with "ad" in its description) looked terrible in a headline and I take responsibility for not communicating it better at the time, which I feel like wouldn't have led to such a massive furor.

Rather than support for XPI (which is just the packaging for Firefox webextensions), the current version of Waterfox does still support bootstrapped extensions - in theory anyone can still write one, with access to all the privileged JavaScript APIs typically not accessible to MV2/MV3 webextensions.

It's not widely used though, there are two repos I'm aware of that take advantage of this:

https://github.com/xiaoxiaoflood/firefox-scripts/tree/master...

https://github.com/onemen/TabMixPlus/

Comments URL: https://news.ycombinator.com/item?id=47545607

Points: 300

# Comments: 60