80

cross-posted from: https://lemmy.world/post/1766078

Bromite's actively maintained fork is going to have its own branding starting from next release according to the latest release notes:

Please note: this is the last release, the next one will be in https://github.com/uazo/cromite

top 12 comments
sorted by: hot top controversial new old
[-] Im28xwa@lemdro.id 4 points 1 year ago

I get an image of a scarecrow in my head whenever I say Cromite

[-] Cistello@reddthat.com 3 points 1 year ago

Brave is almost the same and Vanadium is better on Grapheme devices I don't recommend Bromite or even a fork It will probably have the same Update issues like Bromite which makes it a terrible option

[-] stonemilker@discuss.tchncs.de 3 points 1 year ago

He was the developer working on Bromite with csagan, and he was likely not the cause of the delays, since the builds on his repo have been keeping up with Chromium all year. I've been using it since Bromite stopped getting updates and it works really well. Brave was my second option because of the fingerprinting protection and adblocking, but they don't disable JavaScript JIT like Bromite and now Cromite. User script support is also really handy for me

[-] glacier@lemmy.blahaj.zone 2 points 1 year ago

I wish Bitwarden auto fill worked better with this browser.

[-] varaki@lemmy.world 4 points 1 year ago

Yes, apparently it has to be on some kind of builtin list of allowed browsers, otherwise it won't work. But sadly the PR is still stalling...

[-] privacyfalcon9899@lemmy.one 1 points 1 year ago

Still don’t understaand why devs prefer fork in instead of improving existing apps and duplicate efforts.

[-] bug@lemmy.one 24 points 1 year ago

Bromite hasn't been touched for 6 months, so this is the opposite of duplicating effort, it's an effort to save the project!

[-] privacyfalcon9899@lemmy.one 3 points 1 year ago

I was not aware of that. Thanks for the information.

[-] varaki@lemmy.world 10 points 1 year ago* (last edited 1 year ago)

It's exactly what you said: improving an existing app. For certain reasons, the original Bromite branding can't be used and since the original project's developer is basically left the project, this was the only way: forking and rebranding. The owner of this fork project was one of the main, most active contributors to Bromite anyway, so it should be fine. I wonder, though if there's going to be a Cromite WebView as well, because I still use the Bromite WebView... Does anybody know?

[-] lemann@lemmy.one 2 points 1 year ago

Something similar happened with youtube-dlc, allowing yt-dlp to be born

[-] Infiltrated_ad8271@kbin.social 3 points 1 year ago

At a quick glance, cromite apparently intends to be much stricter on security and privacy, over usability.

this post was submitted on 19 Jul 2023
80 points (100.0% liked)

Privacy Guides

16263 readers
42 users here now

In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.

This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.


You can subscribe to this community from any Kbin or Lemmy instance:

Learn more...


Check out our website at privacyguides.org before asking your questions here. We've tried answering the common questions and recommendations there!

Want to get involved? The website is open-source on GitHub, and your help would be appreciated!


This community is the "official" Privacy Guides community on Lemmy, which can be verified here. Other "Privacy Guides" communities on other Lemmy servers are not moderated by this team or associated with the website.


Moderation Rules:

  1. We prefer posting about open-source software whenever possible.
  2. This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
  3. No soliciting engagement: Don't ask for upvotes, follows, etc.
  4. Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
  5. Be civil, no violence, hate speech. Assume people here are posting in good faith.
  6. Don't repost topics which have already been covered here.
  7. News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
  8. Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
  9. No help vampires: This is not a tech support subreddit, don't abuse our community's willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
  10. No misinformation: Extraordinary claims must be matched with evidence.
  11. Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
  12. General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.

Additional Resources:

founded 1 year ago
MODERATORS