Live data from Hacker News

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

blog.agilebits.com

171–180 of 181 posts

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

#171
post #77

Earlier quoted context omitted.

I disagree. In fact, given the regular loss of online credentials, I think you are misguided in your faith in a hosted password solution. There are plenty of people that do not want to for very good reasons. As far as syncing using non-hosted 1Password, I use a combination of wifi sync (for mobile devices) and Resilio (in local sync only mode, no tracker, no cloud copy a la Dropbox) to sync. Works very nicely across…

Does that work well with multi device updates? What happens if two devices write to the database and then sync?

If you're using 1Password for Mac or iOS, then simultaneous writes are a non-issue. All sync types have conflict resolution implemented, where worst case scenario it'll put the overwritten password into a "Conflict" section at the bottom of the item.

With the other apps, you'd get nice behavior with 1Password.com because the first one to hit the server will have its record saved in the archive. That's one of the nice features of 1Password.com, getting to see item history. You don't need to worry about accidentally overwriting changes.

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

#172

Earlier quoted context omitted.

Yes it is because you're asking to get the upgrade for free. The version you paid $50 for has standalone support and will continue to work exactly as it did when you bought it. Maybe that's a caveat of the SaaS/hosted model. I don't see why they should be obligated to give anyone the version with new features for free, though.

This line of thought is bullshit. When you buy a product you also buy it because: 1. you expect long term support 2. you believe in the company's values and business model 3. you trust that company to keep protecting your interests There are many more factors going into a buying decision than "current implementation has features X or Y". Many people are upset with AgileBits because when they bought 1Password, they di…

We've provided 30+ updates to 1Password 4 for Windows:

https://app-updates.agilebits.com/product_history/OPW4

The first release was in June of 2014. The most recent update was September of this year.

Our July 2017 updates included support for our new Native Messaging based extension system so that the extension will continue to work for 1Password 4 for Windows users. This is all offered after we stopped selling 1Password 4 for Windows.

That's 3 years of updates. I'd say that's pretty long term.

So far as I'm aware, nothing is fundamentally broken in 1Password 4 for Windows. It behaves the same way now as it did before we stopped selling it and we've continued to produce fixes and improvements for it.

I'd be curious to understand what it is we did to earn your scorn here. It's almost like we kicked your dog or something. I'm all for constructive criticism, but when the criticism isn't actually in line with reality it starts to make me really doubt the authenticity of the feedback we're getting.

Kyle

AgileBits

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

#173

Earlier quoted context omitted.

That's how we designed the original 1Password data format (.agilekeychain). It certainly made syncing with Dropbox much simpler. It does have its drawbacks though. Once you have too many files (and make too many requests), both Dropbox and iCloud will start throttling you. It also might take a while to reload the data, even from the local disk. We had to add a cache file at some point.

I could see either local caching or (assuming the storage backend provides access to file metadata like date/time stamps that are internally consistent) I can think of several ways to have any instance of the application consolidate those small index files into larger ones such that you'd mostly need to load the consolidated file plus any individual entries modified since its timestamp. If those consolidated files we…

Yea, our current solution, as Roustem mentioned, sort of recreates the Dropbox app on Mac. We replicate the entire keychain file on the device, then perform syncing to keep both up to date.

Our newer OPVault format uses band files, each band file is named after the first character in each item's UUID, which means we have far fewer files than AgileKeychain (individual files for each item).

They both have their pitfalls, but initial sync with OPVault is infinitely faster as number of items increase. We did a ton of testing when we switched to the new Dropbox API and we had AgileKeychain's with thousands of items in them. They took awhile to sync. The same number of items in OPVault was nearly instant, at least with regard to the replication portion. Sync still took a little while due to the encryption and decryption that had to happen.

Sync with 3rd party sync services have always been quite difficult for us. Especially from a troubleshooting standpoint. It's hard to replicate certain issues because the data is incredibly sensitive for users so we can't "get" the data and instead have to try to duplicate the issue with limited information.

Every day is certainly a unique challenge :)

Kyle

AgileBits

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

#174
post #165

Reading some comments, I feel like I may be the only one here: happy, paying customer. Had the standalone Mac and iOS clients, migrated to the Family plan when it was announced. Couldn't be happier. I really, really am. Love the 1Password.com client which displays all it usefulness on a guest computer. Can't wait to try out 1Password X, but unfortunately I've switched to Firefox recently :(

