It's even weirder when people dismiss real issues as "works just great". Just use the great old version and ignore all future changes if they scare you!

Haha, this is essentially what the original maintainer (Dominik Reichl) does. He keeps a 1.0 and 2.0 version depending on which format you use.

> Many file sharing tools, sync tools, and some cloud platforms (Dropbox for instance) support delta syncs with block-level delta compression.

Ok, but "some" isn't even "many", and the core reason why the single-file problem doesn't go away with sqlite

Instead the new solution must be dumb-cloud-friendly any rely on multiple files, and definitely split all the pdfs and icons away from the few kilobytes of actual user passwords

> but "some" isn't even "many"

True, but it’s a start.

Splitting the file into pieces is certainly not the right way to go about it though, as you would just be poorly emulating VeraCrypt! The most robust sync solution is an actual protocol (like Bitwarden), otherwise dumb file syncing is going to have the same issues it usually has.

Veracrypt is a single file container, did you mean Cryptomator? And how does a protocol help with a dumb cloud with local file access? You'd still need to define a local scheme

Nope, I meant VeraCrypt. As I assumed you meant splitting attachments into their own BLOB. This means you would have the KDBX file, then the attachment blob. I’m saying that you might as well use a purpose built encryption container tool.

As for the protocol my main argument is that passing around a file with dumb syncing is always going to have issues. The only real way to mediate it is to have a defined schema and standardized sync protocol between keepass clients. This would make them behave more like a centralized password manager. However, this approach would require some sort of relay infrastructure and just ends up emulating syncthing but for application specific data rather than simple files. It’s far out of scope for KeePass IMO to build a p2p sync protocol.

Editing this comment because a user in this thread actually acknowledges this point:

> Solving sync and sharing cannot be done on whole database file level, as it implemented now in KeePass. Changes need to be tracked at the password record level, all changes need to persisted as operations log and that log needs to be distributed across devices.

> I’m saying that you might as well use a purpose built encryption container tool.

Which is what keepass is, it just fails in a few ways (built to contain passwords and attachments) some of which are what the format change suggestion is supposed to fix. So I don't understand the conceptual disconnect.

> passing around a file with dumb syncing is always going to have issues

That's true of everything, including the protocol. But also, how does it help if you think the protocol is out of scope anyway, so shouldn't block non-ideal improvements? Let's not perfect be the enemy of the good?

> New, modern launcher for macOS, built from the ground up

The only sign of modernity noticed is leaving good old stuff behind:

> macOS 15 Sequoia or newer required

It was Tahoe only at first but quite a few people asked me to lax the version requirement and now you're telling me that's a problem too?

lol

Does your dog have a phone number?

> All of them can be killed

> Anyone can be killed, my Lord!

So nothing is decentralized?

Then you'd have to copy the old one over to keep it alive

It isn't minimal since it depends on a terminal

That doesn't explain it since that point is theoretical, in reality markdown is poorly readable even for the basics (table with a few bold red words in a cell easily breaks alignment / readability)

(also seeing all those marks isn't aesthetically good, hence the need for a viewer)

It is right by definition. Link emacs to those controls, shed some statically linked weight, and it will also become lighter!

So build it in Wordpad?