←back to thread

64 points jqssun | 5 comments | | HN request time: 0s | source

Been working on an experimental Chromium-based browser that brings 2 major features to your phone/tablet:

1. desktop-style extensions: natively install any extensions (like uBO) from the chrome web store, just toggle "desktop site" in the menu first.

2. privacy/security hardening: applies the full patch sets from Vanadium (with Helium's currently wip).

Means you get both browsers' excellent privacy features, like Vanadium's webrtc IP policy option that protects your real IP by default, and security improvements such as JIT being disabled by default, all while being a reasonably efficient FOSS app that can be installed on any (modern) android.

It's still in beta, and as I note in the README, it's not a replacement for the full OS-level security model you'd get from running the GrapheneOS Vanadium combo. However, goal was to combine privacy of Vanadium with the power of desktop extensions and Helium features, and make it accessible to a wider audience. (Passkeys from Bitwarden Mobile should also work straight away once merged in the list of FIDO2 privileged browsers)

Build scripts are in the repo if you want to compile it yourself. You can find pre-built releases there too.

Would love any feedback/support!

1. sphars ◴[] No.45716304[source]
Ah thought I saw a Helium browser mentioned recently on HN[0] and thought this was the same thing. So this is not the same as this Helium browser [1]?

[0]: https://news.ycombinator.com/item?id=45366867

[1]: https://helium.computer/

replies(1): >>45716505 #
2. VPenkov ◴[] No.45716505[source]
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.

[0]: https://helium.computer/

replies(2): >>45716963 #>>45731192 #
3. kelnos ◴[] No.45716963[source]
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.
replies(1): >>45731177 #
4. akazantsev ◴[] No.45731177{3}[source]
Here is a homework for you to see why they do it:

  1. Checkout Chromium's codebase.  
  2. Make a commit and see how long it takes.  
  3. Try to push it to any git hosting service.  
You will discover what's actually brittle and annoying.

And yes, being 10s vs 10000s devs in the same repo isn't fun.

5. akazantsev ◴[] No.45731192[source]
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.