Sam Sneddon 🏳️‍⚧️

@gonzo_askold@mastodon.social @bagder@mastodon.social there’s plenty of things where there are inputs which aren’t hashed in Nix: time/date, random, host name, username, file system enumeration ordering, memory allocation, etc.

I know plenty of cis people who view statements like “death before detransition” as hyperbole, but it’s really hard to express quite how bad both the discomfort of living as a gender you are not, day in a day out, and being on the wrong hormones, actually is.

For #TDOV this year, consider what you can do to push back on the rising anti-trans movement, and put that into action over the next year. If you’re unsure, here’s some actions:

• write to your elected representatives (and candidates, if there are elections coming up), and push back;
• look at spaces you frequently go (whether a cafe or your office, etc!) and push back on any sort of “biological” distinction between restrooms (either by not allowing such a distinction to be introduced or by changing them all to be unisex);
• imagine your new coworker is a stealth trans person: is there anything that could make your workspace more comfortable for them?

@swope@mstdn.plus @Aaron_DeVries@mastodon.social it’s inherent to all SSDs, to varying degrees, because it increases leakage from the cells — from memory offline storage at temperature is actually worse than online behaviour. you can certainly design SSDs to be better at high temperature, mostly by doing the normal things to decrease leakage, like single layer cells, decreasing density of the cells, increasing the number of error correction bits, etc. you can also just mitigate the online case in firmware, by increasing cell refresh frequency. such SSDs are manufactured, primarily for industrial, aviation, automobile, and similar applications, and especially targeting such markets you’ll often find data sheets giving a lot more detail about retention at temperature.

@Edent@mastodon.social As someone who use Matrix a bunch, it is… frustrating in many ways. The disjoint, half-redone apps don’t exactly leave a fantastic feeling (and if it’s taking years to reimplement what is mostly a chat protocol, then maybe you’ve over-complicated your protocol). The various times when apps spin loading, clearly spending a lot of time going to the network for content any other app would’ve cached feel like relatively basic usability. And yeah, even if you’re excluded from message data for DMs, you can at the very least implement client-side blocking/hiding of it. Some of the worst bits of badness I’ve avoided by not being on the largest server, and on one that cares much more about moderation. But that’s a single shortcoming solved — every implementation of the protocol I’ve tried just… has not been good. For so many things which I use Matrix for, I do wonder if we’re gonna reach a point where IRCv3 is stable enough and has enough adoption that channels on major servers can turn on things like persistence and threading, and then we’re just going to head back to IRC.