I use syncthing to sync almost everything across my computer, laptop (occasional usage), server (RAID1), old laptop (powered up once every month or so), and a few other devices (that only get a small subset of my data, though). On the computer, laptop, and server, I have btrfs snapshots (snapper). Overall, this works very well, I always have 4+ copies of my data in 2+ geographical locations.

TOR exit node IP addresses are well-known. If YouTube wants to, they can just block the TOR network.

The same amount of JXL gives you more image than JPEG? Also, it supports ridiculous resolutions (terapixel).

I took my existing JPEG file, compressed it using JXL, 15% smaller.

Then I decompressed it again into JPEG. The file was bit-for-bit identical to the original file (same hash). Blew my mind!

Directly using JXL is even better of course.

You can check heavens above (adjust your location) to check when it will be visible for you.

Wait a second, it’s going to pass over my house in 5 minutes!

Edit: Shit, clouds!

Edit2: I was able to see it through a few gaps in the cloud cover!

The link is broken, because it is attempting to create a new archive.org snapshot whenever someone clicks on it.

• Original URL
• Working archive.org link

3 weeks, roughly in line with faster Space Shuttle turn around times

The shortest shuttle turnaround time was 55 days. Almost three times as much as Falcon 9. The fastest post-Challenger turnaround time was 88 days, I believe. After Columbia, the fastest turnaround was around 5 months.

NASA claimed that the shuttle could achieve a turnaround time of two weeks (page IX). It looks like SpaceX is not the only one setting unrealistic timelines?

Without UEFI, the boot process is different for each device, requires a custom boot loader, or at least explicit support by the operating system. Is your laptop going to be supported by the distribution you want to use? What about in 5 or 10 years? With UEFI, the boot process is standardized, so it should just work.

This article has been removed at the request of the Editors-in-Chief and the authors because informed patient consent was not obtained by the authors in accordance with journal policy prior to publication. The authors sincerely apologize for this oversight.

In addition, the authors have used a generative AI source in the writing process of the paper without disclosure, which, although not being the reason for the article removal, is a breach of journal policy. The journal regrets that this issue was not detected during the manuscript screening and evaluation process and apologies are offered to readers of the journal.

The journal regrets – Sure, the journal. Nobody assuming responsibility …

Then the editor, all extensions, language servers, etc. are all running as root.