3 ms·
What's wrong with KeePass, besides low marketing budget?
by hoseja 6y ago
What's wrong with KeePass, besides low marketing budget?
- Macha 6y ago1. No inbuilt syncs. Dealing with sync conflicts manually eventually gets frustrating. 2. No multiple URL support. I had to have three entries for roll20 to support their app.roll20.net, roll20.net and forum domains. These duplicated entries also make rotation a pain and reduces the value of duplicate password tests when migrating to a password manager approach initially. 3. Poor Android apps. Apps don't support auto fill, have a UI from the gingerbread era, don't sync well even given the above caveats, and the android file system permission tightening has made using a seperate unrelated app to do the sync more painful. 4. Lack of a standard for identifying apps. Do they use the URL field and put the store ID in there? Do they use a custom field to allow having app + website login use the same entry? Does your next mobile app use the same field or even support that field?
- SV_BubbleTime 6y agoTell you what, I’ll give you my moms phone number and you have her set up keypass remotely with only quick basic instructions. No? Because she was able to set up and run Lastpass fine.
- dingaling 6y agoAnd now she'll have to export and migrate away from Lastpass. So the complexity was basically tail-loaded. One of the major advantages of an app like Keepass{whatever} is that once it's set up it keeps working without subscription or keeping an eye on your inbox for changes to the Terms of Use.
- SV_BubbleTime 6y agoShe could pay the $12 or whatever it is.