Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Getting 1Password 7 ready for the Mac App Store

blog.agilebits.com

Post reply on HN
Print view View original

311–320 of 484 posts

Re: Getting 1Password 7 ready for the Mac App Store

#311

Post by facetube »

_b8r0 wrote: post #305
facetube wrote: post #280

Earlier quoted context omitted.

Removing the ability to get your own passwords out of your password management utility that you paid for would be corporate suicide.

Crippling it, not so much. I moved away from 1password at the time of the subscription palaver. I managed to move everything to Keepass but each entry has it's own folder. I don't blame 1Password for the state of my Keepass db (although they pretty much forced my hand) but the closed nature of 1Password does bite you in the arse when you decide to leave.

I keep meaning to write some Applescript and/or browser glue for pass(1). Uses GPG, checks into Git, and even has an iOS app.

Re: Getting 1Password 7 ready for the Mac App Store

#313

Post by coldtea »

facetube wrote: post #280
Nullabillity wrote: post #256

Earlier quoted context omitted.

For now...

Removing the ability to get your own passwords out of your password management utility that you paid for would be corporate suicide.

"Corporate suicide"? 99% of the users wont even notice the feature existed...

Re: Getting 1Password 7 ready for the Mac App Store

#314

Post by saagarjha »

coldtea wrote: post #313
facetube wrote: post #280

Earlier quoted context omitted.

Removing the ability to get your own passwords out of your password management utility that you paid for would be corporate suicide.

"Corporate suicide"? 99% of the users wont even notice the feature existed...

They will if you go out of business or decide to spin off the product.

Re: Getting 1Password 7 ready for the Mac App Store

#315

Post by beepbeepbeep1 »

cdumler wrote: post #123

So, I'll join the chorus here by saying that I've picked up the subscription fee. I've been using their software daily for over three years. During that time, they have consistently improved their product and have been open about issues (as far as I am concerned). I was a little irked when I saw the subscription model. I was like, "hey, I paid for this." So, I looked up how much I paid in licenses by looking them up.…

I am a long time 1Password user, purchased Mac licenses, IOS and Android over the years.

I was annoyed when it changed to being subscription based, the price wasn't an issue I think for the value it gives the price is fair, 1Password is the only thing now keeping me on a Mac.

The issue i had with it is you don't own the software and when my credit card expired and i forgot to update it losing access to passwords even if temporarily until updating the card details left a bad taste and showed the downside of being subscription only.

It's been on my list to move away ever since. 12 months on I've still not done it, there's lot's of alternatives but 1Password have the UX and functionality just right however i know i should move as i now don't own my passwords.

Re: Getting 1Password 7 ready for the Mac App Store

#316

Post by saagarjha »

scarface74 wrote: post #215
archagon wrote: post #182

Earlier quoted context omitted.

As time goes on, I've gotten less and less comfortable using proprietary software for critical tasks. If 1Password were open source, I'd actually be pretty happy to subscribe. But as it stands, I have no faith that the product won't change out from under me in the future, whether due to a pivot, an acquisition, or some other reason. The incentives align in favor of the business, not the customer. IMHO, subscriptions…

So if the app were open source and the maintainers decided to abandon it, are you going to download the code and keep it updated? If it is forked are you going to trust the new maintainers? Are you going to audit the source code?

Of course, the answer to all your questions is "not necessarily". Sure, it's totally possible for people to not audit the code, or let it be abandoned–but open source makes this probability much lower, whereas with closed-source software you have no choice in the matter at all.

Re: Getting 1Password 7 ready for the Mac App Store

#317

Post by coldtea »

saagarjha wrote: post #314
coldtea wrote: post #313

Earlier quoted context omitted.

"Corporate suicide"? 99% of the users wont even notice the feature existed...

They will if you go out of business or decide to spin off the product.

"Corporate suicide" implies that it would be a problem for the company.

Users noticing it after the company is already "going out of business" does not qualify as such.

