We also allow export in something called 1PIF. It's a JSON format export of your data. It doesn't currently handle everything super smoothly, notably Documents which are new.

We'll have another solution in the not too distant future that should cover things and be a documented format that anyone with the know how could use.

Also important to note, that if your account ever lapses due to lack of payment. The account is still read-only. You can export your data if you wish even when the account is read-only. We do not lock you out of your data, we just prevent normal use of the application (browser extension, editing items, adding new items, etc). But the data you've already entered is entirely accessible if you want to copy/paste or export.

Kyle

AgileBits

Password Store (AKA 'pass') stores each password as a GPG-encrypted text file, so with gpg, $EDITOR, and cp/mv you have full control over your password data at all times without pass even having to get involved.

It’s nice to see a team of marketers working so hard to convince the masses. Kudos.

Yes, you can export it as a CSV file. They even warn you that it’s not secure.

> They even warn you that it’s not secure.

I don't think anyone who uses a password manager is exporting to CSV for security purposes.

I was trying to illustrate that not only can you extract data in an open format, they also are responsible enough to warn end users that the data is no longer encrypted. This isn’t for the benefit of your typical HN reader.

For now...

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 switched from 1Password to LastPass last year and it was a smooth transition. If they’d had a Linux version I’d still be a customer right now.

They now have a chrome extension that supports Linux[1] and a command line app.[2]

[1] https://support.1password.com/getting-started-1password-x/

[2] https://support.1password.com/command-line-getting-started/

We evaluated Lastpass about a year ago and the UI was borderline unusable. Doesn't matter so much for technical teams, but it does in broader use cases.

What did you settle on? It’s basically just a browser extension.

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.

"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.

Yes, you're right, an already-dead company can't die a second time in this highly-hypothethical scenario. They're still dead.

For ever.