Live data from Hacker News

1Password X: A look at the future of 1Password in the browser

blog.agilebits.com

51–60 of 181 posts

Re: 1Password X: A look at the future of 1Password in the browser

#51
Chrome only makes this effectively useless. Considering that the entire browser market is moving to a largely unified web extension format this is not that impressive. "Everywhere Chrome works" is simply repeating the mistakes of the past, but with Chrome now instead of IE.

Re: 1Password X: A look at the future of 1Password in the browser

#52
post #35

Ugh. Agilebits left out until the very end that this is only for their hosted solution. No surprise but looks like standalone users are left out in the cold. Again. Much as I like and use 1Password every day, I really really do not like the fact that they moved to a hosted model.

Standalone user here since 1Password 2.0, using it both on iOS and OSX. I feel that it receives pretty frequent updates, and doesn't suffer from feature bloat. It even synchronizes great with Dropbox. What are people's gripes with AgileBits' support of the standalone version?

Most of these people are on the Windows version, I'm guessing. The 1Password Windows version is very neglected by AgilBits.

Re: 1Password X: A look at the future of 1Password in the browser

#53
post #50

Earlier quoted context omitted.

People see progress happening on something they don’t use (because standalone is basically feature-complete) and just want to gripe. I’ve been a stand-alone user for literally as long as I can remember and have never had a single issue with 1P.

Same. I have a tough time empathizing with people who expect free upgrades forever (especially if purchased many years prior) if they don’t articulate how those upgrades should be funded. I think it comes from a desktop software mentality, where things remained rather static relative to mobile’s rapid changes.

I don't expect free upgrades forever, but I am extremely disappointed that I will have migrate all my data to another product if they cease providing an offline version.

Re: 1Password X: A look at the future of 1Password in the browser

#54
post #52
post #35

Earlier quoted context omitted.

Standalone user here since 1Password 2.0, using it both on iOS and OSX. I feel that it receives pretty frequent updates, and doesn't suffer from feature bloat. It even synchronizes great with Dropbox. What are people's gripes with AgileBits' support of the standalone version?

Most of these people are on the Windows version, I'm guessing. The 1Password Windows version is very neglected by AgilBits.

Yeah, tell me about it.

Windows Teams support isn't out of beta yet and regularly has bugs.

Re: 1Password X: A look at the future of 1Password in the browser

#55

Earlier quoted context omitted.

Larger players being? I can only think of Lastpass when it comes to similar feature sets.

Apple's iCloud Keychain would qualify as a larger player.

... if you omit the lack of cross-platform support

Re: 1Password X: A look at the future of 1Password in the browser

#56
The cloud storage they are pushing everyone to annoys me. I feel like it's just a matter of time before i will switch to something else.

Also, does the average person really need a $3/month subscription even though they could just store the few KB/MB of data in their iCloud/Dropbox/whatever for free? No they don't, but they probably won't realise that anyway. To me it feels like they are trying to fool people.

A 5 year subscription would cost you $3 * 12 * 5= $180 Who would ever buy 1Password software & upgrades for $180 in 5 years?

Even though $3 a month feels like a small amount, it isn't.

Re: 1Password X: A look at the future of 1Password in the browser

#57
post #50

Earlier quoted context omitted.

People see progress happening on something they don’t use (because standalone is basically feature-complete) and just want to gripe. I’ve been a stand-alone user for literally as long as I can remember and have never had a single issue with 1P.

Same. I have a tough time empathizing with people who expect free upgrades forever (especially if purchased many years prior) if they don’t articulate how those upgrades should be funded. I think it comes from a desktop software mentality, where things remained rather static relative to mobile’s rapid changes.

1Password upgrades are not free, they were charging for major versions.

Re: 1Password X: A look at the future of 1Password in the browser

#58
post #53
post #50

Earlier quoted context omitted.

Same. I have a tough time empathizing with people who expect free upgrades forever (especially if purchased many years prior) if they don’t articulate how those upgrades should be funded. I think it comes from a desktop software mentality, where things remained rather static relative to mobile’s rapid changes.

I don't expect free upgrades forever, but I am extremely disappointed that I will have migrate all my data to another product if they cease providing an offline version.

What does “cease providing” mean? Don’t you have the software? Isn’t the whole point of a standalone program that once you have it, the company can just go bust?

Re: 1Password X: A look at the future of 1Password in the browser

#59
post #52

Earlier quoted context omitted.

Most of these people are on the Windows version, I'm guessing. The 1Password Windows version is very neglected by AgilBits.

Yeah, tell me about it. Windows Teams support isn't out of beta yet and regularly has bugs.

Teams support has been released long time ago: https://app-updates.agilebits.com/product_history/OPW6

And all our apps have bugs :)

Re: 1Password X: A look at the future of 1Password in the browser

#60

In-browser password managers are completely insecure by design. Any site can write whatever they want within the page, so it's easy to fake the prompt and steal the password. The only way to prevent this is if the password manager runs as a standalone application, so that the password is entered outside the browser. 1password has this, and the workflow is fine --- switching to the insecure one makes no sense.

How are sites going to trick the extension into believing the site is on a different domain?
Post reply on HN