Considering it would be completely possible to make this distinction without breaking existing users, it's difficult to see this as anything other than a bad de

Considering it would be completely possible to make this distinction without breaking existing users, it's difficult to see this as anything other than a bad decision by the Debian package maintainer. While having the ability to have KeepassXC without networking features is certainly nice, considering the browser integration to be a niche feature is just severely out of touch; I would be willing to place real money on betting that more than half (probably well over half) of users of KeepassXC in Debian today want features that will be surprise-disabled because the maintainer chose a way of doing this that would break existing users to impose their opinion. It is ultimately their decision to make, but that doesn't mean it is a good one, I contend it is not.