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:
- We prefer posting about open-source software whenever possible.
- 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.
- No soliciting engagement: Don’t ask for upvotes, follows, etc.
- Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
- Be civil, no violence, hate speech. Assume people here are posting in good faith.
- Don’t repost topics which have already been covered here.
- 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.
- Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
- 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.
- No misinformation: Extraordinary claims must be matched with evidence.
- 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.
- 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:
- 1 user online
- 1 user / day
- 6 users / week
- 70 users / month
- 649 users / 6 months
- 1 subscriber
- 665 Posts
- 11.1K Comments
- Modlog
So Chromium?
Just use Firefox, its the better browser anyways.
deleted by creator
I already use Firefox but brave is just better at fingerprinting protection
There’s CanvasBlocker for Firefox that can do fingerprint protection.
Adding add-on makes you more fingerprintable, not less.
It depends. Many addons have effects that can be tested for and fingerprinted, but it’s not always straight forward. There’s a way to detect any specific chrome extension, but doesn’t work on firefox because it uses unique extension ids per person.
With addons like CanvasBlocker, they generate random values for a bunch of apis like canvas. So each time you will look unique, but it changes every time so you’re not easily tracked. I’d assume it’s similar to what Brave does, but I haven’t looked into the details. Some stuff isn’t randomized by default, so they can get info like timezone and languages, but probably not enough to give you a unique identity.
Arkenfox is also good at protection from naive fingerprinting
Aye Firefox gang 🦊🤘
Almost all of my Linux devices have both chromium-browser and Firefox installed. Firefox is my default, but there are some apps out there that work a lot better in something chromium-based.
Ungoogled-chromium is a good substitute in that case
Haven’t used Ungoogled Chromium in a couple years, but I’ve seen some criticisms of it even compared to regular Chrome: https://qua3k.github.io/ungoogled/
No one is going to develop exploits only for a browser with certain default security options disabled (especially these made at compile time using toolchain). Binary exploitation is hard, and extremely not worth the effort in this case.
Disabling CRLSets though is worrisome, and its binaries are built by potentially unknown third parties with compromised systems.
Thank you for sharing this, I was unaware. I wonder if any of this has been addressed recently as the linked article is two years old (not demeaning its value, just wondering if the devs saw the article and decided to improve ungoogled-chromium).
They still disable CRLSets and have binaries built by “contributors” not in an automated fashion by the developer themselves.
Yeah, that’s why I pointed out that I haven’t used it in a couple years, I have no idea about the direction development took after that, so maybe some folks that work on the development of Chromium and its many forks can give us some insight. Personally, I just decided to stick to Firefox tweaked with Arkenfox as my main browser on desktop and I have Brave with all its annoyances turned off as a backup option
Brave might have started as a basic Chromium fork, but the various privacy/security features they added do make them standout now.
But they still contribute to google’s monopoly over web standards.
It is really disingenuous to say “X is just a skin of Y” just because they share the same browser engine or are forked from the same browser. Like you say, there are a lot of changes.