crunchymunchytoast
It says at the bottom you're using a version built in Nov 2021, you might just need to update to the latest release (latest Arch release is 4.23-1, built 10-29-2023).
If the version in your repos is that out of date though (you didn't state your distro so there's no telling offhand), your best bet may to be to build it from source and install it.
I think your options are mainly virtualization or something like this
Virtualization is definitely easiest though; there's a transmission docker image out there that's preconfigured for a ton of VPN providers, including mullvad. It can be touchy to get working but is amazing when it does work.
mean I wouldn't doubt it, it's just something from my saved posts on reddit. Even if it is AI generated, I still think it's a cool wallpaper and wanted to share ¯\_ (ツ) _/¯
I suppose it depends. An 4/8gb RPi 4 may be able to handle a smalll instance, keeping in mind that a 2 core/4gb VPS has sufficed for most instances until the recent influx. My concern with using one would be primarily with storage capacity and speeds, but iirc, there's a SATA hat you can get to connect drives directly (as opposed to external USB storage).
A good frame of reference would be the VPS that lemmy.world is running on imo. Looks like they upgraded to a 4 core/16gb setup to handle the influx of users, so if your instance is running under 1k users, I believe those specs would be sufficient.
If it starts chugging, I wonder how well it'd work to run the server on the laptop and the DB on a VPS (or vice versa).
I use librewolf from the aur so I'm not sure if this would apply (or if you've already tried it), but try moving the "native-messaging-hosts" directory from the ".mozilla" directory to your waterfox directory in your home and then symlinking the waterfox directory to ".mozilla"
KeepassXC technically only has support for Firefox (and other mainstream browsers) so it always puts the required files for the integration into that ".mozilla" directory.
Speaking purely on speculation, waterfox in a flatpak should already have read/write access to whatever folder in your home it uses for user data so I'm assuming that the difference in where keepass puts the "native-messaging-hosts" is what's causing your issue.
If that's not it though, you could likely use bubblejail to tweak the permissions of the waterfox container to grant it access to those folders. Or double check that browser integration is enabled in keepass.