The keepass ecosystem is comprised of a dozen implementations of the KDB(X) file spec. Some are better than others.
I built KeePass Tusk back in 2018, for example. This would kill the project and abandon 30K users without a rewrite of the JS engine (there are several now!)
I agree with you that KDBX sucks, but at this point a keepass based on SQLite would be keepass in name only, a new password manager to migrate to.
Breaking format changes is not such a major issue, they happened before: kdb → pre-2.08 kdbx → kdbx3 → kdbx4. If the new format is worth it, popular apps will adopt it within a few years — while still supporting older formats. Users would just stick with their current format until the ecosystem catches up, as it happened with KDBX and KDBX4.
Hey I’ve seen your project before! You bring up a super good point that I was thinking of when I brought up the idea that the extension should be renamed to .kp . Really the only reason to keep the KeePass name would be branding, people know and trust it. Honestly my dream password manager is essentially something that uses the CodeBook (by SQLCipher authors) storage format, but with the nice trustworthy, FOSS KeePass ecosystem chrome on top of it (keepassxc<-browser>, keepassium, etc).
I've ripped and archived CDs for well over a decade, purchase from Bandcamp and — if I can't find a way to buy it — I'll find it and buy a shirt or something from the band as directly as possible.
It's an advertisement for noai.duckduckgo.com, a version of DuckDuckGo that disables the AI features and tries to filter out AI-generated content. (Or, if you choose "yes", it's an advertisement for DuckDuckGo's AI features.)
Aside from the fact that it kind of obviously is if you "vote" the fact that it says "Not sure yet? That's okay — vote anyway!" is kind of a give-away that this isn't going to produce anything like rigorously useful data on the question (it produces a lot of other data though!)
At least for me it tells me about some options to use ai privately for duckduckgo so I assume it's from them. Possibly collecting views for Ai generated search results.
Yes, it seems to be DuckDuckGo advertising that they'll let you control the use of AI in searches rather than foisting it on you by default the way e.g. Google does.
I editorialized slightly on the title, but this post made me want to go and play more with the personality in my Claude file to reinforce some of these same values. I might even copy some of it verbatim.
I would love to see some deep economic analysis of what the fuck is going on with Bombas. Why is everyone on the internet trying to sell a helix mattress? How does a marketing department even negotiate that many different contracts with that many small scale influencers?
> scholarly dark matter that exists to pad CVs and satisfy bureaucratic metrics, but which no one actually reads or relies upon.
Is it cynical to believe this is already true and has been forever?
Is it naive to hope that when AI can do this work, we will all admit that much of the work was never worth doing in the first place, our academic institutions are broken, and new incentives are sorely needed?
I’m reminded of a chapter in Abundance where Ezra Klein notes how successful (NIH?) grant awardees are getting older over time, nobody will take risks on young scientists, and everyone is spending more of their time churning out bureaucratic compliance than doing science.
I built KeePass Tusk back in 2018, for example. This would kill the project and abandon 30K users without a rewrite of the JS engine (there are several now!)
I agree with you that KDBX sucks, but at this point a keepass based on SQLite would be keepass in name only, a new password manager to migrate to.
reply