passforios
passforios copied to clipboard
Domain name matching is too fuzzy
Sometimes (well, most of the time), when using autofill, the "suggested passwords" include several completely unrelated entries in addition to the required one:

When I'm trying to work with sites with a complex domain structure (e. g. many sites with separate logins under a common domain), quality of matching degrades even further:

I think the domain name matching algorithm needs to be much smarter in these cases. I can think of a few rules that would be very helpful if implemented:
- Domain name matching algorithm needs to work at each path segment of the password file name, starting with the last path segment (after last
/). - For a match to count, a substring of the domain name must match a substring of the file name segment, where both substrings have to be anchored at the end of the string and end either with a dot or at the beginning of the string (i. e.
foo.comshould not matchfoooo.comjust because there is a commono.comsubstring). - Something needs to be invented against matches consisting just of TLDs. For example, substring matches without a dot could be inhibited unless it is a full string.
- Matches must be sorted by their length.
Any chance this sort of algorithm could be implemented? Or just point me to the place where matching happens and I'll try to learn enough Swift to code it.
I believe this is still broken in the same way with the latest TestFlight build. Please reopen.