You can take the package from the Ubuntu PPA, which is generally updated quickly, and rebuild for Debian using the instructions here.

According to Wikipedia:

In March or April 2023, it dimmed to magnitude 12.3. A similar dimming occurred in the year before the 1946 outburst, indicating that it will likely erupt between April and September 2024.

Try removing all the superfluous default routes.

Argon2id (cryptsetup default) and Argon2i PBKDFs are not supported (GRUB bug #59409), only PBKDF2 is.

There is this patch, although I have not tested it myself. There is always cryptsetup luksAddKey --pbkdf pbkdf2.

GRUB works just fine with LUKS2 these days. There is no need to switch bootloaders.

This seems right and exactly the way I've set it up. On subvolid=5 I have subvolumes @ and @home, in /etc/fstab I mount / as subvol=@, and /home as subvol=@home.

Redirector allows you to specify a pattern to do that.

Funny enough I arrive at this the most when I play the Triassic and my opponent goes for a Cretaceous game structure.

We have those on I2P already, see tracker2.postman.i2p for example.

I thought about torrents, but found no way to do that privately either.

You can torrent privately using I2P (It's like Tor but peer-to-peer). The Java router comes with a pre-installed torrent client, accessible from the console. After installing and setting up your browser you can browse the main tracker at tracker2.postman.i2p.

I occasionally experience the same thing. When this happens, it appears the jwt token is not sent with the initial request (thus appearing to be logged out), but it is sent with api requests on the same page (unread_count, list, etc.), so the cookie is not lost (document.cookie also shows it). Sometimes refreshing again fixes it, but I haven't yet found a good workaround. I'll experiment a bit next time it happens.

But you can do this.