zlacker

[parent] [thread] 4 comments
1. HWR_14+(OP)[view] [source] 2022-06-22 15:19:20
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.

replies(1): >>jacoop+cY
2. jacoop+cY[view] [source] 2022-06-22 19:44:14
>>HWR_14+(OP)
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.

replies(1): >>HWR_14+de1
◧◩
3. HWR_14+de1[view] [source] [discussion] 2022-06-22 21:10:53
>>jacoop+cY
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.

replies(1): >>jacoop+tj1
◧◩◪
4. jacoop+tj1[view] [source] [discussion] 2022-06-22 21:43:02
>>HWR_14+de1
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.

replies(1): >>HWR_14+6U1
◧◩◪◨
5. HWR_14+6U1[view] [source] [discussion] 2022-06-23 02:27:24
>>jacoop+tj1
> Non google browsers didn't only disable it, they removed it completely.

They set the toggle to false and deactivated any of the options to turn it back on. That's very different from removing a feature (or maintaining a legacy feature).

The only code they changed was UX-related and a single default.

[go to top]