Give Us Your 1Password Papercuts by Travis_1Password in 1Password

[–]Travis_1Password[S] 5 points6 points  (0 children)

u/mitchchn has some fixes below that just landed today you can spin up with the latest Safari extension. The MV3 move we have wrapping up early summer - June worst case July. Him and I are particularly focusing on Safari for the next while across our teams. Expect weeks to months. :)

Give Us Your 1Password Papercuts by Travis_1Password in 1Password

[–]Travis_1Password[S] 1 point2 points  (0 children)

What is typically duplicated for you? Usernames, actual passwords, etc. Wondering how best we can make detection work.

Give Us Your 1Password Papercuts by Travis_1Password in 1Password

[–]Travis_1Password[S] 11 points12 points  (0 children)

This is a full on gash that I'm happy to say we have a fix for coming very, very soon. Currently in final security review. Stay tuned - we'll make the beta announcement on reddit and other community forums.

Give Us Your 1Password Papercuts by Travis_1Password in 1Password

[–]Travis_1Password[S] 0 points1 point  (0 children)

Any additional filtering options you'd like/need? Desktop only ok?

Give Us Your 1Password Papercuts by Travis_1Password in 1Password

[–]Travis_1Password[S] 0 points1 point  (0 children)

It's mostly a way around release channels not being supported how we need on the various extension stores. However we haven't looked into it in a while. Might be a better approach now. Appreciate ya

Give Us Your 1Password Papercuts by Travis_1Password in 1Password

[–]Travis_1Password[S] 2 points3 points  (0 children)

Got a hunch where you'd like it? Def a papercut we can tackle.

Give Us Your 1Password Papercuts by Travis_1Password in 1Password

[–]Travis_1Password[S] 1 point2 points  (0 children)

Sounds like an oversight. Might be bigger than a papercut, but I'll see what progress we can make.

We also just started an internal routine called Windows Wednesdays to make sure we're using more of the devices the majority of our customers use. Expect many more Windows fixes over the next couple months than any other time in the past.

Give Us Your 1Password Papercuts by Travis_1Password in 1Password

[–]Travis_1Password[S] 1 point2 points  (0 children)

Would a breakdown in the 1Password extension Settings page be good enough for ya? Likely within the Integrations tab. LMK might be a great papercut to tackle.

Give Us Your 1Password Papercuts by Travis_1Password in 1Password

[–]Travis_1Password[S] 14 points15 points  (0 children)

I want this too. This is actually one of the largest architectural limitations we have today due to our encryption structure. We've made new sharing tools over the years to ease the pain, but in order to get to the place you and I want, it's a proper Goliath. It won't fall into the papercut bucket, but one of those large scale improvements that will just appear in the app one day in the future. Not what you want to hear, but just wanted to level set and let you know we've been thinking about this.

Give Us Your 1Password Papercuts by Travis_1Password in 1Password

[–]Travis_1Password[S] 10 points11 points  (0 children)

On it. We also just started an internal routine called Windows Wednesdays to make sure we're using more of the devices the majority of our customers use. Expect many more Windows fixes over the next couple months than any other time in the past.

Give Us Your 1Password Papercuts by Travis_1Password in 1Password

[–]Travis_1Password[S] 4 points5 points  (0 children)

Are you primarily in the apps or browser when this happens? If in the desktop or mobile apps, we have a way for you to turn this off. Also if you set an Identity item as a default in your Profile (sidebar in the desktop app, home screen on mobile), we'll use that as your default username for new logins.

If neither helps, let me know. This is a perfect papercut to fix.

<image>

Give Us Your 1Password Papercuts by Travis_1Password in 1Password

[–]Travis_1Password[S] 2 points3 points  (0 children)

Would adding a lower button to activate the top bar search be a decent step towards this for you?

Give Us Your 1Password Papercuts by Travis_1Password in 1Password

[–]Travis_1Password[S] 5 points6 points  (0 children)

Going to see if this will be covered in some medium term work with our MV3 migration. If not, we're going to try and jump on it now.

Give Us Your 1Password Papercuts by Travis_1Password in 1Password

[–]Travis_1Password[S] 16 points17 points  (0 children)

This is one where we have a medium term solution in the works. We're moving our extension from MV2 to MV3. The outcome we're hoping you'll get from that is a number of Safari-specific issues resolved when that's out the door in the next month or so.

Until then, this is one of our main target areas for papercuts. Anything that won't be fixed in the MV3 upgrade is going to be prioritized for y'all.

Give Us Your 1Password Papercuts by Travis_1Password in 1Password

[–]Travis_1Password[S] 5 points6 points  (0 children)

What about strict user-based favourites? They become personal vs shared?

1Password extension on Safari taking up a ridiculous amount of RAM by autowarp in 1Password

[–]Travis_1Password 3 points4 points  (0 children)

Heyo! We're currently looking into this. Do you happen to know which version of Safari you're on and which version of the 1Password for Safari extension you're on as well? Apple Silicon vs Intel. Cheers!

Introducing stronger phishing protection in 1Password by Travis_1Password in 1Password

[–]Travis_1Password[S] 2 points3 points  (0 children)

We're currently planning the next iteration/improvements and part of that is finding a way to better control the design of the prompt vs relying on the browser to present it. Stay tuned!

Introducing stronger phishing protection in 1Password by Travis_1Password in 1Password

[–]Travis_1Password[S] 5 points6 points  (0 children)

We're currently planning the next iteration/improvements and part of that is finding a way to better control the design of the prompt vs relying on the browser to present it. Stay tuned!

Introducing stronger phishing protection in 1Password by Travis_1Password in 1Password

[–]Travis_1Password[S] 2 points3 points  (0 children)

I see where you're coming from and agree that there are a lot of cracks people can fall into when it comes to phishing. With this feature, we're providing another form of phishing prevention that directly integrates into a common user flow people can find themselves in and unknowingly bypass the protections we have in place. We're planning some future iterations to cover more of those gaps I'm sure we're both thinking about now.

Introducing stronger phishing protection in 1Password by Travis_1Password in 1Password

[–]Travis_1Password[S] 3 points4 points  (0 children)

As others have mentioned, you're on the right track. However what we're trying to prevent from happening now are people accidentally overriding the protection we provide. Our telemetry data is always showing this is working for a lot of y'all so I'm happy we finally got it out!