Jeffrey Goldberg@khad @jpgoldberg the tech is pretty neat, but the most exciting part for me is how we’re starting to put the Emergency Kit behind us. We’re decoupling onboarding from recovery with better (and safer) systems for both.
Mitch Cohen
@mitchchn
- 417 Followers
- 50 Following
- 131 Posts
Principal PM @1Password. Here for the takes. Tech, infosec, gaming, coffee, and whatever else we’re geeking out about today.
@mitchchn @khad this is really good news. I was always unhappy with the burden that the Secret Key put on users, and the nasty trade-offs we had to make. For a very long time, I had thought those trade-offs were necessary, but I saw a glimmer of hope emerging from the tech that was being developed for new device enrollment.
One of our goals this year is to make 1Password less frustrating and more forgiving, while still upholding our stringent security model. We're taking a step in that direction today with 1Password Recovery Codes:
https://blog.1password.com/introducing-1password-recovery-codes/
https://blog.1password.com/introducing-1password-recovery-codes/
Andrew GermanDid you know that now in beta, #1Password 8 can display a Wi-Fi QR code for your Wireless Router items?
Pin it to Home for quick access when a friend comes by and needs Wi-Fi access.
Really happy to see what looks like autofill provider support for OTP codes in iOS 18! Like I said last week, APIs get better every year and that’s always something to look forward to.
Happy WWDC keynote day! Here's what I'm looking forward to the most this week from a work perspective:
1. On-device AI/LLMs. Private, local compute will be huge for privacy-first software like 1Password which cannot responsibly use services like ChatGPT.
2. Improvements to Safari, WebKit, extensions, and AutoFill APIs.
3. Signs of Apple's continued investment into credential management, especially passkeys. (Yes, even if they release their own app!)
Apart from the mega-threads I *also* wrote a 9-page RFD this week and my fingers are about to call it quits.
Look if Apple makes an app we'll just pivot and make a Prefs Pane. (Can you still add these in System Settings?)
The difference between Safari and other browsers comes down to a few fundamental issues:
1) Immature implementation of the Web Extension API
2) Extra indirection and instability in the XPC layer
3) Severe restrictions on extension lifecycles and persistence, especially on iOS.
All of these contribute to an experience in Safari that's just not as fast, reliable, or feature complete when compared to the same browser extensions in Chrome and Firefox.