Keepassium used to be listed (I think), should I now prefer alternatives?

Yet chromium is bashed by developers working on alternative firefox based browsers regularly and yet TinFoilChat dev is allowed to criticise SimpleX.

To be clear, I am not against the above criticisms. I support those criticisms. I just want to point out that I think there is inconsistency in this message. If PG wishes to be fair, projects should be allowed to criticise other projects if the criticisms are valid. Keepasium’s criticism is valid, and they should be allowed to defend themselves if PG “softly implies” anything to them which they perceive as incorrect.

Disclaimer

Please do not flag this message, just reply here it DM with what CoC guideline it breaks, I will edit it asap. This is also NOT off topic as it ties into the thread about Keepasium not being recommended and their team being criticised for coming into the forum with valid complaints.

1 Like

Constructive criticism is welcome for sure. Otherwise how would anyone improve.

3 Likes

It seems to me that wanting to remove strongbox was motivated by them misrepresenting themselves as open source, not due to their closed source nature. That is a distinct issue from the open-source password managers issue.

If it is irrelevant then that topic should be closed with a link to the relevant one posted.

3 Likes

I actually see no reason, why Keepassium should not be listed as recommendation on Privacy Guides.

4 Likes

From kepassium’s POV privacy guides is saying (according to Jonah’s comment and the current recommendations) that their project is less trustworthy than strongbox, to an extend I understand why they are pushy.

Also if current guidelines don’t have any problem with strongbox lying about being open source then the guidelines seem very incomplete.

Off topic

Summary

If anything this looks like criticism against privacy guides not the competing project strongbox.

1 Like

2 posts were merged into an existing topic: KeePassium (iOS Password Manager)

No, unfortunately I did not see any of your comments that you have linked, because they were posted in closed GitHub discussions/issues and solved question topics on this forum (i.e. this one, where this ongoing discussion is off-topic). I don’t go back to look at solved and closed discussions like this one generally, because unfortunately I’m not yet omniscient and my time is limited. I will look through your links now.

The fact is that if someone wanted me to look at KeePassium then someone should have opened a topic about it in Tool Suggestions, like every other tool we look at. Still nobody has done this, so it is no surprise that it has not really been on my radar.

However, I will open a new Tool Suggestions post for you, and from there I will take a closer look at KeePassium :slight_smile:

Now I will lock this thread, because our advice forum is obviously an inappropriate venue to have this discussion in the first place. I’m sorry our community’s organization is apparently confusing, but generally things eventually work out whenever there’s clear community consensus.


To quote our evaluation criteria:

Usability: Tools should be accessible to most computer users. An overly technical background should not be required.

This absolutely includes feature-set.

I’m unaware of KeePassium ever being listed. I’m not sure where this misconception came from.

As @ph00lt0 mentioned this is still actively being discussed.

Things only slip through the cracks when they are not organized and categorized properly, as I was alluding to earlier. I/we try to keep up with and triage misplaced discussions the best we can, but we also try to give the community all the tools, documentation, and resources necessary to understand how Privacy Guides works, and if discussions still get lost it can certainly take a while before we take note and get things back on track. Like my reply here :pensive:

1 Like