AnyOldName3

It’s been the default since 2015 when Windows 10 launched, although there was an obvious button to opt out during first-time setup back then which was then respected permanently. It’s got gradually less prominent over time, and maybe the article’s just doing a really bad job of explaining that it’s no longer something where your initial preference is permanent and it’ll change back to the default every so often.

It’s a silly flag to use as it only works when running 32-bit Windows applications on 64-bit Windows, and if you’re compiling from source, you should also have the option to just build a 64-bit binary in the first place. It made a degree of sense years ago when people actually used 32-bit Windows sometimes (which was usually just down to OEMs installing the wrong version on prebuilt PCs could have supported 64-bit) if you really wanted to only have one binary or you consumed a precompiled third party library and had to match its architecture.

That’s what I remember, so I’m not convinced the other commenter posted correct numbers.

No, that’s the cyborgs.

They tried. UWP and the Windows Store did loads to boost security and make the source of apps verifiable, but people hated it and barely used it, so the holes they were supposed to patch stayed open. The store itself did have the problem that part of its raison d’être was to try and take a cut of the sales of all software for Windows, like Apple do for iOS, and UWP made certain things a pain or impossible (sometimes because they were inherently insecure), but UWP wasn’t tied to the store and did improve even though it’s barely used.

They update on two Tuesdays a month, and have done that at least since XP. Even with the most reboot-keen settings, the update doesn’t happen until the time of day you’re least likely to be using the machine based on when you typically do it. It tells you when that time will be and gives you several hours of notice with a popup with the option to delay. Depending on the variant of Windows you’re using, you have settings to delay a forced reboot for up to a week (Home), a month (Pro) or forever (Enterprise). Obviously, that’s not enough to make sure no one ever gets updates forced on them when they don’t want them, and it would be nice if there was a way to distinguish users who know what they’re doing from users who don’t so people who do could be given more power to control if and when they install updates, but it is enough to ensure that checking the equipment before you use it is enough, potentially two weeks in advance.

!openmw@lemmy.ml has less than 150 subscribers, so it’s definitely not large. We’re already swamped with infrastructure work for the stuff we already self-host, so I don’t think we’ll be running our own Lemmy instance any time soon.

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?

Instead of a commit history, you get a commit fairy tale, which is prettier than the truth, but probably less useful. You get something akin to merging the base branch into the feature branch but things look as if they were done in an order they weren’t instead of getting an ‘ugly’ merge commit.

And yeah, the PETA kills site clearly has an agenda, but their agenda is to try and save animals from PETA’s “love.”

Their agenda’s to make PETA look bad so people don’t become vegan or demand higher welfare standards from meat producers, and they can continue selling meat to Americans of such low standards that it would be illegal in the rest of the civilised world.

You know what no-kill shelters try to do when they don’t have space? Coordinate with local foster programs, coordinate with other shelters to see if they have space. There are other alternatives besides taking in a perfectly healthy animal and dropping it in the euthanasia queue.

As I said, they can’t do that once the foster programs and other shelters are full, too, and then overflow into PETA-run shelters because they’re the ones that still have a capability to receive more animals after they’re full. There aren’t enough shelters to keep every animal in good conditions until it’s either adopted or dies of natural causes, and no amount of coordination can magically create extra capacity.

It doesn’t strengthen your point to link Fox News and the literal website for the smear campaign I mentioned: https://www.sourcewatch.org/index.php?title=PETA_Kills_Animals

As for PETA putting down lots of animals, that’s no secret. It’s really easy to get people to donate to a no-kill animal shelter, so there are lots of them. However, when you’re a no-kill animal shelter, and you’re full of animals you can’t kill, or are asked to take an animal that can’t be ethically be treated with anything other than euthanasia, you have to turn the animal down, and it ends up wherever will take it. Usually, that ends up being a PETA-run shelter. When a PETA-run shelter is being given all the rejects from everywhere else, it’s obviously going to end up putting lots of animals down. It’d be better for PR if they didn’t, but less ethical, and they prioritise the ethics above the PR.

If you look at one of your more reliable sources, the Snopes article, it backs up what I’m saying, and not what you’re saying. It corroborates the story from my original post, lists another incident where PETA staff were accused but not convicted, and then discusses that they put down a lot of animals in their shelters, and how it includes healthy animals. The only controversy there is the definition of adoptable - a healthy stray kitten is theoretically adoptable, but if you get ten times as many kittens in a week as you do people wanting to adopt a kitten, 90% of them won’t get adopted, and your shelter will get quickly overcrowded if you insist on ignoring that fact.

The UK has a high rate of veganism, and part of that is attributed to the fact that the major vegetarian and vegan organisations in the UK generally recommend persuading people by offering them delicious food that is also vegetarian/vegan and saying it’s more ethical. On the other hand, the equivalent organisations in the US tend to lean more towards recommending telling people that eating animal products is unethical, and it’s difficult to accuse someone of unethical behaviour without being insulting. It also doesn’t help that multibillion-dollar organisations have run successful smear campaigns against groups like PETA - everyone’s heard of the time they took someone’s pet dog and killed it, but most aren’t aware that it happened once and gets reported on as if it’s news every few months, or that it was an accident as the dog’s collar had come off and it was with a group of strays, and got muddled with another dog, so was put down weeks earlier than it was supposed to be, bypassing the waiting period they had specifically to avoid this kind of mistake.

It’s a 250W+ part running at around 1V, so it’s going to draw a lot of current. Power is supplied via many pins on the back of the CPU, and they’re connected to many traces, so it’s not putting all that current through just one. It still puts out a lot of heat anyway, which is why modern motherboards have large heat sinks, sometimes with fans, on their VRMs.

I just left a game where someone was using the Spear to great effect, although they were finding it a bit of a pain to lock. That’s pretty different to completely broken.

This kind of mod is always a DLL of some kind, and typically, they’ll have you install the DLL to a location that the script extender will load DLLs from automatically (but sometimes they instead use the same name as a Windows DLL and go in the same directory as the game’s executable, as when the game tries to load the Windows DLL, it’ll try ones in its own directory before System32 and similar folders, then as long as the mod DLL in turn loads the real DLL, everything will still work). When the DLL’s loading, it’ll either overwrite bits of memory corresponding to functions with its own code, or if it needs to replace the whole function, will swap out the first few instructions with instructions to jump to a mod function instead.

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 super quick to swap it on Windows once you know the problem exists and know where to look. You just click the audio icon in the system tray and change the output device in the dropdown from the headset version of the device to the headphones one, and it enables all the higher-bandwidth modes. I’m not sure there’s user-accessible control over which specific codec gets used, though.

Some Bluetooth controllers can’t handle the bandwidth required for sound input and output at the same time unless it’s at very low quality, and if Windows suspects such a device is in use, it defaults to the low quality mode as users are more likely to be able to tolerate it than tolerate their headphones not working at all. It’s overly cautious, though, and uses the low quality mode far more than it has to.