Never use Chrome, but there are some reasons to use a Chromium fork browser.
On privacy, just using Pale Moon gives them like 10 bits of signal to id you with on top of all the other things they can use. That's huge. Brave looks like any other Chromium except with fingerprint randomization for lots of things.
Also the more Chromium forks there are the harder it is for Google to make changes because they have to keep the forks from splitting off on their own.
For example with the new manifest to limit adblocking, if Brave/Edge/Vivaldi/Opera don't accept that change then Google's 75% market share drops to maybe 60% or something like that and those others are virtually identical except with better features so it's easy for people to switch.
Google has already delayed manifest v3 by 4 months so far for this reason. They say "intently monitoring comments from the developer community to help inform our timelines" and what that means is "finding some way to do it without losing the forks".
DNS blockers will become irrelevent when ads are served as first-parties on sites, which goes hand-in-hand with googles MV3 and Shadow/DOM push. As well as PWA's. Just a PSA ;)
Ads that run on decently-administered first-party sites are much less concerning than third-party ads from a security perspective.
Shadily run first-party ads running third-party code are, as always, a risk.
I don't much care if you want to load a picture and a hyperlink, but if you want to get any more complex than that, I am going to take issues with your site serving ads at all.
Adblocking is already a massive nuisance on Twitch and they are essentially serving their own ads, for me the only thing that works is a chrome extension in Brave, same extension fails to work in Chrome.
Never use Chrome, but there are some reasons to use a Chromium fork browser.
On privacy, just using Pale Moon gives them like 10 bits of signal to id you with on top of all the other things they can use. That's huge. Brave looks like any other Chromium except with fingerprint randomization for lots of things.
Also the more Chromium forks there are the harder it is for Google to make changes because they have to keep the forks from splitting off on their own.
For example with the new manifest to limit adblocking, if Brave/Edge/Vivaldi/Opera don't accept that change then Google's 75% market share drops to maybe 60% or something like that and those others are virtually identical except with better features so it's easy for people to switch.
Google has already delayed manifest v3 by 4 months so far for this reason. They say "intently monitoring comments from the developer community to help inform our timelines" and what that means is "finding some way to do it without losing the forks".
DNS blockers will become irrelevent when ads are served as first-parties on sites, which goes hand-in-hand with googles MV3 and Shadow/DOM push. As well as PWA's. Just a PSA ;)
Ads that run on decently-administered first-party sites are much less concerning than third-party ads from a security perspective.
Shadily run first-party ads running third-party code are, as always, a risk.
I don't much care if you want to load a picture and a hyperlink, but if you want to get any more complex than that, I am going to take issues with your site serving ads at all.
Adblocking is already a massive nuisance on Twitch and they are essentially serving their own ads, for me the only thing that works is a chrome extension in Brave, same extension fails to work in Chrome.