Google did it again.
Step 1. Uninstall Chrome why are you still running it? Stop giving Google power over the internet. Just stop. Uninstall it. Use Firefox, Brave if you must. Just ditch Chrome.
Step 2. See above. Just flipping stop. No, don’t install another browser and keep chrome. Just DITCH CHROME. TOTALLY. If you need a backup use Edge or Brave or Firefox. STOP GIVING GOOGLE POWER OVER THE INTERNET.
I wouldn’t use Edge, if you’re on Lemmy, use Firefox. Cmon, if you’re technically literate you can figure it out. Everybody else, use Brave. It’s the least worse normie browser.
Just install another more privacy friendly browser
Firefox is the only answer here
I personally use librewolf. Firefox is making it look like they are private, but you need to tweak a lot of settings to get there
deleted by creator
I read this article from top to bottom and didn’t find a clear explanation of why you should disable this feature.
It’s an underhanded way of implementing a browser supported foolproof adblock detector. Even its stated goal of “give advertisers a unified, browser backed, ‘private’ way of tracking you for advertising” isn’t especially appealing or useful when you get something better than that from adblock anyway. Turning it off will be reflected in telemetry sites gather about feature availability and hopefully low adoption numbers discourage them from taking advantage of this “feature”.
Hmm, not having read up on the tech, what’s stopping someone from making a Firefox plugin that just spoofs fake data back? It’s all done client side if I’m understanding, so everything necessary to do so must be available. Only wrinkle I could see is if they have signing and ship the cert with Chrome and regularly rotate it. It’s still not impossible in that case, just more annoying.
My understanding is vague but the sandbox environment is cryptographically integrity checked in some fashion that makes the spoofing you’re suggesting difficult or impossible.
Well, I did a little digging, and while parts of the stuff proposed by Google might be tricky, the actual topics portion of the API looks pretty easy to spoof. It seems like there’s really only two things that need to be done. The first is to spoof the feature detection logic to return true for calls to
document.featurePolicy.allowsFeature('browsing-topics'). The second would be to return randomly selected topics from all available topics from calls todocument.browsingTopics()(care might need to be taken to return a consistent set of random topics to a given page, otherwise clever sites might poll the API many times to detect randomness). That really seems to be all there is to the topics API part of this. As for spoofing the rest of the web DRM parts, that’s going to be a lot trickier, but with control of the browser I can’t see how it could be made insurmountable.
Everyone here has probably seen Scott McCloud’s Contra Chrome web-comic. In the off chance you haven’t, it details exactly why you shouldn’t use Chrome.
Never seen it before. I’ll give it a better read when I’m not so busy in a bit (taking a shit right now ;)
Instead, text the boss: this is gonna be a looong shit.
I hadn’t seen it but am aware enough that it didn’t reach me a whole lot. But still.
Damn.
I haven’t seen it yet. Thanks for sharing.
Oh man! Time to give Google a damn good show of a
morbidly obese balding 40 something world of warcraft guy beating it heavily to lesbian futanari furry content staring into the camera as he gets busy!Google wanted this to happen, so why not give those suckers the VIP First Class treatment?
Anybody else think of things that’ll make those Google folk writhe in visual and audial agony and cut the privacy invasion act?
deleted by creator
