Live data from Hacker News

1Password 8 will be subscription only and won’t support local vaults

1password.community

311–320 of 685 posts

Re: 1Password 8 will be subscription only and won’t support local vaults

#311

Earlier quoted context omitted.

> However how many subscriptions are we going to have to end up with? I started making a list to answer that question myself. So far, I'm up to SEVENTEEN, but I'm sure I'm still overlooking a few.

I remember dropping cable cos of the costs and now we all have 2-5 streaming services we pay for...?

Even if pick-and-choose subscriptions weren't cheaper than cable (which they are, for me so far at least), I'd gladly pay up to 2x the cost of Comcast service just to avoid subsidizing Comcast's evil monopoly, and how Comcast is intentionally keeping much of the US from having real, modern internet service (read: fiber with symmetric speeds, instead of their bullshit where they pretend a 1000Mbps down/20Mbps up link is lightning-fast and don't even TELL customers what the upstream speed is).

Re: 1Password 8 will be subscription only and won’t support local vaults

#312
post #51

The writing was on the wall when they took VC money[1]. Anyone has a good guide to move to Bitwarden/Lastpass? [1] https://techcrunch.com/2019/11/14/fourteen-years-after-launc...

Hi. I'm a feature developer for 1Password, and I want to clarify a few things. First of all, our decision to built the macOS app in Electron was absolutely not driven by VC money. For the past few years, we've been working on consolidating 1Password's business logic into a single Rust-powered core that could be shared across all our apps. This has many advantages: feature consistency across platforms, faster developm…

Question: you built it in Rust for performance reasons, right? Wouldn't Electron take it away?

Re: 1Password 8 will be subscription only and won’t support local vaults

#313
post #57

Earlier quoted context omitted.

Bitwarden's UX is so frustrating. The Firefox extension has no memory to it. For example, if you're logging into your credit card provider from Mint.com, you have to search your card, copy the username. when you paste the result on Mint, you lose the window, and you have to re-search for your card to get the password. Very frustrating.

This is probably an edge case where the fields in the browser cannot be identified by their ids/classname. In this kinds of a scenario, you can set extra fields (and their corresponding values) in Bitwarden after inspecting the field elements in Dev tools.

No he means that Bitwarden's extension does not remember state. When you go back and forth between the form and opening the extension window, you always start at the default page. It does not remember you had an item open before. This happens with your credit card for instance which is typically not linked to a particular url.

Re: 1Password 8 will be subscription only and won’t support local vaults

#314

Earlier quoted context omitted.

