AnyOldName3

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.

A lot of the comments are making the assumption that the buttons are telling the truth about being different sizes, but I’ve flushed plenty of toilets where both buttons do a full flush. If you can’t tell the difference after experimenting, it might just be broken or cheap tat.

You can’t really find out of you’ll get good enough to enjoy a soulslike without buying one and playing it for longer than the two hour refund period. For other products, you usually have something you can do about it or some way to try it first. You don’t need to buy a kayak to find out you don’t like kayaking as you can go for a kayaking lesson first and use the venue’s equipment. It’s understandable that people who hit a wall and can never get any enjoyment from a soulslike will be upset that it cost them just as much to find that out as it costs someone who’ll compete the game and have a great time.

Maybe it’s enough to just do the refund window based on progression rather than time.

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.

If anyone’s in this thread because they’re looking for a new mail client after Microsoft killed the old Mail app, and haven’t been happy with the typical suggestions of using each email service’s web interface or Thunderbird, I found I don’t hate Mailspring (with the fancy features disabled - I just want my email client to do email well and don’t want extras that provide clutter).

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.

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

They banned someone for a few weeks who’d comment Dub time on dubs after some weirdos got irrationally angry about it and mass reported her. There’d also be a meaningful comment on the actual episode from the same user, but it wouldn’t be upvoted as much, so wouldn’t be displayed as prominently. Before the ban and after it was reversed, there’d typically be an argument in the replies to the Dub time comment between people angrily ranting about it and other people defending it.

So there clearly was some moderation, but beyond an automated bad word filter, and I guess something blocking URLs, it was done sparingly and reluctantly.

Better have comments on Crunchyroll than make me go to R*ddit to find out if I missed something in an episode, especially as anime subreddits typically start permitting episode spoilers before the dub for that episode is out, so there’s often nowhere except the dub comments on Crunchyroll that’s safe to look for dub watchers.

Super useful for something like Overlord, where scenes with background information were cut and there’d be someone saying what else you’d know by this point in the manga, or if you’d forgotten something since watching a previous season and needed a reminder.

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.

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.

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.