KeePassXC 2.7.1 Released
keepassxc.orgAs much as I like/use KeePassXC, I don't think we need a post for every minor release.
I'm personally grateful for the periodic reminders. Keeping an eye on what's changed in all the applications I use is a lot of work, and I can let it slide when things get busy. I have specific communities for some things like browsers to alert me to some changes in the meantime, but for something like a password manager which probably doesn't have a thriving online community around it it's nice to know folks here are keeping an eye out for changes and updates.
Same goes for all software. Unless there's a significant change or upgrade in the release, why post? The Emacs post today made sense, because it introduced native compilation. That's a huge speed increase. Not merely bug fixes.
> why post
Because it gets upvoted to the sky every time, for reasons unclear to most of us. Maybe there's an "I've heard of that - upvote" effect.
Yes. People see the name of the project and want to discuss the project in general*—not the minutiae of the latest release. This is a problem because most of that energy goes to the most popular, best-known projects, leading to repetitive discussion, which is the thing we most don't want here. It also crowds out lesser-known interesting stuff.
The solution we've arrived at over the years is to have a major thread when there's significant new information (on a popular topic) but downweight the others.
https://news.ycombinator.com/item?id=23071428
https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so...
* Edit: here's an example from today's Emacs thread: https://news.ycombinator.com/item?id=30932332. That was the top comment on the page just now, until I downweighted it. (Downweighting generic subthreads turns out to be one of the highest-leverage moderation thingies we can do to help thread quality.) It's a fine, perfectly good comment—but it's about $PROJECT in general, not anything new. Such comments are half the fun of HN but they need to not overwhelm discussions in order for things to stay fresh.
This also seems to happen quite a lot for Firefox on here, Dan. I'm a bit tired of seeing Firefox releases on the home page as (IMO) there's never much interesting about the new version. It's mostly just, as you put it above, people wanting to discuss the project in general.
Yes.
Switching from KeePass to KeePassXC for work was one of the best decisions I've made in awhile.The modern GUI is cleaner, stuff is easier to find, and the browser integration extension is much better. I have yet to find any downsides.
Every time KeePassXC comes up, I think about when I tried to switch from KeePass in 2020 and wrote myself the following notes:
I hope someone can tell me I am wrong and somehow overlooked these features.* Does not have global hotkey to show window * Does not have {PICKFIELD} auto-type placeholderI guess I never felt the need for a global hotkey to show window. 90% of my password autofill is through the browser extension, and if you click the KeePassXC icon next to a field and the database is not open, KeePassXC itself will pop to the forefront to allow you to re-authenticate.
Interesting that they are changing the official distribution method from snap to flatpak. I've had much better experience with flatpak than snaps.
I don't think I've personally heard someone praise Snap over Flatpak.
Also interesting because PopOS has flatpak built directly into the software center. No idea how common that is.
Redhat family of distros are the same.
Why is it interesting then? Or did you have a better experience with snaps?
Just happy that they made the switch. Not interesting in the sense that it is unexpected.
One additional change that came after the release of 2.7.0 and is continued in 2.7.1, there are now builds that support legacy Windows 64-bit (7/8/8.1) as the main builds are only for Window 10/11 64-bit starting with 2.7.0. The last version to support 32-bit Windows is 2.6.6 and as that's no longer updated, it would be better to switch to mainline KeePass on 32-bit Windows.