Somewhere around 0.3 to 0.4 Mooches.
placatedmayhem
joined 4 years ago
You're not the only one I've seen. It's pretty entertaining that Google's decision to neuter adblock plugins in Chrome then deploying anti-adblock measures on Youtube is pushing folks off Chrome.
Welcome back to Firefox. :)
Twitter already broke their internet search results just a couple of months ago:
https://www.theverge.com/2023/7/3/23783153/google-twitter-tweets-changes-rate-limits
That's believed to be why they reversed on the "must log in to read" and rate limiting policies.
This is the backdoor that's deployed after a host is compromised. How the host is compromised is somewhat irrelevant. It could be exploited manually, social engineering, a worm, etc.
Yes, weird corner cases in musl cause a lot of things to misbehave when run on musl. For example, DNS upgrade to TCP, which is required for certain queries and covered by one of the DNS RFCs, wasn't implemented in musl for the longest time, although I think it finally got implemented recently. However, there are other cases like this fwiu.
No. There are a whole bag of tactics to get you to enable it like "Whoops, got re-enabled in an update. Our bad.", which has happened before, or a myriad of dark patterns. By changing the name of this at least twice now when it got backlash from users, Google has shown it doesn't care about Chrome users' preferences, only that it wants this to fly under the radar so that every Chrome user won't know to disable it.
Change to a browser that actually gives a crap about your privacy. As a bonus, changing helps reduce Google's ability to dictate what happens to the web via Chrome's huge user base, like the recent "Web Environment Integrity" push.
Fewer than originally expected. Apple cut the initial production order[1]. Also, "selling out" is a hype generator now.
[1] https://www.reuters.com/technology/apple-forced-make-cuts-vision-pro-production-plans-ft-2023-07-03/