Live data from Hacker News

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

1password.community

571–580 of 685 posts

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

#571

Earlier quoted context omitted.

KeePass ( https://keepass.info/ ) with something like Nextcloud ( https://nextcloud.com/ ) or any other solution for syncing password databases across devices. Let's Encrypt SSL/TLS certificates are free, as is Apache/Nginx/Caddy to reverse proxy Nextcloud or any other solution (if a web based interface is needed). You might also need something like ngrok ( https://ngrok.com/ ) for publically accessing the instance i…

Recently set up something similar. DNS entry that resolves to a local ip, swag + letsencrypt reverse proxying to Nextcloud, all setup as containers and accessible anywhere over WireGuard. I'm pretty happy with it.

Here's a link to swag, if anyone hasn't heard of it before: https://github.com/linuxserver/docker-swag

It does seem like an interesting and useful project, though there are also other more popular alternatives like Caddy: https://caddyserver.com/ (even though their V2 not being backwards compatible was a tad annoying)

Oh, and some people also have pretty good luck with software like Traefik: https://traefik.io/traefik/

Apart from that, just wanted to say that WireGuard is absolutely lovely! Pretty simple to set up, works well and uses way less resources than something like OpenVPN.

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

#572

Scott Forstall, who led iOS until 2012 and oversaw the creation of the App Store, once said that he installed a new app every day to see what new ideas developers were coming up with. The mass migration of apps to the subscription model has killed this sort of exploration and discovery of new apps. As one example, I recently looked for a flight tracker and many wanted more than $30/yr for a tool that is (to me) an oc…

> I don't know the solution to adequately compensate developers for their work but I hope the subscription mania goes away.

There are ways, but nobody seems to bother to provide usage-based model. Similar to how cloud providers figured multiple usage plans. I have a feeling that many apps live off people paying but using service really low, so there is no incentive. What's stopping them to offer a different price for 1h - 5h monthly access? They could upgrade to a flat fee automatically if you start using their app every day.

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

#573
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.

Mostly the same; but the only thing I miss in Bitwarden compared to Lastpass is, if the vault is logged out, it doesn't prompt me to log in (to the vault) when it finds a login prompt for a site I have saved in the vault.

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

#576
post #159

Earlier quoted context omitted.

I'm somewhere in between. I also paid for a non subscription version and I also feel like I was forced to upgrade to the subscription. Sadly switching password managers, especially if you share with a family, is really painful. We now pay the subscription, a tad begrudgingly, but I have to admit 1Password overall does a great job.

Bitwarden can 1-click import 1Password vaults.

i did this last year and it wasn't very smooth to say the least. but now, i'm happy that i did :)

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

#577

1Password used to be native on the Mac, and now it's an Electron app. I'm not going to be using 1Password for this reason, and I encourage you to do the same. Subscription business models and non-native apps are hallmarks of rot by VCs. Dump them!

Many applications choosing to use eletron instead of building native apps is the hallmark of failure of platform developers.

I think there is an element of truth in that, especially on the Microsoft side.

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

#578

Earlier quoted context omitted.

> Ps. They can delete accounts too: https://support.1password.com/add-remove-family-members/ This makes losing local vault support an even bigger cause for alarm: > After you remove a family member’s account, they can’t sign in to 1Password, which means: > They lose all the items in their Private vault. Because the items weren’t shared with any other family members, no one will be able to access them. Imagine: the ac…

So don't use the family plan?

...which makes the subscription even more expensive.

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

#579

Earlier quoted context omitted.

> requiring two separate teams of platform developers for every feature we needed to implement So your margins are more important than your users’ native experiences. Got it.

I mean looking at this I can see why people came to the conclusion that this was primarily a move that VC funding caused even though AgileBits seem to vehemently deny this.

[deleted]

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

#580

Earlier quoted context omitted.

> Can you quantify the "needless development churn and hassle for both customers and our support team" in some way? Sure, happy to elaborate on that! Since we were rebuilding our app from the ground up, it was a significant slow-down on development to create a user interface for both Electron and SwiftUI, requiring two separate teams of platform developers for every feature we needed to implement. There were also con…

> requiring two separate teams of platform developers for every feature we needed to implement So your margins are more important than your users’ native experiences. Got it.

The primary issue with having two separate teams for the same platform was not money, it was time. To be clear: we wanted to build a native app in parallel with our cross-platform Electron solution, and we had the developers to do it. But unfortunately, having an additional team that needed to implement the UI for every single new feature was a significant slow-down, and we collectively realized that we could not meet our deadlines nor maintain this long term.

I'm sorry for not being more clear earlier as to why we couldn't support two separate teams for the same platform. Hopefully this clears up any confusion.

Post reply on HN