passff VS hashpass

Also, there's a firefox extension https://addons.mozilla.org/en-US/firefox/addon/passff/ (on github: https://github.com/passff/passff)

It requires the user to run a daemon that reads ~/.passwordstore passwords and feed it to the extension https://github.com/passff/passff-host - but the design is pretty transparent to inspection if you're inclined to check

The reason I currently use pass is that it has Firefox integration through PassFF: https://github.com/passff/passff

It's a good idea that I've considered. However, I didn't anticipate the need for this when I originally designed Hashpass in 2014, and adding it now would be a breaking change.

I am still considering it, but there would need to be a very slow, very careful rollout plan. Probably some transition period where users can opt into the new scheme, and then eventually make the new scheme the default but still support the old scheme, and finally remove the old scheme to make things simple again.

Since this is a Chrome extension which collects no information from users, I have no way of contacting users about this. So I would need to wait long enough that users discover it themselves in the UI. All told, I'd guess it would take about a year for the full migration.

Still, it's not unlike me to go to great lengths to remove minor annoyances like this.

Anyone is welcome to discuss things like this with me via GitHub issues: https://github.com/stepchowfun/hashpass