Seems like a positive change to me.
This is not good, it's nonsensical.
All of the disabled features are expendable. I never used any even while they were in there. Yet I do use keepassxc all day every day for the one job it actually does exist to do.
Convenience and necessity are two different things. You want conveninece, and you're not wrong to want it, but you don't need it, and your want of convenience is not important enough to make the base utility when it is a password manager and not a gif editor less safe than it could be by default. It is correct that if you want to trade away safety for convenience, that you have to go out of your way to add that yourself, even if most people will choose to do that, and even if the previous default was backwards and it's now ever so slightly disruptive to correct that error now.
As for friction leading indirectly to less security through user behavior... how many clicks and how many seconds is it to install the full version? So, yet more bullshit.
> Somehow, I have been using the same app without any of those features. So, the idea that the app is not functional or useful without them is bullshit.
Different people might have different needs and wants and other criteria to consider it functional? I think this is not up for you to decide.
And are you putting your passwords on the clipboard in a way that doesn't verify domain names?
Congratulations, you're using insecure methods. Not bullshit.
While I'm not opposed to differentiating between a -full and a -minimal version, calling every plugin dangerous by default doesn't make sense.
Is that xkcd of a tiny project doing a lot of heavy lifting.