Any progress on this? With the switchover from LW1 now imminent, I’ve looked at the LessWrong code on github a bit more and from a cursory review, it really does seem that the usecase or ‘flow’ of a user editing their own “recovery email” address is broken. The code calls the proper Meteor/Vulcan functions when creating a new user, and will in turn create new users when importing them for the first time from a legacy (LW1) database, but aside from that, there is no acknowledgement that Vulcan/Meteor has its own functions in the ‘account’-related packages for setting/updating these data. Did you test this user flow (even just in a test instance of the code) and verify that it can be used to set an email address that the “forgot password/reset password” will rely on?
Any progress on this? With the switchover from LW1 now imminent, I’ve looked at the LessWrong code on github a bit more and from a cursory review, it really does seem that the usecase or ‘flow’ of a user editing their own “recovery email” address is broken. The code calls the proper Meteor/Vulcan functions when creating a new user, and will in turn create new users when importing them for the first time from a legacy (LW1) database, but aside from that, there is no acknowledgement that Vulcan/Meteor has its own functions in the ‘account’-related packages for setting/updating these data. Did you test this user flow (even just in a test instance of the code) and verify that it can be used to set an email address that the “forgot password/reset password” will rely on?