notabot

Thanks for the analogy, that really helps to put it in perspective. I was trying to work out the number of molecules per metre that would leave you with, but either my sense of scales is off kilter or I’ve got it wrong.

From what I can find, there are approximately 2.5e25 molecules per m³ at 1atm. Given an 11km cube has a volume of 1.3e12 m³, that gives around 2e13 molecules per m³ per m³ released. That sounds high, have I got the figures wrong somewhere?

“Gelatinous tuna mold concoction” is a concept I don’t want to have to think about ever again, and I ate similar things when I was a young’un.

Fastration?

It tracks the location of a body (or anything else that causes the same sort if interference), but it doesn’t identify the person, and as such they can reasonably make the claim that this technology is privacy preserving.

Of course, as with anything that claims to anonymise data, or preserve privacy, that assertion starts to fall down when you use the resulting data in conjunction with other data sources, even if they too claim to be privacy preserving.

That’s pretty much what a mercury thermometer does. As the temperature changes so does the volume of the mercury, which causes the level to move up and down, and the temperature scale on the side is just a measure of how high the mercury reaches.

It’s been quite a while since I’ve used sleep on a laptop, but it worked well on my Dell (latitude I think, as I said, it’s been a while). It did take a little experimenting with sleep levels to get it reliable, but once it was it worked for years.

ETA: I realise that saying “it worked for me” is probably intensely annoying, my appologies for that, but I thought a counterpoint might be a useful extra data point.

Destroying the encryption key tends to be the only reliable way to put the data beyond use. Physical destruction techniques like the obe in the article have been tried before, and iften leave the data intact, just destroying the driver side of the chips. It’s not easy to retrieve the data, but a sufficiently determined and resourced oppinent can do it.

Obviously, there’s no reason not to do both, for added certainty, but if the encryption protocols used in proper FDE are compromised, we have a lot more to worry about.

It does seem like it would be simpler and more reliable to use full disk encryption to encrypt the data before it’s written, and just destroy the key if you want to nuke the data.

It’s a bit ambiguous, so you could be right, but I took it to mean that activation of the receptors was that active mechanism, regardless of cause. Psilicin is just the compound they’re focused on, and maybe it does activate them in some unique way that has this effect, but the summary didn’t make that clear.

If there are alternative pathways to activate the receptors they may be better suited to thereputic use without the psycadelic side effects.

I haven’t gone looking forthe souce paper, but from the article it looks like seretonin was the actual compound that’s having a beneficial effect, specifically serotonin outside the brain.

Fair, that maybe came across harsher than I meant. Refusing to provide packages because you don’t use the system is fine, but please provide a tarball that I can unpack, rather than some dodgy script that has to try to work with the differences in those ststems anyway.

Better to do away with the entire concept of downloading and running a shell script like that, and use distro native packages instead. It’s not hard to create DEB or RPM packages, ebuilds aren’t too bad either, and it sounds like AUR packages are managable too.

The entire concept of blindly downloading a script, running it as root, and hoping that, in the best case, it’d install the version of the software you want is a bit crazy. If the upstream developers refuse to provide packages, please, at least, provide a tarball.

This is excellent article on enshitification, some of the factors that can lead to it, and ways founders could think about it to hopefully avoid it. What it doesn’t seem to talk about is how Tailscale intends to avoid it, now and in the future.

The joys of distributed algorithms. You can now get more errors, more quickly than before!

I remember writing a chat system in assembler, for DOS, using, IIRC, IPX networking. When it went wrong, one or more machines would just freeze, with the string “NETWORK ABEND” in the middle of the screen.

I should fork vim and call it ‘death’, so I can shout “give me vim or give me death!” any time someone suggests a different editor.

That has unironicaly made me nostalgic for the days when the web was a place of experimentation, joy and just a bit of crazy.

Yes, the IMEI uniquly identifies the phone itself, so if the GSM radio is on, the network can monitor it’s approximate location.

There’s a couple of caveats: IMEI cloning is possible, but unlikely, and he accuracy of the triangulation will depend on a lot of factors including how far apart the towers are and what sort of obstructions there are between you and the towers. My understanding is that it is done by comparing your signal strength at each of the towers as a proxy for distance. If there’s a large obstruction that reduces your signal to a tower it could throw those measurements off. They’ll know you’re in the area, but not exactly where.

That does feel rther like jumping out of a plane and hoping you can finish making your paracute before it’s too late.

The concept of moving on from X11 is a good one, but making Wayland just a protocol that every compositor has to implement separately, and having so many optional larts to the spec seems like a guarantee that the ecosystem around it will never properly mature.

The KiCad developers have a good article about some of the issues with Wayland here.

Hmm, that one worked for me, but maybe the wayback machine will work for you? https://web.archive.org/web/20250618100950/https://www.linuxjournal.com/content/arch-linux-breaks-new-ground-official-rust-init-system-support-arrives

The article vanished some time after being published, here’s an archive link.