Hacker News new | ask | show | jobs
by mbirth 20 days ago
It was better when it was still a native app and not this Electron nonsense.
2 comments

Quality in general seems to be going downhill, too.

Frequently the desktop app and the safari extension won't be in sync and missing a recently added password, or doesn't show up on my other devices hours later. I still have no idea how the extension vs desktop app actually work together, or if they do at all.

Sometimes 1password (safari extension) is "locked" - but the desktop app isn't locked? and No amount of clicking the little 1password icon, that's supposed to unlock it does anything. Just a completely no-op button. Quitting safari _and_ the desktop app seems to be what's required to fix it.

I've been thinking about just moving back to native macOS keychain, but I haven't bothered to check on linux+windows support.

Wait, it even needs an extension for Safari?

I'm using Strongbox (uses a KeePass-compatible database) which integrates into Apple's AutoFill API and appears automatically in all input fields - just like Keychain. No extension needed.

Maybe that’s why I get the 1Password UI _and_ the native password selection UI :-/
Since the extension works flawlessly in all other browsers I've chalked it up to Safari extensions being a pain.

But yes the Safari 1Password extension constantly shits The bed.

The publishing process for Safari extensions is painful, but otherwise it's not meaningfully different from Chromium extensions and there's no good reason for it to work worse in Safari.
Works a lot better on Linux and Windows since they dropped the native app though.