The problem is that syncing between devices is not implemented in KeePass itself but through an external tool (Nextcloud, Syncthing, or whatever else). The sync client will only see the ciphertext and won’t be able to tell which records have been changed, only that two different binary files have a common ancestor and are in conflict.

The most obvious solution is to lock and close the database when it’s not in use (which is a good practice from a security perspective too), and to sync immediately when it is changed.

tl;dr: yes, credentials are cached locally. https://github.com/dani-garcia/vaultwarden/discussions/4676

The major downside to the single file storage used by Keepass is that it’s easy to accidentally create a conflict between files on different devices if they’re not synced immediately. Conflicting files have to be merged manually or data might be lost. I’ve run into this several times with Keepass + Nextcloud. In comparison, a central master database with local cache can resolve conflicts between individual records.

deleted by creator

Tailscale should work. It uses Wireguard and does some UDP fuckery to get around the firewall and NAT (including CGNAT). I can stream Jellyfin through it at 1080p native with no significant buffering, it’ll work for music.

If you want to be really pissed, read up on doctor disgraced former doctor, lifelong charlatan and grifter Andrew Wakefield. https://en.wikipedia.org/wiki/Andrew_Wakefield

He abused autistic kids in a medical experiment that was meant to convince both the public and the scientific community that a specific combined vaccine (measles-mumps-rubella, a.k.a MMR) could trigger some kind of bowel disease that causes autism, all so he could peddle his own alternative that is three separate shots.

Somehow this step didn’t make it into Mortuary Assistant.