There was an EU-wide one that gota lot of its funding redirected to AI stuff recently that you might be thinking of.
There was an EU-wide one that gota lot of its funding redirected to AI stuff recently that you might be thinking of.
That’s more likely to be the tool assuming it’s running on a case-insensitive filesystem than it is Windows breaking anything. If you mount networked storage running on a case-sensitive machine, that’s something that’s worked fine in Windows for a very long time.
No, that is an entirely unrelated bad decision. It being okay to not have a popup to opt out of secure boot when it does its one job and notices you’re about to run insecure code in kernel mode doesn’t make every other user-hostile thing Microsoft ever does magically okay.
It’s upstream GRUB that’s decided the older GRUB versions are insecure and not to be trusted. Microsoft just propagated that to machines running distros that weren’t shipping patched GRUB builds yet. Up-to-date Debian wouldn’t be affected provided that they downstreamed fixes quickly.
https://fedia.io/m/linux@lemmy.ml/t/1111595/-/comment/6916699 says that Debian’s GRUB wasn’t affected, but another part of the boot sequence was.
You can’t trust users to make informed decisions about cybersecurity as most users don’t have the necessary background knowledge, so won’t think beyond this popup is annoying me and has a button to make it go away and I am smart and therefore immune to malware. Microsoft don’t want Windows to have the reputation for being infested with malware like it used to have, and users don’t want their bank details stolen. If something’s potentially going to be a bad idea, it’s better to only give the decision to people capable of making it an informed decision. That’s why we don’t let children opt into surgery or decide whether to have ice cream for dinner, and have their parents decide instead.
The comment you’re quoting was replying to someone suggesting a warning popup, and saying it would be a bad idea, rather than suggesting the secure boot UEFI option should be taken away. You need at least a little bit more awareness of the problem to know to toggle that setting.
But it does mean you can spend forty hours a week or thereabouts putting effort into a particular goal and maintaining the knowledge, skills and experience to keep doing it to a high standard without having to sink time and effort into something else in order to get paid enough to live on.
Those forks aren’t maintaining Firefox itself, just their own modifications. If a bug is found in Firefox, the LibreWolf team don’t have to fix it themselves, they can wait for Mozilla to do it, and incorporate the fix once it materialises. There are forks that diverge further, but they either get quickly abandoned after their creator realises how much of a headache maintenance will be, or they’re left with gaping security holes.
When the internet was becoming a world-changing technology, there weren’t thirty years of websites to keep working and malware to protect from, web standards were far simpler, and a much higher proportion of users were enthusiasts who were excited by anything they could get and didn’t mind if things were rough around the edges. Similarly, two brothers could make the world’s first aircraft that flew under its own power, and yet with the combined might of everyone working for Boeing, people are worried about airliner doors falling off and an eight-day space trip has become an eight-month one. Mature technologies need a lot more effort to build and maintain than emerging ones.
UX isn’t universal. What intuitively clicks for one person might be unusable for someone else. Good UX is adequate for as many people as possible, but it can’t be perfect for everyone at once when some people work best with large labelled buttons with big, clear icons that have to go into submenus to fit on the screen, and other people prefer lots of small buttons whose purpose and location they’ve memorised which all fit on screen at once to save them needing to click into submenus.
Maintaining a web browser in the 2020s is an expensive thing to do. You need full time employees who specialise in all the systems that make up a browser, and can’t leave security-critical parts like ensuring the integrity of the JavaScript sandbox to volunteer hobbyists. It’s far from the only thing Mozilla spend money on, so if they need to mage cost savings, it won’t necessarily stop them being able to maintain Firefox, but another organisation picking it up if they do stop isn’t likely.
If you’re doing things properly, you’ll know your Microsoft account password or have it in a password manager (and maybe have other account recovery options available like getting a password reset email etc.), and have a separate password for the PC you’re locked out of, which would be the thing you’d forgotten. If someone isn’t computer-literate, it’s totally plausible that they’d forget both passwords, have no password manager, and not have set up a recovery email address, and they’d lose all their data if they couldn’t get into their machine.
Is that enough to mitigate how much worse bare Google is than it was ten years ago, back when they were winning against SEO bots? In my experience, it hasn’t been, but I’ve not done enough AI-aided web searches to have a good sample size.
It wasn’t me who you replied to originally - I agree that it’s most likely AMD are just being super cautious given historically how many times bad news for their competitors has been falsely equated by the press as equivalent to a minor issue they’ve had, and the delay moving things after the microcode update and therefore making launch-day benchmarking more favourable is just a bonus.
You’ve misunderstood. The original release date was set, then Intel announced the microcode update, which was after the original release date, then AMD announced that they’d be delaying the release date, and that new release date is after the microcode update.
They’re not supposed to have trust. That’s why they’re only allowed fully anonymised data under this scheme. They do pay the bills, though, so they can’t be completely banished until there’s an alternative source of money.
OpenMW’s official Lemmy community has been on lemmy.ml since 2021, way before lemmy.world existed (and most other instances, too), and way before there was any inter-instance drama. It’s becoming increasingly likely that it’s not going to be a suitable long-term home, but we’d be much happier if we could migrate the existing community rather than start from scratch with a new one. Is there any way to do that yet?
If all they do is add more Creation Club content, all that happens is the functions people are hooking end up the same, but at different addresses. After the first few Creation Club updates, tools were made to automate mapping old addresses to new ones, and most script-extender-based mods could be made to work with just an Address Library update, which said which new addresses to use.
This is not that kind of update. The compiler version and settings used have changed, so functions, even ones that do the same thing, end up with different machine code at different addresses. This means a lot of mods will need making from scratch, and a lot of mods will need lots of work tracking down which functions need hooking now and how to do it even if there’s still stuff that’s salvageable.
There’s a pretty extensive API, capable of more than most games that advertise modding support, but it can’t do literally everything anyone could think of, so people reverse engineer the game engine to make it possible to do even more things (hence it being called a script extender rather than the modding API). It’s the mod reliant on reverse engineering the executable that break, not the ones using the modding API.
Fixing the script extender itself won’t take that long as it doesn’t need to hook that many functions (although depending on how much free time people have and whether there are any surprises, it could still take longer than most people expect). Fixing all the mods that depend on it will take much longer, as between them, they hook lots more functions than the script extender itself, and with this update, it’s not just a case of most functions being the same, but at a slightly different address (as was typical with creation club updates, which tools could help with), but instead lots of functions have changed slightly due to using an updated compiler, and lots of functions have been inlined differently (so instead of just existing once, they get copied into every function that uses them, and then optimised differently in each place based on the surrounding code).
It’s easy to get pressured into thinking it’s your responsibility. There’s also the risk that an unhappy company will make a non-copyleft clone of your project, pump resources into it until it’s what everyone uses by default, and then add proprietary extensions so no one uses the open-source version anymore, which, if you believe in the ideals of Free Software, is a bad thing.