Google Chrome is downloading a 4 GB Gemini Nano model onto users' machines without consent, with no opt-in, no opt-out short of enterprise tooling, and an automatic re-download every time the user deletes it. The pattern is identical to the Anthropic Claude Desktop case I wrote about last month, but the scale is between two and three orders of magnitude larger. This article does the legal analysis and, for the first time, the environmental analysis. The numbers are not small.
I have to use Windows 11 at work. Whenever I complain about it to any of my friends, they say, “it’s easy to work around that. You just have to…” and then they say to modify some registry key, or set up a group policy, or run a powershell command, or use some cleaning tool.
But even if it’s easy to do that, it’s not easy.
You have to know about the key or the cleaning tool, and there’s a different one for every problem.
You have to keep up to date with the new user-hostile behavior introduced to Windows every month.
You have to keep up to date because Microsoft removes those circumventions, because they don’t want you to be able to remove their trash.
You have to vet the tools, make sure they’re not malware. And continuously make sure it’s not replaced by malware in the future. There’s no central repository of Windows programs like there is for Debian or Ubuntu, so if you just web search for the tool name every time, you might click on a malvertising link in the search results instead.
Naw, Linux is easy, until OBS won’t start virtual camera because V4L has dependency on the previous kernel which is pretty old.
if you did’t run it right after the update, you might not even put together it was a kernel issue.
No easy errors, start obs from cli see v4l errors out, start digging into v4l, it’s not hard, but you have to know about it, then you have to know grub well enough to select an old kernel.
Yup. I don’t think it’s hard. I used to have a dual boot setup. I’m just lazy.
And by that I mean, lazy enough that messing with regedits is something I’m already familiar/comfortable with and can do relatively quickly.
Too lazy to (re)learn an entirely new OS and file system (it’s also why I’m still on Win10 because fuck Win11), learn what programs of mine are compatible and not compatible, dealing with grub/kernals anytime I need to diagnose an issue, etc.
That being said, Windows will eventually piss me off to the final breaking point/straw where my anger/spite will outweigh my laziness. And THEN they’ll be sorry!
I’m in the overlap where I can easily follow reg edit direction and similar tutorials but can’t actually diagnose it myself. I wouldn’t have a clue. These known regedit edit workaround posts exist and are spread because there’s a ton of people in this overlap. We just aren’t vocal because it’s not one of our hills to die on.
But I can deal with cars, fix older models, and avoid buying an internet-connected model. Shit, I even learned how to fix drum brakes to maintain my options. I also disconnected my smart TV and grabbed a retired pc with win 10 pro or whatever to get some control back over that.
I do what I can, but at the end of the day, I still need to relax at some point.
Honest question, not necessarily for you but for maybe one of those people that actually understands the registry - how do those people figure that stuff out? Like, do software authors actually publish their registry config, or do people have to decompile/reverse engineer things to figure out what registry settings a given program might use?
keys tend to be organized (that’s a horrible word for whatt he registry is lol) in a handful of locations depending on context. so those chrome keys are next to the other chrome keys. in enterprise we mod that area pretty often.
the 2 was to discover a new key are:
reg watcher that takes a baseline, then you install soemething, and you see the diff.
in the case of no new key has been added (like for this new setting), most softwares have support articles aimed at Enterprise Admins who need to control deployments granularly. So the regkeys tend to be available.
Sometimes some dev figures it out, sometimes word spreads from the devs themselves on Discord/etc. Sometimes if you contact Support they have that workaround (after escalating to engineer). Not that you can easily get to Google Engineers, but you have a much better track with say a paid Workspace account.
It’s a FT job though to maintain a set of controlled software in an enterprise environment. Constant fiddling/tweaking. SOmetimes it’s a RegKey, sometimes a GPO setting, sometimes you’re modding a config file in AppData, or adding some lines to a Logon Script. And a lot of the info spreads by word of mouth still and to really answer your question - sometimes, no one knows where the hell it came from but after days of searching, you’re happy some random forum post finally worked and you hope to never have to touch it again. Then you close your ticket and move on to the next one.
“Linux is hard” but godawful reg key hacks are fiiiiine, eh.
didnt make the switch, but it feels like theres more and more shit to disable on fresh installs
I have to use Windows 11 at work. Whenever I complain about it to any of my friends, they say, “it’s easy to work around that. You just have to…” and then they say to modify some registry key, or set up a group policy, or run a powershell command, or use some cleaning tool.
But even if it’s easy to do that, it’s not easy.
Naw, Linux is easy, until OBS won’t start virtual camera because V4L has dependency on the previous kernel which is pretty old.
if you did’t run it right after the update, you might not even put together it was a kernel issue.
No easy errors, start obs from cli see v4l errors out, start digging into v4l, it’s not hard, but you have to know about it, then you have to know grub well enough to select an old kernel.
Yeah, that’s a relatively easy issue to debug. It goes to show that it’s really about where your familiarity level is.
I think the overlap between people who think using Linux is hard and the people who would open regedit in the first place is basically zero.
Yup. I don’t think it’s hard. I used to have a dual boot setup. I’m just lazy.
And by that I mean, lazy enough that messing with regedits is something I’m already familiar/comfortable with and can do relatively quickly.
Too lazy to (re)learn an entirely new OS and file system (it’s also why I’m still on Win10 because fuck Win11), learn what programs of mine are compatible and not compatible, dealing with grub/kernals anytime I need to diagnose an issue, etc.
That being said, Windows will eventually piss me off to the final breaking point/straw where my anger/spite will outweigh my laziness. And THEN they’ll be sorry!
But until then… Opens up regedit with a sigh
Tell that to my Windows desktop support coworkers, hah.
It’s really all about what you’re familiar with.
I’m in the overlap where I can easily follow reg edit direction and similar tutorials but can’t actually diagnose it myself. I wouldn’t have a clue. These known regedit edit workaround posts exist and are spread because there’s a ton of people in this overlap. We just aren’t vocal because it’s not one of our hills to die on.
But I can deal with cars, fix older models, and avoid buying an internet-connected model. Shit, I even learned how to fix drum brakes to maintain my options. I also disconnected my smart TV and grabbed a retired pc with win 10 pro or whatever to get some control back over that.
I do what I can, but at the end of the day, I still need to relax at some point.
Honest question, not necessarily for you but for maybe one of those people that actually understands the registry - how do those people figure that stuff out? Like, do software authors actually publish their registry config, or do people have to decompile/reverse engineer things to figure out what registry settings a given program might use?
keys tend to be organized (that’s a horrible word for whatt he registry is lol) in a handful of locations depending on context. so those chrome keys are next to the other chrome keys. in enterprise we mod that area pretty often.
the 2 was to discover a new key are:
Sometimes some dev figures it out, sometimes word spreads from the devs themselves on Discord/etc. Sometimes if you contact Support they have that workaround (after escalating to engineer). Not that you can easily get to Google Engineers, but you have a much better track with say a paid Workspace account.
It’s a FT job though to maintain a set of controlled software in an enterprise environment. Constant fiddling/tweaking. SOmetimes it’s a RegKey, sometimes a GPO setting, sometimes you’re modding a config file in AppData, or adding some lines to a Logon Script. And a lot of the info spreads by word of mouth still and to really answer your question - sometimes, no one knows where the hell it came from but after days of searching, you’re happy some random forum post finally worked and you hope to never have to touch it again. Then you close your ticket and move on to the next one.
I don’t miss it lol
There are tools that let you hook the registry and see what keys programs are trying to read from.
Ah ok cool, that was the sort of middle ground option I was missing