f-droid is unsuitable for a browser. they regularly block security patches for many months and violate the android security model. anyone who cares about their privacy or security should not be using it
Sorry to sound like an ad, but I'd hate myself if I didn't take the opportunity to mention Accrescent, which is a big leap forward from an end-user security perspective vs F-Droid:
https://accrescent.app/
Of course, if Google succeeds in their mission to kill AOSP, kill unsigned APK installation (even for power users) and force all developers to submit photo ID, this is kind of moot.
The mobile FOSS community would benefit from accelerating transition away from Android to alternatives, even as incomplete and insecure as they are at the moment. The upstream maintainer of the OS itself is an entity that is hostile to the ownership rights end users have over their own devices, has been doing a ton of engineering work on "DRM" (to "manage" aka remove YOUR rights), has shown warning signs of abandoning the open source nature of AOSP itself, and has generally signaled extensive hostility towards their own end users, on an ongoing basis, across more or less all of their product lines. Alphabet/Google has been very clear about telegraphing how much they hate your freedom and how hard they're working to alleviate you from the burdensome weight of being able to decide what runs on your own hardware that you purchased.
I say this as a disappointed and worried GrapheneOS user. You can rip Google out of Android. Ripping AOSP out of Android is a much more complicated and much less realistic task, though. I'm not advocating for everyone moving their entire PROD workflow off of Android and onto a Linux smartphone today, but we shouldn't be burying our heads in the sand to the long-term risks that Alphabet itself poses to the availability, auditability, trustworthiness, and usefulness of AOSP.
The repository introduces it as indeed based on Helium [0].
The cool part about Helium is that it's based on patches, rather than forking the full source code. I don't know how sustainable this is in the long term, but it's an interesting approach for sure.
Standard practice for Chromium forks. Chromium's repo is huge, slow, and impossible to diff for your changes with 10000s of other commits. Also, painful to host it anywhere.
Not sure what's cool about that. A fork is a patch set, with a ton more ergonomics on top. Passing around sets of patches was what we did before VCSs were common/easy-to-set-up, and it was always brittle and annoying.
I tried installing uBlock Origin but the web store says I have to sign in and enable sync to download it. I didn't want to do that so I tried unpacking the extension .zip from GitHub and loading unpacked, but then the app just crashed.
Is extension support only meant to work with a Google account signed in or am I missing something?
EDIT: I tried loading the store page in desktop mode but I can't install the non-Lite uBlock Origin, I guess because this Chromium version doesn't support Manifest V2 anymore. I'm still on Kiwi Browser which supports MV2.
With Obtanium you can add the URL (https://github.com/jqssun/android-helium-browser) and it will automatically notify when a new version is available. Kind of like a package manager for GitHub and other sources (for stuff not available on F-Droid).
Quetta is unusable for me from how much they redesign the UI for no real reason. What I wanted was just an up-to-date version of Kiwi Browser which this project seems to aim for.
Great job on this release! I've been waiting for something like it since my favorite browser, Kiwi, stopped getting updates.
Without updates, many sites will likely stop working with it soon.
Kiwi had some great features, like disabling AMP mode, rearranging the Chrome Store for mobile, and customizable tab layouts, etc. These features might interest others as well.
I suspect these 'alternative' Chromium-based browsers are mostly aimed at those (like me) who want to keep their data out of Google's (et. al.) reach and as such would consider 'sync with the data parasites' as a misfeature.
The title of this thread actually says "with extensions support", so I think it is a major selling point intended for casual users like me, who priorities convenient over privacy.
> ...would consider 'sync with the data parasites' as a misfeature.
I am curious why Firefox isn't a choice for you. Why Mozilla as a NGO isn't trusted for handling your data?
What makes you think I do not use (something like) Firefox? I use Fennec - F-Droid's build of Firefox Nightly - as my main browser. I only use Chromium-derivative browsers for those sites which won't work with Gecko and to test whether things I make work 'on the other side´.
As to not trusting an NGO with my data, well... where to start? Ever since Mitchell Baker turned Mozilla into an activist cooperative while firing those pesky developers - who needs developers when all you want to do is political campaigning - and raising her own salary 5-fold that organisation has lost its shine as far as I'm concerned. As far as I'm concerned Mozilla is ripe for a new 'March 31 event' [1] in the sense of a transfer of the stewardship of the Gecko engine and Firefox browser to either another organisation entirely or to a splinter group from within Mozilla which still considers developing the main competitor to the Blink engine as its primary focus without any of the heavy political baggage from the Baker days.
That would raise the value of that project quite a lot (at least for me, but I feel like there are others, thinking similarly).
Please, push it to F-Droid!
Of course, if Google succeeds in their mission to kill AOSP, kill unsigned APK installation (even for power users) and force all developers to submit photo ID, this is kind of moot.
The mobile FOSS community would benefit from accelerating transition away from Android to alternatives, even as incomplete and insecure as they are at the moment. The upstream maintainer of the OS itself is an entity that is hostile to the ownership rights end users have over their own devices, has been doing a ton of engineering work on "DRM" (to "manage" aka remove YOUR rights), has shown warning signs of abandoning the open source nature of AOSP itself, and has generally signaled extensive hostility towards their own end users, on an ongoing basis, across more or less all of their product lines. Alphabet/Google has been very clear about telegraphing how much they hate your freedom and how hard they're working to alleviate you from the burdensome weight of being able to decide what runs on your own hardware that you purchased.
I say this as a disappointed and worried GrapheneOS user. You can rip Google out of Android. Ripping AOSP out of Android is a much more complicated and much less realistic task, though. I'm not advocating for everyone moving their entire PROD workflow off of Android and onto a Linux smartphone today, but we shouldn't be burying our heads in the sand to the long-term risks that Alphabet itself poses to the availability, auditability, trustworthiness, and usefulness of AOSP.
Combined Obtainium it's easy to keep it updated. https://github.com/ImranR98/Obtainium
[0]: https://news.ycombinator.com/item?id=45366867
[1]: https://helium.computer/
The cool part about Helium is that it's based on patches, rather than forking the full source code. I don't know how sustainable this is in the long term, but it's an interesting approach for sure.
[0]: https://helium.computer/
And yes, being 10s vs 10000s devs in the same repo isn't fun.
Have you thought about merging your efforts with ungoogled-chromium (Android)?
There USED to be an ungoogled-chromium for Android (circa v88 chrome, the APK is still available for download) that also allowed extentions.
Is extension support only meant to work with a Google account signed in or am I missing something?
EDIT: I tried loading the store page in desktop mode but I can't install the non-Lite uBlock Origin, I guess because this Chromium version doesn't support Manifest V2 anymore. I'm still on Kiwi Browser which supports MV2.
Edit: hard to find where to get this browser. Do I need to build it myself?
Without updates, many sites will likely stop working with it soon.
Kiwi had some great features, like disabling AMP mode, rearranging the Chrome Store for mobile, and customizable tab layouts, etc. These features might interest others as well.
Some Chromium builds has that: https://chromium.woolyss.com/#google-api-keys
> ...would consider 'sync with the data parasites' as a misfeature.
I am curious why Firefox isn't a choice for you. Why Mozilla as a NGO isn't trusted for handling your data?
As to not trusting an NGO with my data, well... where to start? Ever since Mitchell Baker turned Mozilla into an activist cooperative while firing those pesky developers - who needs developers when all you want to do is political campaigning - and raising her own salary 5-fold that organisation has lost its shine as far as I'm concerned. As far as I'm concerned Mozilla is ripe for a new 'March 31 event' [1] in the sense of a transfer of the stewardship of the Gecko engine and Firefox browser to either another organisation entirely or to a splinter group from within Mozilla which still considers developing the main competitor to the Blink engine as its primary focus without any of the heavy political baggage from the Baker days.
[1] https://www.cnet.com/tech/tech-industry/netscape-sets-source...
Kiwi was a great browser but has since shutdown. Android needs something like Kiwi that also has a steady income to support itself in future.