zlacker

>>dochtm+(OP)
"Hi, you seem to be browsing without being signed into Google with your government verified identity. Please do so to continue seeing the ads, I mean the internet"

>>HWR_14+L4
Chromium is open source. You're confusing Chromium with Chrome.

>>encryp+vq
It's like confusing "open-source" Android, AOSP and Play Services: https://arstechnica.com/gadgets/2018/07/googles-iron-grip-on...

>While Android is open, it's more of a "look but don't touch" kind of open. You're allowed to contribute to Android and allowed to use it for little hobbies, but in nearly every area, the deck is stacked against anyone trying to use Android without Google's blessing. The second you try to take Android and do something that Google doesn't approve of, it will bring the world crashing down upon you.

>>rcMgD2+zs
The difference is, AOSP on its own is unusable, but Chromium Is.

>>jacoop+Jt
Oh good, I look forward to the continued ad-blocking Manifest v2 provides after Chrome sunsets it.

And we still have to see if other browsers will block the Topics API spyware or not.

>>HWR_14+rW
Yeah, I'm looking forward to see what will happens when V2 dies. I'm using brave so this won't change anything for me really.

As for the Topics API, It looks like to be a new copy of FLOC, which flopped immediately on release, as no body adopted it other than chrome.

>>jacoop+DU1
Topics is rebranded FLOC. Everyone pushed back on it when FLOC came out, but that was publicly reviled and there was a simple toggle to turn it off (it was an experimental feature).

This is an excellent test of Google's ability to just push a very unpopular feature into Chromium derivatives.

>>HWR_14+Ea2
Non google browsers didn't only disable it, they removed it completely.

Google has a lot of control over chromium, but I don't think its even close to how gimped AOSP is compared to Android google edition.