Title, I've also added a little note saying that KeePassX doesn't have regular updates, feel free to use a shorter term to say that, I couldn't remember it. Brought up by #259.
Sidenote: The box is too small for all the text, should we just remove the update comment?
Title, I've also added a little note saying that KeePassX doesn't have regular updates, feel free to use a shorter term to say that, I couldn't remember it. Brought up by #259.
Sidenote: The box is too small for all the text, should we just remove the update comment?
### HTML Preview
http://htmlpreview.github.io/?https://github.com/hugoncosta/privacytools.io/blob/patch-3/index.html
Hmm,
The community edition does seem to have a more active development, I don't know what @Shifterovich thinks but replacing it completely might be more interesting route.
Hmm,
The community edition does seem to have a more active development, I don't know what @Shifterovich thinks but replacing it completely might be more interesting route.
Wanted to suggest that, but that might require some additional feedback. I know that some people prefer KeePassX over KeePass2 because they don't like mono. But I don't know anything about the community edition.
Wanted to suggest that, but that might require some additional feedback. I know that some people prefer KeePassX over KeePass2 because they don't like mono. But I don't know anything about the community edition.
I'm fine with approving this as a temporary measure but how many forks of KeePass are there?
KeePassX?
KeePass2?
KeePassXC?
I personally use KeePassX (on an offline VM), not a fan of mono either :P
I'm fine with approving this as a temporary measure but how many forks of KeePass are there?
KeePassX?
KeePass2?
KeePassXC?
I personally use KeePassX (on an offline VM), not a fan of mono either :P
I suppose we could poll on reddit about this one?
I like the active development of KeePassXC but I hadn't heard of it before and don't know any of the devs..
I suppose we could poll on reddit about this one?
I like the active development of KeePassXC but I hadn't heard of it before and don't know any of the devs..
I like the active development of KeePassXC but I hadn't heard of it before and don't know any of the devs..
Exactly. Non-maintained software is better than ill-maintained software.
> I like the active development of KeePassXC but I hadn't heard of it before and don't know any of the devs..
Exactly. Non-maintained software is better than ill-maintained software.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
jonah
Title, I've also added a little note saying that KeePassX doesn't have regular updates, feel free to use a shorter term to say that, I couldn't remember it. Brought up by #259.
Sidenote: The box is too small for all the text, should we just remove the update comment?
HTML Preview
http://htmlpreview.github.io/?https://github.com/hugoncosta/privacytools.io/blob/patch-3/index.html
Hmm,
The community edition does seem to have a more active development, I don't know what @Shifterovich thinks but replacing it completely might be more interesting route.
Wanted to suggest that, but that might require some additional feedback. I know that some people prefer KeePassX over KeePass2 because they don't like mono. But I don't know anything about the community edition.
Maybe put the replace the See also with "KeePassXC and KeePassX (older)"?
I'm fine with approving this as a temporary measure but how many forks of KeePass are there?
KeePassX?
KeePass2?
KeePassXC?
I personally use KeePassX (on an offline VM), not a fan of mono either :P
KeePass2 isn't a fork iirc. I think it's the official cross-platform successor of KeePass
I suppose we could poll on reddit about this one?
I like the active development of KeePassXC but I hadn't heard of it before and don't know any of the devs..
Exactly. Non-maintained software is better than ill-maintained software.
Will do for now.