Thanks for the kind words. Use the tool that works well for you. If that's us, great, if not, great. We can't fault anyone for having a different opinion, so long as that opinion is informed :)

Glad you're on our side though!

Kyle

AgileBits

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

#175
post #148

Hi, big fan of hosted 1Password here! I'm just curious, in the blog post you guys mentioned it autofills two-factor codes. I just tried using the extension on Postmark, and it didn't recognise the input field for my code. What heuristics are you using to determine the code input? As a front end developer myself, is there an autocomplete attribute for instance I could add that would help?

Is this postmarkapp.com you're having issues with or another URL?

I'd love to make sure I'm testing on the appropriate site and then I can get you some more information.

Kyle

AgileBits

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

#176
post #175
post #148

Hi, big fan of hosted 1Password here! I'm just curious, in the blog post you guys mentioned it autofills two-factor codes. I just tried using the extension on Postmark, and it didn't recognise the input field for my code. What heuristics are you using to determine the code input? As a front end developer myself, is there an autocomplete attribute for instance I could add that would help?

Is this postmarkapp.com you're having issues with or another URL? I'd love to make sure I'm testing on the appropriate site and then I can get you some more information. Kyle AgileBits

Hi Kyle,

Yes, postmarkapp.com

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

#177
post #176
post #175

Earlier quoted context omitted.

Is this postmarkapp.com you're having issues with or another URL? I'd love to make sure I'm testing on the appropriate site and then I can get you some more information. Kyle AgileBits

Hi Kyle, Yes, postmarkapp.com

I just setup an account and enabled 2FA for it.

What happens is the extension fills the username and password, then when you get to the next page, just click the extension icon and choose the item again. It'll fill the 2FA field.

Or you can use the keyboard shortcut and it'll do the same thing.

Does that work any better? As far as I am aware it won't automatically fill when the field is on a second page. The filling is one and done, it won't fill again on the next page without your instruction to do so.

Kyle

AgileBits

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

#178
post #77

Earlier quoted context omitted.

Does that work well with multi device updates? What happens if two devices write to the database and then sync?

If you're using 1Password for Mac or iOS, then simultaneous writes are a non-issue. All sync types have conflict resolution implemented, where worst case scenario it'll put the overwritten password into a "Conflict" section at the bottom of the item. With the other apps, you'd get nice behavior with 1Password.com because the first one to hit the server will have its record saved in the archive. That's one of the nice…

We’re not talking about syncing using the server but rather local file that is later synced via a file sharing service.

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

#179
post #128

Earlier quoted context omitted.

Is this an option for Chrome/Linux/ChromeOS users to provide a more streamlined first-use experience? The "a look at the future" and "this is just the beginning" wording in the announcement blog post implies that this is the direction that 1Password is taking as a product, and Chrome support is just the beginning. As a user who prefers a native implementation, uses local vaults, and uses Firefox, none of these advant…

I think the easiest way to look at this is as you said, another option for users. Some enterprises don't allow their users to install applications, but do allow extensions, so this opens up that possibility. It also brought 1Password support to two new platforms: Linux and Chrome OS. As for this being the future. Imagine a world where from a design perspective this sets the tone. Thus, the beginning of the future. It…

Thanks for the response. I appreciate the clarification on this being the beginning of the visual design for the future. As long as _solely_ browser extensions are not the future of 1Password, then it will continue to be my password manager of choice.

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

#180
post #172

Earlier quoted context omitted.

This line of thought is bullshit. When you buy a product you also buy it because: 1. you expect long term support 2. you believe in the company's values and business model 3. you trust that company to keep protecting your interests There are many more factors going into a buying decision than "current implementation has features X or Y". Many people are upset with AgileBits because when they bought 1Password, they di…

We've provided 30+ updates to 1Password 4 for Windows: https://app-updates.agilebits.com/product_history/OPW4 The first release was in June of 2014. The most recent update was September of this year. Our July 2017 updates included support for our new Native Messaging based extension system so that the extension will continue to work for 1Password 4 for Windows users. This is all offered after we stopped selling 1Pass…

It's unwarranted. I'm still using 1Password 4 on all my Windows machines and it works just fine. I'm waiting for standalone support in 1Password 7 (just like most of the people complaining) but I don't feel like I'm entitled to the latest version for free. That's just nonsense. You guys have jobs and need to pay for staff and development time. I would gladly pay more for the standalone version that I am now but getting a major upgrade like that for the same price is more than fair. This guy's just being ridiculous.
Post reply on HN