Your spoiler tag isn't working.

A vote for neoliberals is a vote to not have fascism for four more years. America's voting system doesn't allow the never-have-fascism votes to be pooled with the delay-fascism votes, so unless there's a decent chance for a mass swing of voters from delay-fascism to never-have-fascism, trying to encourage a small-scale swing only makes immediate fascism more likely by weakening the only thing with a chance to delay it.

If the plan is to try and encourage the Democrats to have primaries that actually have the power to move the party left, now is not the time to withhold a vote in protest as there's a good chance that even if it did convince them, there'd never be another election that wasn't rigged so they'd lose it no matter how popular they were.

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.

Abbott was talking about it in general whereas the report was talking about it specifically within the labour party.

It's depleted. They'll just get something like lead poisoning but much worse.

Yep. You can scare people even more by mentioning that it's also used by Windows Update.

NFTs, when implemented properly, would be an item tracked on a blockchain with a link to an asset backed by IPFS, plus some kind of copyright notice granting whoever owned the NFT a copyright licence to do stuff with the asset.

People see IPFS mentioned in the same context as NFTs, and assume it's a scam. People have seen memes about NFTs just being an expensive hyperlink that can go down at any time, so think IPFS can go down at any time. People have seen twitter meltdowns from people who've bought NFTs and then lost access when the previous owner stopped adding redundancy to the IPFS file because the new owner was a moron who didn't know they were responsible for adding redundancy to the files they cared about and had spent their life savings on a esoteric way of getting a commercial copyright licence to something they didn't need a commercial copyright licence to without knowing that's what they were buying.

It's basically just down to NFTs being the thing that made most people who've heard of IPFS hear of it.

Current-generation OLEDs aren't worse than late-generation CRTs for burn-in, they're just worse than LCDs.

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

No, that's the cyborgs.

No, but mostly you.

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.

[email protected] 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?

They're hardly good at impressions, either. Everyone from north of Essex has the same voice, and they have to announce who everyone is when they start talking as if it's The Archers.

Looks cheaper than a horse or motorbike, too, so also cost effective.

That worked pretty effectively in the 1940s, whereas asking the Nazis politely not to invade Poland was completely useless.

It doesn't necessarily work that way, though. If tests tell you you broke something immediately, you don't have time to forget how anything works, so identifying the problem and fixing it is much faster. For the kind of minor bug that's potentially acceptable to launch a game with, if it's something tests detect, it's probably easier to fix than it is to determine whether it's viable to just ignore it. If it's something tests don't detect, it's just as easy to ignore whether it's because there are no tests or because despite there being tests, none of them cover this situation.

The games industry is rife with managers doing things that mean developers have a worse time and have the opposite effect to their stated goals. A good example is crunch. It obviously helps to do extra hours right before a launch when there's the promise of a holiday after the launch to recuperate, but it's now common for games studios to be in crunch for months and years at a time, despite the evidence being that after a couple of weeks, everyone's so tired from crunch that they're less productive than if they worked normal hours.

Games are complicated, and building something complicated in a mad rush because of an imposed deadline is less effective than taking the time to think things through, and typically ends up failing or taking longer anyway.