3 ms·

As a long-time happy customer of 1Password I have quite a bit of a problem with them pushing their new hosted product. If you want to offer that as an alternati

As a long-time happy customer of 1Password I have quite a bit of a problem with them pushing their new hosted product. If you want to offer that as an alternative by all means do but don't make it the only long-term option. I would have no problem with paying a monthly fee or paying for every major version (as I have done in the past when applicable) but I think for this use case being able to choose where to host your data - or to not host it at all - is much more justified than it arguably already is with SaaS products in other areas. 1Password certainly know their cryptography but do they also know how to secure servers and networks? I must say I trust Apple or Dropbox a lot more on this matter. In general, the tendency to build and provide every aspect of a service is bothering me. Otherwise known as the Not-invented-here syndrome, which we largely thought to have overcome with the Internet and the age of hosted software, particularly Web 2.0 kind of SaaS offerings, this development amounts to tight coupling and agglomeration of features that are secondary to the benefit of the actual product at hand: Why does every application apparently have to provide these features: - file hosting and serving - calendaring and event notification - messaging - PDF export - and most famously: Email ("Every program attempts to expand until it can read mail.") Why is it so hard to provide just the core features of your product and use other products and services by providers specialising in those to implement ancillary features required for building a product or service? We still have to go a long way in terms of connecting with and building upon other services, one particularly preposterous example of which I recently encountered with a supply chain management process where a company used two perfectly fine - if slightly aging - applications to keep track of different but related data sets. In order to exchange data between these applications a PDF containing the relevant data is exported from application A, sent via email and finally manually entered into application B again. The waste created by processes like this never ceases to amaze me.

AGKyle 9y ago
Disclosure: I work for AgileBits, makers of 1Password I hear you on this, but having years of experience using other sync platforms and having to work within their unique solutions has proven to us that to have the best experience it's best to have a solution designed for your application. Every sync solution has their own gotchas and dealing with it in 1Password is incredibly tricky. I get the feeling that many people think sync is this easy thing that takes a week and you're done. We are still fixing bugs in our various sync solutions and they've been released to users for years. Want an example of how each solution is weird for us? Lets take Master Password changes as an example. If you want grittier details, our blog post on the topic here gives a really nice overview: https://blog.agilebits.com/2015/04/28/how-1password-syncs-changes-to-your-master-password/ https://blog.agilebits.com/2015/04/28/how-1password-syncs-ch... But because of how Dropbox works, we have to: 1. Change the Master Password on one device, let it sync 2. Unlock the other device, let it sync, lock, then unlock again With iCloud, 1. Is the same as above: Change the Master Password on one device, let it sync 2. Unlock the other device with the new Master Password. Very different behaviors and that's just two sync solutions. Adding additional sync solutions would result in similar oddities between them. This type of inconsistent behavior is very difficult to explain to users when things go wrong. They don't want to know these details. They pay us to not know these details. We can't provide a consistent experience with other sync solutions. But we can if we provide our own. Things work the way users expect because we can design the solution to work like that because we control the entire solution. This is just coming from a developer who has been doing support with AgileBits for nearly 6 years. I was the last line of defense between our customers and our users when they wrote in. I seen all the messy stuff that users can find their ways into when things do not work how they expect. I happily welcome our new solution because we can design 1Password in a way that makes sense and is actually incredibly secure as well. That said, if you don't like our hosted solution... have you tried it? If not well... don't knock something you haven't tried. But if you have tried it and don't like it I'd love to hear your feedback. Seriously. I welcome your feedback if you have any after trying it. We love talking with our users and finding ways to make 1Password better. We wouldn't be where we are without our users. Anyway, if you don't like our hosted solution we offer standalone licenses and version 7 for Mac and version 7 for Windows will both be available as standalone licensed versions with standalone vaults just like you're used to. Nothing changes for users like yourself if they wish to continue using that variation of options. Kyle AgileBits

AGKyle 9y ago

Disclosure: I work for AgileBits, makers of 1Password I hear you on this, but having years of experience using other sync platforms and having to work within their unique solutions has proven to us that to have the best experience it's best to have a solution designed for your application. Every sync solution has their own gotchas and dealing with it in 1Password is incredibly tricky. I get the feeling that many people think sync is this easy thing that takes a week and you're done. We are still fixing bugs in our various sync solutions and they've been released to users for years. Want an example of how each solution is weird for us? Lets take Master Password changes as an example. If you want grittier details, our blog post on the topic here gives a really nice overview: https://blog.agilebits.com/2015/04/28/how-1password-syncs-changes-to-your-master-password/ https://blog.agilebits.com/2015/04/28/how-1password-syncs-ch... But because of how Dropbox works, we have to: 1. Change the Master Password on one device, let it sync 2. Unlock the other device, let it sync, lock, then unlock again With iCloud, 1. Is the same as above: Change the Master Password on one device, let it sync 2. Unlock the other device with the new Master Password. Very different behaviors and that's just two sync solutions. Adding additional sync solutions would result in similar oddities between them. This type of inconsistent behavior is very difficult to explain to users when things go wrong. They don't want to know these details. They pay us to not know these details. We can't provide a consistent experience with other sync solutions. But we can if we provide our own. Things work the way users expect because we can design the solution to work like that because we control the entire solution. This is just coming from a developer who has been doing support with AgileBits for nearly 6 years. I was the last line of defense between our customers and our users when they wrote in. I seen all the messy stuff that users can find their ways into when things do not work how they expect. I happily welcome our new solution because we can design 1Password in a way that makes sense and is actually incredibly secure as well. That said, if you don't like our hosted solution... have you tried it? If not well... don't knock something you haven't tried. But if you have tried it and don't like it I'd love to hear your feedback. Seriously. I welcome your feedback if you have any after trying it. We love talking with our users and finding ways to make 1Password better. We wouldn't be where we are without our users. Anyway, if you don't like our hosted solution we offer standalone licenses and version 7 for Mac and version 7 for Windows will both be available as standalone licensed versions with standalone vaults just like you're used to. Nothing changes for users like yourself if they wish to continue using that variation of options. Kyle AgileBits