Hacker News Reader

This is the stack I used before switching to bitwarden/vaultwarden. Couple of reasons why I switched:

- I selfhost it on my NAS so I don't have to depend on a 3rd party to sync all of my password (even though they are encrypted).

- If I need to access my passwords from a new/temp machine, there's a web UI I can access very quickly

- The client is much prettier and nicer to use. The KeyPass clients all felt very dated and clunky.

I've been on KeePass + Dropbox since Dropbox first became a thing and I have yet to find a reason to do it any other way.

Or SyncThing. This setup works and more people aren't considering it. The UI is great and the desktop app is not Electron based.

I used to do this. I finally had to switch off of it because the Syncthing Android experience is so bad (necessarily, because Android is bad).

I had many instances of not noticing Android had killed the Syncthing backend again despite being explicitly told not to, and then I had two out-of-sync password databases and would have to go merge them again.

I'm still bitter about it, because Syncthing as a syncing layer is so much more elegant than everyone implementing their own server and sync protocol.