Redjard

What’s the point over keepass with syncthing?

Bitwarden seems to be pretty clearly on the path of enshittification. They’ve been going towards closing off the self-hosted versions for a while, and moving their app out of repos that check licenses, with the likely aim of taking it closed source.
The usualy will surely follow.

Not sure how soon, but I definitely wouldn’t newly go to them at this point.

since im not sure where in the boot process linux recognizes my raid and when the decryption happens

Usually raid and decryption happen in the initram. This is because these are too complex to sit purely in the kernel, requiring userspace tools like cryptsetup, but you want to be able to boot off of them so they have to be handled before the disk is mounted.

Usually that initram is dracut. Why dracut only partially completes the process here, likely figuring out the raid but not decryption, is anyones guess. In my experience dracut is quite hard to debug and configure.

The simplest approach is probably to just eat it and write a startup service that does it. Basically a startup command. No need to worry about timing, as when the initram finishes the raid should already be up.
There might be a prebuilt systemd service for it too iirc…

If you really wanns go for it, there are other initram systems like ugrd, which are easier to configure and might figure your setup out properly. But you’ll probably have to manually install and update them. That would definitely be a very involved approach.

There are some guesses I made here on your boot timeline. If you show your dmesg I can confirm if the raid really comes up at initramfs time. But it should be s solid bet.

Kdeconnect is usually gonna go over regular wifi or ethernet. So that might go phone to ap to laptop, for twice the wifi hops.
Also means the speed is limited by the router, so modern phones would be slowed by an older access point.
Or by being far from the access point yet close together.

Your demo instance seems unable to open any other subs.
Also it redirects to an archive path which is not how redlib works and makes me question how the sesmless response regardless of state is supposed to work.
Once it dumps me in the archive for whatever reason, don’t I have to go back manually? (Not that even seems possible right now)

Why was this ever a hardcoded limitation?