Yeah, I think that a helps a bit but if it requires actually opening the thread, then it’s only a mild improvement. I’d really prefer mark as read or hide without opening the thread (there’s a lot of threads I have no interest in reading but are hanging around the front page).
I appreciate the suggestion though. It does help a little.
These really aren’t vulnerabilities. Give the github issue a read. Basically, if they have access to the unencrypted db, then asking for the password again is just window dressing. It doesn’t really provide much, if any security value as they already have the data from the db.
Keepassxc is not an online manager. It doesn’t really make sense to require a password when making changes as they already have access to everything if they have local access to the machine when the db is unlocked.