base12 has the advantage of being divisible by 2, 3, 4 and 6, while base10 is only divisible by 2 and 5.

Optical Character Recognition. Basically just extracting text from an image.

Here’s a circular rainbow from an aircraft a skydiver:

EDIT: image embedding didn’t work

EDIT 2: not from a plane

EDIT 3: sorry for all the edits, fixed image

Fun fact about that: in morse code, SOS is a prosign. This means it gets its own special rules.

Rather than being three seperate letters (… — …), it’s one letter without any letter spaces (…—…). This is something that applies to all prosigns in morse code, though most of them are just two letters long.

Also, when sending it on repeat you just continue the pattern without any spaces. Instead of …—… …—… (with a letter space) or …—…/…—… (with a word space), you send …—…—…—…—… and just keep continuing the pattern. iirc SOS is the only prosign where this is a thing.

Other prosigns are for example HH (…) to indicate a correction to something previously sent, and SK (…-.-) (silent key) to signal that you have finished with the current conversation and the frequency is now clear.

No problem, thanks for replying.

That makes sense. It looks like a really clever way of letting the boot process allow for basically any arangement. Thanks!

They do, but compounding errors are always a problem with inertial navigation.

Instead of GPS, they can use fixed radio beacons like VOR and TACAN (which I think are both just US systems, but there are similar systems around the world and at major airports). This is basically the system that was in use before GPS.

EDIT: grammar

Thanks for explaining it! So systemd-boot finds the kernel in the EFI partition, which it then loads, and then that kernel loads another kernel from the main partition, which is then the full OS.

Is there a reason it’s done this way, and not just the bootloader loads the main kernel?

Also, are the two kernels the same, or does this use two different kernels?

If you use btrfs snapshots and systemd-boot instead of grub, then be carefull restoring updates from before a kernel update.

If I understand it correctly, with systemd-boot the kernel lives in the EFI partition, while the kernel modules live in the main (btrfs) partition. If you restore a snapshot with a different kernel version, it doesn’t restore the kernel itself, but the kernel modules have different filenames, which stops the system from being able to boot.

At least that is my understanding of the problem, from having to debug it twice (just start a live-boot system and use Timeshift to restore the system to after the update again). The next time I install Linux, I think I’ll go with grub instead of systemd-boot.

That being said, I really like btrfs snapshots as a sort of “almost backup” (still do regular backups on an external drive). They are quick and easy, and most packet managers can be setup to automatically make a snapshot before installing/updating stuff.

If you decide to set up an SDR for ADS-B, you might want to consider setting up a WebSDR with something like OpenWebRX. This would let people listen to all the signals in the bandwidth that you set.

If you’re interested, receiverbook.de is a list of most WebSDRs.

Replaying Death’s Door

Nope, at least afaik. Prototyping and building cars by hand (without a whole factory set up to build it) is hard. Not to mention extremely expensive. And you have to build multiple (identical) copies of the prototype to get it street legal, because of crash testing. And you have to be able to guarantee that what people build with your kit remains identical to your prototype. Or everyone assembling such a kit would have to build multiple copies of the car and go through the certification process individually.

And of course there are very few people that would want to assemble their own car, so you wouldn’t be able to make a business out of it.

I imagine the film crew took out the windows so that they could shine the lights into the plane.

I’d like to elaborate a bit on why DNS can be used to track you.

Nearly all web traffic is encrypted (https), you can check by looking at the padlock next to the URL in your browser. But DNS requests aren’t encrypted by default. This means anyone, most likely your ISP our the admin of your home network, can see what domains you’re accessing. That means just google.com, lemmy.world, etc. and not lemmy.world/post/… This isn’t a huge amount of info, but it does tell anyone who’s looking approximately what you’re doing (googling something, looking at lemmy, etc.).

To fix that there are a few different ways to encrypt DNS requests, the most common of which (afaik) is DNS over HTTPS, which will encrypt DNS requests like any other web request your browser makes. I don’t know why this hasn’t been made the default yet. Firefox has a setting for DNS over HTTPS, it calls it secure DNS.

I’d try mysterytool -H