Re: Getting 1Password 7 ready for the Mac App Store

#318

Post by saagarjha »

dingaling wrote: post #288
cdumler wrote: post #123

So, I'll join the chorus here by saying that I've picked up the subscription fee. I've been using their software daily for over three years. During that time, they have consistently improved their product and have been open about issues (as far as I am concerned). I was a little irked when I saw the subscription model. I was like, "hey, I paid for this." So, I looked up how much I paid in licenses by looking them up.…

Well this one tool is 'only' $60 per year[0]. But what if your compiler moved to subscription, and your text editor and your e-mail client and ... It's the thousand-cuts problem. And once you start on that path you can't go back, or else the tool stops working. [0] which is a substantial chunk of a day's after-tax pay for many people in the UK, for example. 1/400th of their salary for a password database.

> And once you start on that path you can't go back, or else the tool stops working.

How would you feel about a subscription service that guaranteed updates? Essentially, upgrade pricing, but charged every month.

Re: Getting 1Password 7 ready for the Mac App Store

#319

Post by bigiain »

chrischen wrote: post #233
CountSessine wrote: post #232

Earlier quoted context omitted.

You need software companies to provide you with security updates for their products. Insisting that you won’t pay for security updates without new features or that security updates should be offered gratis won’t lead to quality software - it just leads to feature bloat. Attaching a separate price to security updates aligns your needs with a software company’s incentives. Why is that a bad thing in your view?

If you are paying for a subscription there isn’t necessarily an incentive to provide security updates even more, since they have the functionality of your app hostage if you decide to cancel and the automatic monthly billing has no ties to the quantity or wuality of updates they push out. That being said, security updates shouldbe part of the price you already paid, since a security flaw is a flaw in their original s…

> If you are paying for a subscription there isn’t necessarily an incentive to provide security updates even more

I'm not so sure - it'd be much easier to write the email saying "Sorry, we screwed up and got a critical security but wrong, but here's an update that fixes it." if a significant portion of your users are paying a subscription - compared to writing that same email just as marketing are preparing to try and convince everybody to pay for a new upgrade...

> That being said, security updates should be part of the price you already paid, since a security flaw is a flaw in their original software.

If that was how everything worked - our industry would be _very_ different. If everybody who ever charge money fo a piece of software was on the hook forever for all flaws it might have, you'd only ever be able to buy software from Apple or Oracle or Microsoft - there would need to be almost as any lawyers as developers in any software company.

I understand your idea - but it's the same idea as people who call up my work saying "Hey, the app you made us doesn't work any more, you need to fix it!" and everybody here is like "Who the hell are _they???_ Never even heard of them." and it turns out its a 32 bit iOS app that they paid for in 2013 and we haven't heard from since (and there's only 3 people left in the whole company who were around in '13, and none of them are iOS devs). We do not fix that for them as "part of the price they paid".

Re: Getting 1Password 7 ready for the Mac App Store

#320

Post by Groxx »

akerl_ wrote: post #42
cygned wrote: post #26

I really like 1Password, it has been my daily driver for years. The creators gifted me versions for macOS and iOS years ago, so I never had to pay for it - which I would have done happily and, in fact, just recently did. But the push to the cloud versions gives me headache. I don’t want to sync using their cloud - I actually sync using a WiFi server. While it’s (still) possible to obtain the standalone versions, it’s…

It's worth noting (and not super obvious because of their marketing) that "getting a subscription" and "using their cloud sync" are not a mutual requirement. You can pay via subscription and continue using local/Dropbox/etc vaults. This part was super confusing to me until I dug deeper when a friend upgraded. So the primary impact of switching from standalone license to subscription, if you're planning on using 1Pass…

So I asked on Twitter, got an answer: https://twitter.com/1Password/status/998337650380738560

Assuming that's correct (since the blog post still strikes me as vague), the answer is clear in their reply: memberships are exclusively cloud, standalone licenses are exclusively local backups / sync.

Post reply on HN