Just wait until corporate finds out what the Dutch Krampus looks like 🙈
I wouldn't worry about it too much; there's not really anything you need to do as a user anyway.
Well, then I'd highly suggest you just use Xfce and not worry about GNOME so much. Xfce hasn't changed much in years.
"The browser chrome" is the name historically given to the parts of the browser that are not the website. Then Google created a web browser and decided to name it after it - but userChrome.css
existed before the browser Chrome did :)
It doesn't matter if they do, as long as voters believe they do.
Allright allright, you win :)
I mean, you're just saying that if you don't dial it up to eleven, but just to nine, then you'll hit less breakage. Which, sure, but that's kinda my point: a usable browser needs to strike a balance, and that's exactly what Firefox is trying to do - which is really something different from "needing a 180-degree turn". Firefox by default is stopping way more tracking than e.g. Chrome, and guides users to installing e.g. uBO.
Also note that most breakage isn't immediately obvious. For example, if you turn on privacy.resistFingerprinting
, then Google Docs will become blurred. However, by the time you see that, you won't be able to link that to the flipped config. This is the kind of breakage that many "hardening guides" cause, and by that, they eventually lead people to switch to Chrome, which is the opposite of what they're supposed to achieve.
And sure, Librewolf draws the line at a slightly different place than Firefox does. But the main difference is not sending data like hardware capabilities, crash stats, etc. to Mozilla - which don't threaten democracy or result in hyper-targeted ads, but do enable Mozilla to optimise the code for real-world use.
Could you also replace the screen, camera's, USB port, loudspeaker and earpiece with nothing but a screwdriver?
Copying my reply to this same point from elsewhere:
Those phones were presumably glued together and not as repairable as the Fairphone is. Which is very useful, but does lower your waterproof rating, hence the need to compensate elsewhere.
I really feel like people are too quick to assume malice, generally. Often, there are just trade-offs with no clearly-right answer, and it's not obvious to folks like us on the outside what those trade-offs are.
Yes, but "exploratory work" is far from a finished, proper product. Which is to say, expecting it to be available next year would be optimistic, especially since the new rules haven't even been set in stone yet, and that enforcement typically takes time :)
Keep in mind that switching out the engine under your app is probably no easy task, nor is making it well on a new platform in the first place.
I think it's just because some things have country-specific formats. For example, if you want to prefill credit card details, you have to figure out how the credit card fields are labelled.