This is insecure if LW1 hashes get leaked or were leaked at some point.
Isn’t this vulnerability inherent in the whole “hashing passwords on the client” setup? (indeed, it seems to miss the whole point of hashing?) Or am I misunderstanding what Meteor does?
Thanks! Do you plan to add support for the new-to-LW2 “log in with LW1 credentials” flow? It seems to need some special-cased client-side support, according to this post—I suppose you can check out the related commits on LW2 code for the details of how to make it work! (Logging in and participating on LW2 itself is still unbearably slow for lower-powered devices—and I’m not willing to go through the whole prospect of having to change (or worse, “reset”) my credentials there in order to make them usable on GreaterWrong—at least, not unless I hear back from multiple users who have done this with no issues!)