You could still use bcrypt and do the comparison work server-side.
Depending on work factors and whatnot, it's now a backend load balancing issue. But it's probably solvable.
Depending on work factors and whatnot, it's now a backend load balancing issue. But it's probably solvable.
If something like this worked, it would provide a method of breaking the hash in a piecemeal fashion, which would mean the hash algorithm never worked properly in the first place.
EDIT: reply to below: The only thing it can tell you is that two passwords don't match. It tells you nothing about whether they're similar. (And also doesn't tell you they do match, for which you need the whole hash.)
What do you mean? They work for my purpose, which is being able to tell "password" and "passwrod" apart. There will be false positives, of course, but an (educated) assumption is that they are not going to be frequent for lexically related inputs.