limit the features built into the browser that can be used as a platform for tracking users’ habits, and, if it is not technically possible, disable them and leave it up to the user to choose whether to re-enable them
limit the close integration between the browser and its manufacturer
not let the excellent research work done by csagan5 with Bromite be lost
In addition, Cromite would like to promote greater integration with other non-profit, open source browsers, encouraging closer collaboration with others, and attempt to integrate them directly into Chromium once they have reached an appropriate level of maturity.
Be aware there’s no 32-bit support for Android and it’s kinda a beta. But it has support for Windows though.
I’m not sure where Bromite or a fork of it fits into the mobile android browser ecosystem. For other community maintained alternatives there’s FOSS Browser or Privacy Browser. For a good high security model, there’s TOR or Brave.
I’ve just become skeptical of those who aren’t using a webview wrapper due to the occasional tendency for projects to become unmaintained, which becomes a security liability. At least with something like Brave there is a clear monitization model which indicates longevity.
this is great i loved using bromite to separate my web app cookies and my default browser cookies. super happy that the project is coming back to life.
Bromite did create additional functionality for the mobile browser, more notably randomized timezone, quick permission toggles in the “lock icon menu” such as WebGL, JIT, javascript toggles etc. What vanilla Chromium needs on mobile is a permanent Incognito mode for ephemeral browsing, Bromite added that too. It was a unique browser with unique functionality but it fall back on updates.
