I have yet to meet a KeePass user under the illusion that the syncing story is a good fit for everyone.
But we are prioritizing “can’t” over “won’t” in terms of provider access to our credentials. That’s why these hack-related threads tend to draw folks who will remind you that other tradeoffs exist.
For a technical audience like HN, “can work out how to sync a file” is a decent assumption to make.
One of the security advantages of KeePass being just a file is that you can sync it in the way that makes sense to you.
The need to have an opinion on how you’d like to sync a file does, as you suggest, eliminate some portion of the population who need a fully baked answer in one step.
I used to use Google Drive, but now I use Syncthing, further reducing my exposure. Paired with Synctrain and KeePassium on iOS.
One tip: enable the atomic save option in settings to reduce the risk of weird cloud sync issues.
For folks new to the KeePass ecosystem, it’s KeePassXC[0] now. The original KeePass is still developed as well, however KeePassXC is a cross-platform updated version.
I’m on a 16 pro and I’m holding out on 18 as long as I can. I have not heard a single positive review of 26 from people I trust. I usually update Apple stuff as soon as I can, so this is a departure for me.
Usually DBMSes struggle under very high cardinality of databases. Also, easier migration control is a double-edged sword, with the other side being needing to coordinate many migrations.
You probably don’t want to do what you are proposing except in extreme, carefully evaluated cases.
We pulled all of our business after they failed to renew a cert with 30d(!!!) notice and got themselves stuck in a loop of useless org re-validations.
They were completely unresponsive and wasted dozens of hours of our time trying to rectify the situation before we pulled the plug and switched everything to ACME. I still can’t believe we wasted so much time and money with them.
Suggestion for the site: it references “no navigation” a few times, but I am having a hard time understanding what that means. What kind of navigation is meant here? What are the boundaries of the navigation limits?
Various definitions of “navigation” I can think of:
- no switching tasks in the app
- some sort of phone-wide parental control
- maps is disabled ;-)
Less featureful than this, but we’ve been doing GRPC client side load balancing with kuberesolver[1] since 2018. It allows GRPC to handle the balancer implementations. It’s been rock solid for more than half a decade now.
But we are prioritizing “can’t” over “won’t” in terms of provider access to our credentials. That’s why these hack-related threads tend to draw folks who will remind you that other tradeoffs exist.
For a technical audience like HN, “can work out how to sync a file” is a decent assumption to make.