addie

Dang. It's going to take a dedicated regime to fill up a one gallon jar with, eh, fluids.

Yeah, but from the two billion tonnes a year of steel that's produced, about five percent is carbon added to iron, and about half of that remains in the final product, so that's about fifty million tonnes released to atmosphere. Whereas about three and a half billion tonnes of coal was burned for power, and that all ends up in the air. A seventy-fold reduction is quite significant; means we can selectively close the higher-sulfur-content mines for an even better improvement in air quality.

Ironic, since 2B doesn't have ass on any platform. My anaconda don't want none of that.

Android has a massive built-in library of supporting functions that abstracts away most of the differences between devices, including support libraries for older versions of Android, and Flappy Bird is almost the "hello world" of gamws writing.

"Register bit twiddling." Setting all the modes that all their various cards can operate in, with the associated code for sending the bit updates over the connection bus. Tedious stuff that's very prone to copy-paste errors if written by hand.

At some point you have to take AMDs word for it that these codes = this functionality, but if the right graphics come out then it can't be so wrong.

Fake mews, surely? And yeah, this looks better than my Monday.

September 16 is a relatively common day for birthdays; 7% more common than the annual average. So I make the expected value about 3.1. Happy birthday to you, and fuck them.

Because if you disable browser autocomplete, what's obviously going to happen is that everyone will have a text file open with every single one of their passwords in so that they can copy-paste them in. So prevent that. But what happens if you prevent that is that everyone will choose terrible, weak passwords instead. Something like September2025! probably meets the 'complexity' requirement...

A bit like when we renamed all the master/slave terminology using different phrasing that's frankly more useful a lot of the time, I think it's about time we got rid of this "child" task nonsense. I suggest "subtask". Then we can reword these books into something that no-one can make stupid jokes about any more, like "how to keep your subs in line" and "how to punish your subs when they've misbehaved".

Well now. When we've been enforcing password requirements at work, we've had to enforce a bizarre combination of "you must have a certain level of complexity", but also, "you must be slightly vague about what the requirements actually are, because otherwise it lets an attacker tune a dictionary attack against you". Which just strikes me as a way to piss off our users, but security team say it's a requirement, therefore, it's a requirement, no arguing.

"One" special character is crazy; I'd have guessed that was a catch-all for the other strange password requirements:

• can't have the same character more than twice in a row
• can't be one of the ten-thousand most popular passwords (which is mostly a big list of swears in russian)
• all whitespace must be condensed into a single character before checking against the other rules

We've had customers' own security teams asking us if we can enforce "no right click" / "no autocomplete" to stop their users in-house doing such things; I've been trying to push back on that as a security misfeature, but you can't question the cult thinking.

We've found it to be the "least bad option" for DnD. Have a Discord window open for everyone to video chat in, have a browser window open with Owlbear Rodeo or Foundry / Forge for your tokens and character sheets, all works smoothly enough. The text chat is sufficient for sending the DM a private message; for group chat to share art of the things you've just run into or organise the next session.

Completely agree that for anything "less transient", then the UX is beyond awful and trying to find anything historical is a massive PITA.