AnyOldName3

u/AnyOldName3@lemmy.world
18 posts · 1.2k comments

Recent posts

Recent comments

Whether or not it's really from Ukraine, it's not implausible that someone might do something illegal while dressed as Spiderman. People break the law, and if they're dressed as Spiderman, then they're likely to be noticed and get arrested.

on Subtly hinting · c/funny · 1 pts · 1d

Aluminium antiperspirant stains are actually pretty easy to remove if you soak your shirts in something acidic - I use sulphamic acid (commonly sold as the main ingredient in coffee machine descaler, so pretty safe, and not as smelly as vinegar) and just leave things for a day, then any residue that's left just comes out in the wash. The reason it stains is that long-acting antiperspirant seals the aluminium salts in tiny wax beads which break open over the course of the day to keep releasing more, and wax needs a lot of exposure to soapy water to dissolve, but it's protected by the aluminium salts jellifying when wet, and they in turn are protected from rinsing away by the surrounding wax. Acids can attack both.

The law was meant to allow tenants to see the real rent up-front so they wouldn't waste time they didn't have on viewing properties then get pressured into paying more than they were expecting. That should have driven real rents down because people could skip things out of their budget upfront and know what they found for less was genuinely available for less. Instead, landlords are just displaying huge numbers they know they won't get, and totally obfuscating the real price.

on Ken Thompson Hack 2.0 · c/linuxmemes · 1 pts · 3d

Unless you pick a particularly short-lived isotope, the radiation wouldn't have time to hurt you before you died of regular heavy metal poisoning like you'd get from something boring like lead or mercury.

on Ken Thompson Hack 2.0 · c/linuxmemes · 8 pts · 4d

Pretty effective because of its high density, too. It's a shame it's brittle and would give you heavy metal poisoning.

If you grab a generic Linux package from our site, then it should see the same config and saves etc. as your system package uses, so you shouldn't even need to back anything up as long as you don't do anything that would overwrite things. OpenMW doesn't do anything like purge settings that don't mean anything in the current version, so sharing one settings.cfg is safe, and you can try a new version and then go back to the old one. The only thing that doesn't work is loading new saves in old versions of the engine, so you'll need to replay anything you did in the new version if you do end up going back.

The exact quote is:

And this was a debug session from hell, enormously helped by an AI doing much of the grunt-work.

I'd like to call it my tireless helper, but the AI several times stated flat out that this was impossible and unsolvable and that we should just write a report about it.

I suspect those things have been trained by people who may not be quite as stubborn as I am.

But while the AI was ready to give up several times, it did keep adding debug code and analyzing it faithfully when I pushed. So credit where credit is due and I let the AI write the commit message above.

This is basically a one-liner fixing a bogus "round_up()" to a "round_down()", but there were 24 patches adding more and more debug information to this, and 18 kernel boot to finally narrow it down to this. - Linus

That's a long way short of finding the bug and pointing it out, and instead is just the tedious work of adding checks and then deciding where to add more checks when you have the result of the previous checks. I suspect if we'd spent a trillion dollars on a tool for that, we could have come up with something much more efficient than an LLM.

We're pretty thorough about stomping out regressions, so unless you're using mods for documented version-specific things (basically just lighting shaders and XML UI mods), we'd recommend almost all users upgrade to every stable release. Given that 0.48 was branched off four years ago (it had a very long RC phase), you'll almost certainly experience fewer bugs if you just grab a random dev build built from a random tip of tree commit.

We're talking about someone who lives with their parents, but there's no indication they've got any buffer. If there aren't apprenticeships within walking distance of their parents' home and they pay poorly enough to not cover housing or commuting costs, then the option of living with parents doesn't do any good because they can't use that option while also doing work.

Can't cause civilian casualties if you've already exterminated all the civilians. It's the only foolproof was to entirely avoid civilian casualties.

It's not automatically resolved on Windows. Applications can export a symbol to hint to drivers that they want the big GPU, just like they can hint with their .desktop file on Linux, but other than that, it's up to the driver vendor to notice a bunch of users complaining about poor performance in a particular game and manually adding it to a massive whitelist, or the user manually changing a setting.

The long-term prospects are better, but if someone doesn't have some kind of buffer like savings or the bank of mum and dad to cover the period where their earnings aren't enough to break even, then the short-term problems make the long-term benefits impossible to actually reach.

The cost of living for someone with a job can be higher than an unemployed person as they need to live where they can commute from, which can make things like living with parents or not having a car infeasible. If the job doesn't pay well enough to cover this, then having no income leaves you better off.