After using (and loving and having paid for) 1P for years, I moved over to Enpass a year or so ago. Their clients are not as good as 1P's, but I simply neither want a subscription based service (what happens if they are bought / go under), nor do I want my passwords to reside on their servers (encrypted or not).
Getting 1Password 7 ready for the Mac App Store
101–110 of 484 posts
Re: Getting 1Password 7 ready for the Mac App Store
#102Earlier quoted context omitted.
Still, this is a trend I will have nothing to do with if at all possible. And besides subscriptions, version 7 will only sync using their back-end, which is not acceptable for me. On one hand, password managers in browsers are becoming nearly good enough to cover for 80% of my use cases, and most of the other 20% boil down to convenience (ease of pasting, updating, etc.) I don't like the idea of being forced to move…
> And besides subscriptions, version 7 will only sync using their back-end, which is not acceptable for me. What do you mean by "only sync using their back-end"?
Older versions could sync with e.g. Dropbox. So to get your passwords, someone would have to break into dropbox and then into your encrypted vault.
Re: Getting 1Password 7 ready for the Mac App Store
#103There are at least two elements to software maintenance: one is adding truly new features, and the other is making stupid changes just to keep old features working as they always did (often due to platform or hardware changes, especially with Apple!).
I see Apple coughing up none of the costs that they create by regularly fiddling with their platforms and hardware in breaking ways, yet that is a big reason why software can’t be sensibly “bought once”. Now they’ve come up with a scheme where they not only don’t give developers discounts for maintaining software but actually take yet another cut.
Don’t judge developers too harshly.
Re: Getting 1Password 7 ready for the Mac App Store
#104I would be okay with the subscription plan if they would allow for a permanent license after the subscription ends. Something like what JetBrains did. I was going to drop using JB software until they added that feature, and now I am a happy ”subscriber.”
I feel what galls people is that we buyers have nothing to show after ending a subscription, especially if we are not using anything “servicey” about said subscription.
Re: Getting 1Password 7 ready for the Mac App Store
#105Earlier quoted context omitted.
Where is that information on their website?
Is this supposed to be a rebuttal to something or do you actually need help finding it?
I'm interested in where it is. I have recommended 1Password to friends saying that I had heard standalone version was still available, but I am unable to find it on their site.
Re: Getting 1Password 7 ready for the Mac App Store
#106Earlier quoted context omitted.
Where is that information on their website?
Is this supposed to be a rebuttal to something or do you actually need help finding it?
A little of both. I did a check and I literally couldn't find it. If it's that well hidden (I have a few licenses from prior versions, so I'm not a stranger to the site) isn't that effectively not having the option?
Re: Getting 1Password 7 ready for the Mac App Store
#107Stupid question: what does this do that iCloud Keychain doesn’t do?
[deleted]
Re: Getting 1Password 7 ready for the Mac App Store
#108So remember when 1Password claimed it was superior to LastPass for only requiring you to pay a one-time fee and not storing all of your stuff in the cloud? Good times.
To be fair, it still does all that stuff.
I get that these moves make people nervous, and rightfully so. But as it stands every version of 1Password in active development (not including maintenance mode):
* Can be licensed standalone.
* Supports local & Dropbox vaults.
* Was released within the last year, actively supporting those features.
The only feature they’ve actually killed off (by not baking into future clients) is WLAN sync. This is a regression for some, but personally I always found it super impractical.
I agree that how they are going about this doesn’t inspire confidence that these features will remain in the product, but to some extent it does.
While they downplay the hell out of it, 1Password 6 for Windows was a ground up rewrite that ditched local vaults and standalone licensing. Those features were reintroduced in 1Password 7 for Windows, which is a pretty big backtrack for them and requires renewed development effort.
AgileBits doesn’t always make the right decision. They develop opinionated software, like most good developers. However, just like the MAS-only decision they made with 1Password 4 and stood by for some time, eventually they do right by their customers.
1Password 7 for Windows is a great example of that. As much as they would love to go cloud only, they heard the feedback and brought back those two key features. At this point, I can’t expect much more than that.
Re: Getting 1Password 7 ready for the Mac App Store
#109Can I use this space to ask how people actually use password managers on mobile? I got LastPass recently and put on it a good secure "correct horse battery staple"-type password. So now when I use accounts on my phone I have to type that password instead of my short, randomly generated, reused-all-the-time password. This means I'm more secure (no password reuse) but typing 30ish characters without error into my phone is tough! It usually takes me three tries and every time I curse my new password manager.
But the alternative seems to be staying logged in to LastPass which means it's just my four digit phone pin to get access to everything. I mean, I guess if someone takes my phone and bypasses my PIN then I've already lost basically everything. But at least I wouldn't also be signing them into my bank account. My phone doesn't have biometrics which I think would be my compromise if it had them.
Re: Getting 1Password 7 ready for the Mac App Store
#110Can I use this space to ask how people actually use password managers on mobile? I got LastPass recently and put on it a good secure "correct horse battery staple"-type password. So now when I use accounts on my phone I have to type that password instead of my short, randomly generated, reused-all-the-time password. This means I'm more secure (no password reuse) but typing 30ish characters without error into my phone…
[deleted]