I am cognizant of this risk, and assume it, because security is always a spectrum between Secure and Convenient. If I had to pull out my phone every time I wanted to use 2FA, I for sure would not be so liberal to turn it on for all the "low value" properties the way I do now I have never even _heard_ of someone having their 1P master password compromised and the vault(s) exfiltrated (although I grant you it could be…

> I am cognizant of this risk, and assume it, because security is always a spectrum between Secure and Convenient. Absolutely. But also, in such setup, the security benefit of 2FA/OTP codes are negligible at best since there are no conditions under which only one factor could be compromised without also having the other factor leaked (assuming you're using unique passwords for each identity, which is the entire point…

> But also, in such setup, the security benefit of 2FA/OTP codes are negligible at best since there are no conditions under which only one factor could be compromised without also having the other factor leaked (assuming you're using unique passwords for each identity, which is the entire point of a password manager).

Phishing and good ole fashioned human error are two methods by which a password can be leaked without exposing the 2FA token.

Re: 1Password 8 will be subscription only and won’t support local vaults

#315

Earlier quoted context omitted.

> Especially when the product fits into $0 software so $4.99 is infinitely higher than $0. What is the competition that costs $0? Bitwarden is $3.33/mo for equivalent functionality to the $4.99/mo plan from 1Password.

A more apt comparison is $0 for Bitwarden vs $4.99 for 1Password. Most people don't need the 'extra' functionality.

That comparison would be $2.99 for 1Password. It is the family plan that costs $4.99, and Bitwarden's family plan is not $0. It also assumes you don't want the features in the paid version of Bitwarden, so it's not an apples-to-apples comparison. 1Password doesn't offer a free reduced-feature version, true.

Re: 1Password 8 will be subscription only and won’t support local vaults

#316

Earlier quoted context omitted.

Subscription models make sense for something that needs to stay evergreen. Why does a password manager need a subscription? My password should never touch a 3rd party’s server, I don’t need extra features, I don’t need a login, I don’t need long-term or even short-term support. What ongoing development does a password manager have? Is it that buggy from the get-go to need constant updates?

> What ongoing development does a password manager have? I shutter to think about just trying to keep the status quo across all those platforms, devices, browser extensions. How often do we have new versions of iOS or macOS? What about Windows, Android, Linux, Chrome OS? I can think of a TON of work without adding a single feature.

Major releases of MacOS and iOS happen once a year. And most of the time they don’t break existing applications (iOS 12 notwithstanding). Almost everything from early iPhone OS to 12, and from 12 onwards worked ok, even with major resolution changes.

And the fact that we need to constantly change stuff just for the sake of change is the problem.

To add to this: I’m perfectly happy to pay a premium price for software when I need a new version. I did this with Photoshop for years, $399 per copy was perfectly fine for me because I spent that money every 3 or 4 years.

Re: 1Password 8 will be subscription only and won’t support local vaults

#317
post #3

I haven't had a single bad experience with Bitwarden. I even pay for it now and still run it locally just to support them. Highly recommended if you don't want to be forced into 1Password's service.

+1 on Bitwarden. UX is perhaps not perfect. I've had some IOS sync issues but that seems to have gotten much better. Use it in Firefox every day and have no complaints.

I convinced my wife to pick it up and we now share a bunch of stuff and she loves it. And she's low tolerance for UX issues.

Re: 1Password 8 will be subscription only and won’t support local vaults

#318

Earlier quoted context omitted.

I am cognizant of this risk, and assume it, because security is always a spectrum between Secure and Convenient. If I had to pull out my phone every time I wanted to use 2FA, I for sure would not be so liberal to turn it on for all the "low value" properties the way I do now I have never even _heard_ of someone having their 1P master password compromised and the vault(s) exfiltrated (although I grant you it could be…

> I am cognizant of this risk, and assume it, because security is always a spectrum between Secure and Convenient. Absolutely. But also, in such setup, the security benefit of 2FA/OTP codes are negligible at best since there are no conditions under which only one factor could be compromised without also having the other factor leaked (assuming you're using unique passwords for each identity, which is the entire point…

> there are no conditions under which only one factor could be compromised without also having the other factor leaked

Man in the middle attack, Phishing attack, Over the shoulder attack, Brute force attack, Keylogger, Http (not https) traffic sniffing, 'Breech' of the site and realisation they host their passwords in clear text on an unsecured db online.

Then there is human error; typing password into wrong site, giving your password to the tech support cold caller, telling someone your supersecret password ...

Re: 1Password 8 will be subscription only and won’t support local vaults

#320

Earlier quoted context omitted.

Hi. I'm a feature developer for 1Password, and I want to clarify a few things. First of all, our decision to built the macOS app in Electron was absolutely not driven by VC money. For the past few years, we've been working on consolidating 1Password's business logic into a single Rust-powered core that could be shared across all our apps. This has many advantages: feature consistency across platforms, faster developm…

>Electron suited us perfectly, since we could write our UI code once and make it consistent across Linux, Windows, and Mac. This is the source of your mistake. Users don't desire to have the same UI across different OS environments, it's only an app's developers that care about that. Cross-platform UIs are inarguably a worse user experience than UIs tailored to the conventions and designs of each OS. A Mac app that d…

> Users don't desire to have the same UI across different OS environments, it's only an app's developers that care about that.

I guess we'll have to agree to disagree on that. I personally enjoy having consistent user interfaces across the apps that I use, and there are many other people that would say the same, so I would avoid making broad assumptions. From our perspective, consistent user interfaces are a win-win for both the development team and the majority of end users. That being said, I'll take your feedback into account.

Post reply on HN