AnyOldName3

When they first started ramping up ads and demonetising more videos for being insufficiently advertiser-friendly, they probably still had enough goodwill from users that if they’d immediately launched YouTube Premium and presented it as a way to both remove ads, and support video creators that couldn’t rely on ad revenue, it would have been decently successful. A good number of YouTubers who had to switch to sponsorships and Patreon could have been pushing for people to subscribe to Premium instead of play Raid: Shadow Legends, which presumably would have boosted subscriber counts, and might have been enough to make YouTube profitable and much more pleasant for both free and premium users than it is today. Instead, they burned through a large amount of goodwill before implementing Premium, so people were already more reluctant, and for a long while it only shared revenue with a select few channels who were already raking in ad money, and was unaffected by view counts, so early Premium subscribers were paying Logan Paul even if they never watched that kind of video, but weren’t paying the channels they actually watched.

Upstream Firefox doesn’t comply with FDroid’s rules (thanks to the ‘proprietary bits and telemetry’ Handles mentioned), so is only available from the Play Store or as a loose APK that won’t auto-update.

Being mean is willfully making people around you feel worse. Being cringe is negligently making people around you feel worse. Once you’re aware you’re cringe, if you do nothing to mitigate it, you’re being willfully negligent, which is just as bad as doing something intentionally.

Edit: I’ve posted the same joke as a response each time I’ve seen this meme, and this is the first time it hasn’t been well-received. Just in case that’s down to people thinking I’m being mean instead of making a joke, I’ll clarify that I am in favour of letting people enjoy things.

I’m not arguing for anything in the post above, just pointing out that a broken (or badly repaired) insulin pump is genuinely more dangerous than having no insulin pump. That doesn’t have to count against the right to repair one, as if you’ve got the right to repair an insulin pump, and do so badly, it doesn’t mean you’re legally forced to use it afterwards, just like I’ve got the right to inject all the insulin in my fridge with an insulin pen back to back, but I’m not legally forced to do so.

I do think the right to repair should be universal, but as I think that medical stuff should be paid for by the state, NHS-style, that would end up meaning that the NHS could repair medical devices themselves if they deemed it more economical to do so and recertify things as safe than to get the manufacturer to repair or replace them. The NHS is buying the devices, and gets the right to repair them, and that saves the taxpayer money, as even if they don’t actually end up repairing anything, it stops manufacturers price gouging for repairs and replacements, and if the manufacturer goes bust or refuses to repair something, there’re still ways to keep things working. It doesn’t mean unqualified end users can’t use their new right to repair their medical devices and risk getting it wrong, but if you’ve got an option of a free repair/replacement, most people would choose the safe and certified repair over their own bodge.

If you’ve got a broken insulin pump, assuming you’re in a country with a functioning healthcare system, you should have been given a spare pump with the original, and probably some insulin pens, so when one breaks, you fall back to the spare, and get given a new one to be the new spare (or could get the broken one repaired). Using the spare is completely safe.

If you don’t have a spare, your sugars would go up over several hours, but you’d have a day or two to get to a hospital and potentially several days after that for someone to find you and get you to a hospital, so it’s not safe, but also not something you’d die from if you had any awareness that there was a problem.

If you’ve got an incorrectly-repaired pump, you could have it fail to give you enough insulin, and end up with higher sugars, notice the higher sugars, and then switch to the spare. That’d be inconvenient, but not a big deal. However, you could also have it dump its entire cartridge into you at once, and have your sugars plummet faster than you can eat. If you don’t have someone nearby, you could be dead in a couple of hours, or much less if you were, for example, driving. That’s much more dangerous than having no insulin at all.

Prosthetic legs don’t have a failure mode that kills you, so a bad repair can’t make them worse than not having them at all, but insulin pumps do, so a bad repair could.

Nuclear is even less killy than hydroelectric (dams sometimes burst and drown a bunch of people downriver) and wind (sometimes technicians fall off when fixing a turbine) per kilowatt hour, despite the potential for really scary failures, largely because it generates so much power when it’s working.

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.

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.

If you give a chip more voltage, its transistors will switch faster, but they’ll degrade faster. Ideally, you want just barely enough voltage that everything’s reliably finished switching and all signals have propagated before it’s time for the next clock cycle, as that makes everything work and last as long as possible. When the degradation happens, at first it means things need more voltage to reach the same speed, and then they totally stop working. A little degradation over time is normal, but it’s not unreasonable to hope that it’ll take ten or twenty years to build up enough that a chip stops working at its default voltage.

The microcode bug they’ve identified and are fixing applies too much voltage to part of the chip under specific circumstances, so if an individual chip hasn’t experienced those circumstances very often, it could well have built up some degradation, but not enough that it’s stopped working reliably yet. That could range from having burned through a couple of days of lifetime, which won’t get noticed, to having a chip that’s in the condition you’d expect it to be in if it was twenty years old, which still could pass tests, but might keel over and die at any moment.

If they’re not doing a mass recall, and can’t come up with a test that says how affected an individual CPU has been without needing to be so damaged that it’s no longer reliable, then they’re betting that most people’s chips aren’t damaged enough to die until the after warranty expires. There’s still a big difference between the three years of their warranty and the ten to twenty years that people expect a CPU to function for, and customers whose parts die after thirty-seven months will lose out compared to what they thought they were buying.

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.

Note: this technique cannot be transferred to single-player games. I have tested the hypothesis thoroughly.

It’s at least common on forums as bots love making accounts with non-megacorp email addresses on PhpBB and MyBB forums. Typically, there aren’t people signing up the same services with business emails as personal ones, so if ones expecting not to be used by businesses want to fight spam, it’s generally pretty effective and consequence-free to block email providers not known to have effective anti-bot measures built in.

That would be annoying for people who work on files with a double extension for legitimate reasons, e.g. .tar.gz, and (this can’t be stressed strongly enough) Windows users do not pay attention to warning popups, so it wouldn’t actually help. Despite it being eighteen years since Windows Vista released, and therefore vanishing unlikely that any given software was written assuming that Windows didn’t have a permissions system, it’s still most people’s first troubleshooting step to try and run things as admin, and you still get loads of people (including ones who should know better, e.g. ones who also use Linux and would never log in as root) who disable UAC as one of the first things they do when setting up a windows install, and end up running everything as the equivalent of root just to suppress the mildly annoying pop-up when something asks for elevated permissions.

So, your proposed popup:

• would be annoying including for legitimate uses
• wouldn’t help as anyone who already ignores the smart screen popup that shows up when running a dodgy application will ignore the new popup, too
• would be disabled by huge swathes of users anyway

Typically Windows applications bundle all their dependencies, so Chocolatey, WinGet and Scoop are all more like installing a Flatpak or AppImage than a package from a distro’s system package manager. They’re all listed in one place, yes, but so’s everything on FlatHub.

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.

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.