Adoption on desktop is 100% more related to Steam support, at least in the gaming segment.
Anecdotally, among friends and colleagues, people are only staying with Windows for gaming support.
People generally dislike Windows but are forced to stay their for gaming. As support for Linux improves, they'll be less willing to put up with Windows' BS.
That's pretty much what's been happening for the last decade. I turned off search history an age ago and I've had a slightly tailored (based on subscriptions) but mostly generic home page since them.
It's not a cas where they can't. They decide on this course of action.
On a related note, they already show an (almost) totally generic feed for Shorts. If you turn search history off, you see a lot of Andrew Tate, anti-trans, and "masculinity is under attack" messaging. It's disgusting to think that's what Google are showing to new sign users.
To be clear, the copyright strike is for a small two second animation in the middle of a much larger video.
The correct course of action here is for Mr Beast to apologize to the animation owner (AO) and to reupload the video with the animation removed. Or, to license the animation.
YouTube should then lift demonization.
AO didn't suffer any damage so there's no compensation owed. Legally, AO might be able to chase this but the payout will likely be far less than the court costs.
Mr Beast seems to be a pretty upstanding guy, so I wouldn't be surprised if he licensed the animation for a generous price.
Ultimately, it was the editor who messed up so the Mr Beast team need to review their processes.
Most videos like this make the majority of their money in the first few days. If they get demonetized, they're effectively dead. Considering the huge costs involved, that's pretty bad.
I'm not 100% sure the problem you're trying to solve, but I've solved a similar sounding one that may be of use to you too.
We needed to set env vars on React applications (the frontend) inside Docker containers. The containers were going to be built in CI/CD, and we didn't want different builds for each environment.
We solved this by adding a small JS script that is included in the base HTML. It pushes env vars into the window object, so they're accessible from window.env.
The JS file is generated by a Bash script that's ran whenever the container starts (by modifying the entry-point.sh file used by Nginx's Docker image).
The Bash script loads enumerates any environment variable with a given prefix.
Docker already allows you to set runtime environment variables from the run command, or via Docker Compose.
Im the end, the developer experience comes down to "docker run image:tag -e PREFIX_FOO=BAR".
Swiss companies have a history of telling the US gov to pound dust. There's a list of Swiss based registrars (that provide .ch domains) maintained by the .ch NIC: