Fork of Mulch Browser?

DeletedUser60

I was wondering if someone know of Forks for Mulch Browser? Because I only know of IronFox which is a Mull Fork...

DeletedUser67

DeletedUser60 I asked the Maintainer of IronFox if he can maintain Mulch too and he told me that he has a lot to do but he will ask some of his Developer Friends if they could maintain Mulch. Let's wait and see. He will tell me if they will take it up.

AlphaElwedritsch

Not yet

GrapheneOS

We already have Vanadium, which is where Mulch was getting the patches from in the first place.

DeletedUser67

GrapheneOS I think that he was asking for Users outside of GrapheneOS.

MentalM

GrapheneOS I see now that IronFox is available in the Accrescent app list. What would be the use case to choose that over, or next to Vanadium on a GOS device? As I understand it, the mozilla project FireFox (and likely the forks then as well...?) have a larger attack surface: is this then reduced by IronFox?

Xtreix

DeletedUser67 We don't know unless OP makes it clear. However, I also don't see the point of using it on GOS when we already have Vanadium unless you just want to compare them. It should be noted that Vanadium will probably be available outside GrapheneOS., but it won't benefit from a full hardening, so it won't be exactly the same.

SovereignCopper

MentalM

Here are some:

Block known fingerprinting and ads via uBlock Origin (plus all the other perks of it)
(Try to) prevent fingerprintability done by unknown/unblocked entities via further mitigations
Proxied use of Google's safebrowsing
Removes or disables telemetry, experiments and other Mozilla stuff not needed for browsing

As for as continuation of Mulch, FWIW the developer of AXP.OS (a continuation of DivestOS) has put the releases of their browser based on Mulch here: https://codeberg.org/AXP-OS_releases/app_aosmium/releases

GrapheneOS

MentalM Firefox-based browsers have drastically weaker protection against exploitation than Chromium, especially on Android where they don't implement sandboxing yet. There's an even bigger gap when comparing to Vanadium.

Dumdum

MentalM What would be the use case to choose that over, or next to Vanadium on a GOS device?

Pretty much just extensions/better adblocking I think. Vanadium (and Chromium in general) doesn't allow extensions on Android, and adblocking is currently much more basic in Vanadium than something like uBO.

GrapheneOS

SovereignCopper Using a very niche browser makes fingerprinting easier, not harder.

As for as continuation of Mulch, FWIW the developer of AXP.OS (a continuation of DivestOS)

It was based on forking the DivestOS code but it's not really a continuation of it. It doesn't follow the same approach.

SovereignCopper

GrapheneOS Which is why Vanadium would also benefit from wider availability. This would also eliminate the need for Mulch-like initiatives.

GrapheneOS It was based on forking the DivestOS code but it's not really a continuation of it. It doesn't follow the same approach.

Their SLIM variants do to a large extent.

GrapheneOS Step in the right direction: IronFox has enabled fission by default.

TheGodfather

SovereignCopper Step in the right direction: IronFox has enabled fission by default.

It nevertheless does not use isolatedProcess, so it won't really matter.

GrapheneOS

SovereignCopper

Their SLIM variants do to a large extent.

Not really, and we already posted about our thoughts on whether it would make sense to continue DivestOS as is:

https://grapheneos.social/@GrapheneOS/113772409415058393

ceramics

SovereignCopper Which is why Vanadium would also benefit from wider availability. This would also eliminate the need for Mulch-like initiatives.

I'd invest greatly in Vanadium. Make it as close as possible to solving many browser issues, make it available in play store (if there's no compromise), increasing user base, market it like a gateway drug to GrapheneOS.

missing-root

ceramics the GrapheneOS camera already kinda is