1PUX - need some help

ethomp

I'm happy to support 1PUX, but it will take some work on 1Password's part to eliminate the issues I mentioned above. I won't publish a 1PUX generator that creates a problematic import for a 1Password customer.

I've already reworked the code to be able to produce either format. But as I mentioned, I'm at a dead halt at this point.

Straying from the topic of my post... I'm not sure I'd go so far as to say there's any customer lock-in. 1PUX is very easy to read, parse, and is complete enough, so it's not a substantial hurdle for anyone to consume it, esp. other password managers. Customer demand will cause other password manager's to implement a 1PUX importer. A simple JSON file that is readily readable by anyone is not quite the same as the highly proprietary Microsoft formats of a few decades ago. Let's also keep in mind it was the open source threat that caused Microsoft (and Adobe) to move towards supporting open formats, and opening their formats; they had no choice ultimately (others had sufficiently revise engineered the format). And they had no choice in continuing to support their propriety formats (they could not just stop being able to read the billions of extant documents).

1Password's 1PIF export has been one of the best, and most comprehensive in the industry. 1PUX is better. And AgileBits / 1Password has historically been exceptionally responsive to my feedback and fixing issues with their imports. So, if they are still interested in having the converter available, and have the bandwidth to resolve the issues, I'm sure they will soon enough. Their code base is probably several orders of magnitude larger and more complex than it was a decade ago. I can appreciate that they may not be able to get to everything.