It's not the ideal solution, but it is approachable and understandable for technically averse users. I think it's good to have, but I only used it for one package, and that was as a separate Steam install that included an old version of glibc that was used in a particular game's (Squad) anti-cheat until it updated it.

It's good for a stable platform, but each package needs it's own set of everything, which can be good (like the Steam example above having its own version of glibc instead of using the shared version on my system), it's a lot of bloat. I'm not using it unless I require it for some reason, but again it's nice to have around.

The desktop app can be used as a bridge for biometrics in the browser extension, but other than that, it basically serves no unique purpose unless and until they add autofill for desktop applications.

I also would like to know what the desktop app is used for?

I've seen apps like xpipe that have direct Bitwarden integration if you want (way too high risk for me but I can see some people using it), but even then it integrates directly to the servers API. When I need an ssh password or something I copy and paste it from the browser extension. I'm curious if I'm missing some functionality by not using the app.

Is the a downside to repacking the deb package? They're basically just zip files of the same binary you'd run on most other Linux distros.

Reposting the link from another comment on here, there is a PR to build the flatpak from source https://github.com/flathub/com.bitwarden.desktop/pull/222

Why on Flathub it says that it "uses legacy windowing system", but there is granted permission to use Wayland socket in manifest?

It looks like they are working on fixing that with this pull request.

Baby steps?

Bit of a plug, but use gam? https://github.com/fmstrat/gam

Price of the centralization?

Sync that has never broken for me and works on a phone. My attempts at keypass with both google drive and syncthing invariably ended up with me needing to periodically do manual reconciliation. I’ve never had this problem with bitwarden. Also, bitwardens passkey hooks work on iOS. They appear unsupported by keepassium.

Probably a bit more polished UX (especially for not too tech-savy people)

but I'd say the biggest difference is integrated multidevice support, either via their cloud or selfhosted...

I cannot access my homelab from my work network, so I cannot sync via Nextcloud. Syncthing would be better, but they just stopped supporting Android sync, which I need. Proton Drive doesn't sync files on Android. On top of that, I don't want to deal with sync issues because keepass isn't designed for syncing like that. I'm not gonna go back to using Google, Microsoft, or Dropbox just for keepass. I've considered just keeping my db file on a flash drive, but all of the keepass Android apps I tried won't automatically detect that the file exists when I plug in the drive.

If someone has a better way for me to use it, please enlighten me.

Bitwarden is slowly turning their stuff closed-source, and I hope they don't turn to shit, but right now it's what works.