Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
Update about Autofill improvements in Beta
Hey folks,
We’ve worked hard over the last three months to improve the reliability of Autofill in complex situations, such as when you have multiple items for the same website or want certain items...
In response to filmjbrandon (with apologies), and to any ABits folks (e.g. 1P_Travis or @ag_Gabriele), the problem is much bigger, IMO, than simply exposing an API to allow capable people to hack on their entries en-masse. While a nice idea, the fundamental solution that AG has exposed, namely the idea of "only fill on this exact domain", is completely insufficient to handle even the most modest of use cases. Let me explain my thinking:
Imagine even a small business IT/DevOps group with a modest number of (in-house or cloud-based) hosts they manage. Even some of the smallest such organizations will have dozens of "hosts", and they will likely be added to (or removed) over time. Having to set some "only fill on exactly this domain" on each new entry is exceedingly painful and, IMO, completely unnecessary. There is more than sufficient information even given the limited form of URLs that can be usefully entered into 1Password. With some useful heuristics, one can simply sort the entries by a closest-match algorithm and thus present the user with the most likely entry up front, with no manual work on the part of the user. For a complete solution, I urge anyone to look at my suggestions in an earlier post:
https://1password.community/discussion/comment/673589/#Comment_673589
Furthermore, with a little bit of additional smarts, e.g. if the tool supported some form of regex in the URLs, those with even modestly complicated environments, like my own, could say things like:
https://server[0-9].example.com
... and have the entry match a collection of hosts rather than being forced to add a separate URL for each of those N hosts.
Furthermore, this will support even novice users, and those who cannot (or don't want to) work though an API to flip bits on every entry.
Now, I know that the ABits folks are good and talented, and that they'd rather keep internal ideas mum for competitive advantage, but someone from AG could at least comment on my proposed set of changes, even say "interesting idea - we'll take it to the dev team", that would be greatly appreciated.
As it stands now, the 1P8 approach, with the removal of the "smart suggestions" feature, is again a step backwards from the excellent 1P7 version.
