Subdomain matching misses the mark
I've been waiting for a subdomain release for 1password for a long time and was excited when I discovered something had been shipped recently. So I'm a little sad to be writing this post.
Here are the problems I have with the new feature which is at least something but falls a long way short of what I believe most users who need it are asking for.
You have to set this on a per site, per password basis creating a large management task for anyone who uses 1password for a long period of time. I have been using 1password for several years and this alone makes the feature far less valuable than it would have been. I can't set this as a default behaviour and let me handle the problems that might come with that.
It only allows you to switch to exact matching for the domain. So instead of giving us subdomain matching like we were asking for we get FQDN matching instead. This is a bit better but if I choose to put "example.com" in with this option it should match with "https://example.com" but it doesn't. I should also be able to do "http://test.example.com" and then match with "https://dev.test.example.com".
Instead of having an option to fully match FQDN's we just wanted an option to say "match subdomains" because subdomains matter. You've managed to ship something that is supposed to meet the needs of those asking for this feature for years and yet failed to make it usable.
At least it will make port matching a thing now. If we save the exact FQDN we expect to get.
It's not that we didn't like the fuzzy matching it's just we wanted to be able to control it more not remove it entirely.
Also I don't know who wrote this text input box but you should allow someone to scroll up and down to edit their post. I have no idea how I started this because I can't scroll up...
Oh well ship it!
1Password Version: 1Password for Mac 8.10.13 (81013005)
Extension Version: 2.14.1
OS Version: MacOS 13.5.1
Browser: Chrome