You should set your recovery email here on LW1 (if you haven’t done so already), so that it has a chance of being part of the previously-announced “final import” of LW1 data; assuming that this occurs successfully, you’ll then be able to “reset your password” on LW2 (or, more conveniently for you, on GreaterWrong) using that email address and log in there. Just my 2¢ here, since I’m not a LW2 developer. (It would sure be nice if we had more participation from the devs here, since after all we’re thinking about a major migration and there are still unresolved issues with the new site, as e.g. my toplevel comment in this thread shows! I’m not at all opposed to the migration per se—especially since we now have GreaterWrong! - but I would like to see some commitment from them that meaningful efforts will be made to address these issues)
Added: I just checked and apparently “reset password” is not available on GreaterWrong, only on LesserWrong—and it seems to rely on JavaScript. LW2 devs, could you provide a simple JS-free page for the “password reset” functionality, so that GW can link to it and users on e.g. old computers or cheap mobile devices or with accessibility needs (which are often exacerbated by JS-heavy, ‘modern’ web designs) can use this function of the site? Alternately, could you enable its use from GreaterWrong itself?
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!)
Thanks, hopefully this will help some users (although I’m having issues w/ LW1 login right now, hence the different account). Could you try and figure out why newly-imported LW1 comments aren’t appearing in the GW user profile (whether or not I select the show=comments option), although they do appear on the main site? (The same problem also applies to karma scores.) This issue even impacts comments by your LW1 user in this thread.
Sorry for not being around more! We launched the Community/Meetup interface just before we announced the vote, so I’ve been busy polishing that up and making sure everything for that works.
Now that that system works more stably, I will be more responsive in answering questions about the vote and the transition, etc. And in general I check LW2 more often than here, so if you have questions asking over there will probably get you a faster response.
Re password reset: Yep, everything you said is correct, and it does seem reasonable to have a page with both developer contact info and password reset functionality that is accessible without fancy JS. But I don’t know how much I can promise yet for that, since it might just end up being a big pain to make the Meteor password reset work without any JS whatsoever. But we should test it so that it at least works in IE 9+.
You should set your recovery email here on LW1 (if you haven’t done so already), so that it has a chance of being part of the previously-announced “final import” of LW1 data; assuming that this occurs successfully, you’ll then be able to “reset your password” on LW2 (or, more conveniently for you, on GreaterWrong) using that email address and log in there. Just my 2¢ here, since I’m not a LW2 developer.
(It would sure be nice if we had more participation from the devs here, since after all we’re thinking about a major migration and there are still unresolved issues with the new site, as e.g. my toplevel comment in this thread shows! I’m not at all opposed to the migration per se—especially since we now have GreaterWrong! - but I would like to see some commitment from them that meaningful efforts will be made to address these issues)
Added: I just checked and apparently “reset password” is not available on GreaterWrong, only on LesserWrong—and it seems to rely on JavaScript. LW2 devs, could you provide a simple JS-free page for the “password reset” functionality, so that GW can link to it and users on e.g. old computers or cheap mobile devices or with accessibility needs (which are often exacerbated by JS-heavy, ‘modern’ web designs) can use this function of the site? Alternately, could you enable its use from GreaterWrong itself?
I’ve now added password reset capability to GreaterWrong.
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!)
Yeah, I’ll see if I can figure out how to do that.
Thanks, hopefully this will help some users (although I’m having issues w/ LW1 login right now, hence the different account). Could you try and figure out why newly-imported LW1 comments aren’t appearing in the GW user profile (whether or not I select the
show=commentsoption), although they do appear on the main site? (The same problem also applies to karma scores.) This issue even impacts comments by your LW1 user in this thread.Sorry for not being around more! We launched the Community/Meetup interface just before we announced the vote, so I’ve been busy polishing that up and making sure everything for that works.
Now that that system works more stably, I will be more responsive in answering questions about the vote and the transition, etc. And in general I check LW2 more often than here, so if you have questions asking over there will probably get you a faster response.
Re password reset: Yep, everything you said is correct, and it does seem reasonable to have a page with both developer contact info and password reset functionality that is accessible without fancy JS. But I don’t know how much I can promise yet for that, since it might just end up being a big pain to make the Meteor password reset work without any JS whatsoever. But we should test it so that it at least works in IE 9+.