addie

IVEBEENUSINGTHISKEYBORDFORWHOLEMONTHNDMMOREEFFICIENTTHNIVEEVERBEENBEFORE

No 'a', so it's perfect for ordering some piss.

Impressive, since "network effects" are what keeps people on a platform. Why move off Xitter or FB when everyone's on there, and not on the new place? Keep moving a significant fraction of a million people every week, and pretty soon, it'll be where everyone is.

My partner, who is very non-technical, signed up for a BlueSky as well this week: "all the teacher blogs have declared that they are moving over". Looks like everyone has had enough.

Writing this on a Tuxedo Pulse 14 gen 3 - great laptop, flawless Linux support and a coding workstation. Perfect for a bit of eg. Disco Elysium or Crusader Kings 3 on the go, but it's no gaming machine; it has a lot of pixels for a Radeon 780M to push. They do have a list of gaming laptops, though, if you wanted a speciality machine?

Having had one of the old Windows phones with a keyboard dumped on me at an old workplace, can confirm it's completely possible for a phone to have a keyboard and be a complete piece of shit.

A good phone with a good keyboard may have some use cases. If you do a lot of writing but not any more computing power or screen space than a phone has, plus you want to be doing that on the move, then yeah. For me, can shitpost on forums using my phone in my spare time, and dealing with on-call work issues - having multiple tabs of Jira and Slack open, for instance - just isn't really practical on a small screen.

If your job is very email-centric, then yeah, sure. Blackberry were very good for just having the stuff you need - email, vpn, 'corporate' office documents - in a form that worked.

Assuming that these have fairly impressive 100 MB/s sustained write speed, then it's going to take about 93 hours to write the whole contents of the disk - basically four days. That's a long time to replace a failed drive in a RAID array; you'd need to consider multiple disks of redundancy just in case another one fails while you're resilvering the first.

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.

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.