Heck, I'd love it if they added a toggle to not hard-pan all audio to the left channel and drop all input from my microphone until I restart Teams and log in again despite having logged in ten minutes ago.
Reformatting isn't going to change how your SSD is electrically connected to your mainboard. Do you actually mean NTFS?
I suppose a distro might ship without NTFS-3g or the ability to install it, although Bazzite should be able to at least read NTFS.
Not a hardware issue; Linux handles NVMe and SATA drives just fine. They probably encrypted everything with BitLocker. Of course Linux can't access an SSD encrypted using a proprietary Microsoft software with keys that may no longer be accessible.
I mean, if they got fined something like 100 days' revenues¹ they'd change their tune right quick. European law allows for that kind of fine.
¹ One day's revenues being calculated as the total revenues in their last fiscal year divided by 365.
Oh, I love "other apps". My Teams once decided that obscure features like chats and calls belong in there.
Yes, Teams. Put your core functionality out of sight. That's exactly what I wanted.
And that's how you become a complacent enby.
I kinda like my body but feel that I would've liked it more with different chromosomes but also that I'd like it less if I went for surgery. So what I've got is pretty much as good as it's gonna get. Except for hair removal but I actually tried that and my follicles are built like tanks.
As fun as having a fem voice to switch to sounds, voice training takes a lot of discipline and I certainly don't have the drive to see it through. Mad props to those who do.
E-bikes are allowed to go faster than 25 km/h, it's just that the motor has to stop helping beyond that speed. Important difference.
I don't think that a general 20 km/h speed limit is the best choice. Maybe add tiers based on the type of path. Bike lanes on roads and bike paths without immediately adjacent foot paths could go pretty fast, bike paths separated from foot paths only by a line on the ground a bit slower, and shared foot/bike paths even slower. Maybe something like 30/20/15 km/h.
Before someone comments "but bike lanes on roads are also immediately adjacent to foot paths": Yes, but so are roads without bike paths and cars are allowed 30 or even 50 km/h on those. It's generally understood that roads are dangerous and need special consideration so I'd be willing to allow 30 km/h on bike lanes.
It can absolutely be both rushed and way late. You just have to move very slowly (or inefficiently) for a long time and then try to get what you have release-ready in a hurry.
I think that guy now has a fairly successful career in politics, which is one hell of an upgrade from being homeless. Maybe his turtle duck luck came in a bit late.
The term "irrational exuberance" comes to mind.
I read about this a while ago and people then concluded that FROST is harder to exploit in real-world scenarios than in the lab. Still worth addressing and a fix shouldn't be too difficult, e.g. by adding small amounts of random latency to OPFS accesses. Firefox already does this with other APIs to make fingerprinting harder. Chromium doesn't because they love fingerprinting.
Honestly, I'm not thrilled with the OPFS model in general. Each page can randomly occupy part of your storage with you having no control over the process. You don't get asked. You can't even inspect the data. Even if it turns out to be useless for fingerprinting, the ability to use your storage invisibly with zero effort is not a power I want to hand out like candy in an environment that supposedly is assumed to be adversarial by default.
The only upside is that browsers do have a quota which is apparently shared between all instances of IndexedDB and OPFS. So the threat model of "use OPFS to fill up the user's entire storage" isn't plausible per se even if you have multiple tabs to attack with. Filling up the storage to evict other sites' stored data might actually work, though, and while it sounds like more of an annoyance, it might also become a step in some other attack.
Besides, quota size is entirely up to the browser; while Firefox uses 10% of total storage or 10 GB, whichever is lower, Chromium can in principle take up to 60% of total storage. When I tried, both a Firefox-based browser and a Chromium-based one had quotas of exactly 10 GB; I suspect that my distro's packagers configured the latter when the built the browser package.
Expected, though. The EC is not exactly known for having sensible opinions.