Memory safety would be the main advantage.

https://stackoverflow.com/questions/10602504/how-does-user-js-work-in-firefox-in-detail:

It just looks like a JavaScript file. Once upon a time in Netscape 3 and maybe 4 it actually was, but now it's just a file with a .js extension and a very restricted syntax that's parsed by a separate (non-JS) parser and not executed in any way.

singlelogin.re still worked for me recently.

Source

You should not torrent over the tor network, but you can torrent over the I2P network. qBittorrent even has experimental I2P support built in.

Yes, for example, syncing on a kernel panic could lead to data corruption (which is why we don't do that). For the same reason REISUB is not recommended anymore: The default advice for a locked-up system should be SysRq B.

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

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

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.

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.

But you can do this.

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

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.

Try removing all the superfluous default routes.

Could you run sudo lshw -C network and post the output for the wireless interface?

Try perhaps the solution in https://unix.stackexchange.com/questions/648084/docker-interface-tears-down-wifi-internet

Cataclysm: Dark Days Ahead

You can give chisel a try. It tunnels all traffic over http/https, and the client can then create port forwards, just as with ssh, to access other services.