It looks like this is my last chance to comment before being locked out:
The new site doesn’t work for me. I can’t even test if my account was succesfully copied, the login button doesn’t work (nothing happends when I click it). I can read articles, but expanding/collapsing comments, changing sort order or hiding/showing the menu don’t work.
In the browser console I can see the error “23:32:44.521 SyntaxError: missing = in const declaration” in 168fe459c5f7f951455b85e6019b9d94a5142c29e.js:9:1210986 (I guess there are more errors, but the execution stops there).
I have an firefox 48.0.2 (and other even older browsers) on GNU/Linux and I can’t easily install any newer version on my computer.
I didn’t originally have my recovery email set for some time when the new site was launched, so I’m not sure if I’ll be able to get a new password for the new site if and when I get a properly working computer. I might lose my account for good.
It looks like javascript is the source of this problem (and actually many other proplems others have reported in the new site). I would highly recommend testing that all essential functionality (at least: listing and reading all articles, listing and reading all comments of an article, loging in / creating accounts, writing text-only comments and articles) works with javascript completely disabled, or even better in a completely text based browser.
Now the login button opens the login popup correctly, but I still failed to reset my password.
I tried to click the “Forgot password” → popup asks me for email → I enter it and click “RESET YOUR PASSWORD” → error message “User not found” appears → I enter username instead and click “RESET YOUR PASSWORD” → error message “Invalid email” appears. (It doesn’t seem to make any difference whether I enter my username or email or nothing in the first login popup.)
In my older firefox (10.0.4 ESR) the site loads extremely slowly and consumes several gigabytes of memory (some of it is freed after loading is complete) and these errors appear in the error console:
This is expected behavior if the recovery email address was not set in the user data LW2 imported from LW1 back in September, or whatever—LW2 simply doesn’t know about that email address at the moment! The LW2 devs have promised a “final import” of LW1 data, which should fix this sort of issue (again, assuming that you have set your email here; if you haven’t done this yet, you should do it right now, and follow the instructions in the automated email LW1 sends you to verify that you control that address!); though of course it would be nice to have proper confirmation of this. Again, just my 2¢.
(The version of Firefox you mention is positively ancient, BTW—are you sure that you can’t update software on that GNU/Linux computer? It should be possible to do so without impacting system requirements much.)
This is expected behavior if the recovery email address was not set in the user data LW2 imported from LW1 back in September, or whatever—LW2 simply doesn’t know about that email address at the moment! The LW2 devs have promised a “final import” of LW1 data, which should fix this sort of issue
I have set my recovery email four months ago (2017/11/14).
So it seems that I have to wait until I’ve been locked out of lw1.0 and only then I can try if I can log into lw2.0. If anything goes wrong (as it usually does with computer systems), I’ll be locked out of both and so I’ll be unable to communicate to the developers what went wrong. I shouldn’t have to say that this is highly undesirable—users should be able to test the new system before the old system is shut down.
BTW—are you sure that you can’t update software on that GNU/Linux computer?
Updating firefox seems to require (after several layers of depencies) updating udev—which requires updating kernel or it will might make the system unbootable. There are also circular depencies, changes needed to masked packages and manual configuration changes. At this point I’d need to back up my system, get a boot disk and prepare for significant donwtime. Additionaly updating firefox breaks many of the extensions that I’m using.
So it seems that I have to wait until I’ve been locked out of lw1.0 and only then I can try if I can log into lw2.0 …
Good catch. It would make sense to keep some version of LW1.0 running for a while even after the “final import” is done, purely for the sake of supporting existing users in migrating to LW2. However, I understand that the reddit-derived LW1 code is practically unmaintained by now, so Trike (the folks who host LW1) aren’t willing to keep it going for much longer. This means that the site devs’ hands are somewhat tied at this point and the status quo is not really tenable.
Updating firefox seems to require (after several layers of depencies) updating udev—which requires updating kernel or it will might make the system unbootable.
Kernel updates are relatively foolproof, unless you did something fancy like compiling a patched version with support for some sort of custom hardware. And you can probably install a newer version alongside the old, without updating udev, so you can get a choice at boot and have a way to ensure that the new version works before you make your system reliant on it. Even if you can’t in fact do this (because the newer kernels turn out to be incompatible with some feature of the existing system, like old udev), all you really need is a “live” boot disk to make sure that your hardware plays nice with the new kernel—everything else should be recoverable.
BTW, it’s only the very latest versions of Firefox that break all old-style addons. IIRC, 52esr still supports them and is relatively current.
Yeah, we are working on browser compatibility. I actually just figured out what was causing your specific bug, so that one should be fixed within at least the next two or three days.
Some navigation aspects are definitely hard to make work with javascript completely disabled (example: The hamburger menu), but we should be able to make it so that the site fails gracefully when some javascript stuff doesn’t work.
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+.
It looks like this is my last chance to comment before being locked out:
The new site doesn’t work for me. I can’t even test if my account was succesfully copied, the login button doesn’t work (nothing happends when I click it). I can read articles, but expanding/collapsing comments, changing sort order or hiding/showing the menu don’t work.
In the browser console I can see the error “23:32:44.521 SyntaxError: missing = in const declaration” in 168fe459c5f7f951455b85e6019b9d94a5142c29e.js:9:1210986 (I guess there are more errors, but the execution stops there).
I have an firefox 48.0.2 (and other even older browsers) on GNU/Linux and I can’t easily install any newer version on my computer.
I didn’t originally have my recovery email set for some time when the new site was launched, so I’m not sure if I’ll be able to get a new password for the new site if and when I get a properly working computer. I might lose my account for good.
It looks like javascript is the source of this problem (and actually many other proplems others have reported in the new site). I would highly recommend testing that all essential functionality (at least: listing and reading all articles, listing and reading all comments of an article, loging in / creating accounts, writing text-only comments and articles) works with javascript completely disabled, or even better in a completely text based browser.
The site should now work properly on Firefox 48. Are there any other browsers you use on which it still breaks?
Now the login button opens the login popup correctly, but I still failed to reset my password.
I tried to click the “Forgot password” → popup asks me for email → I enter it and click “RESET YOUR PASSWORD” → error message “User not found” appears → I enter username instead and click “RESET YOUR PASSWORD” → error message “Invalid email” appears. (It doesn’t seem to make any difference whether I enter my username or email or nothing in the first login popup.)
In my older firefox (10.0.4 ESR) the site loads extremely slowly and consumes several gigabytes of memory (some of it is freed after loading is complete) and these errors appear in the error console:
“can’t redefine non-configurable property ‘name’” in https://www.lesserwrong.com/84070395a9ed6ed856734634005a280abd590aba.js?meteor_js_resource=true line 9
“Fragment “LWPostsList” not registered.” in https://www.lesserwrong.com/84070395a9ed6ed856734634005a280abd590aba.js?meteor_js_resource=true line 113
(+ too many warnings to list here)
[edited to correct formating]
This is expected behavior if the recovery email address was not set in the user data LW2 imported from LW1 back in September, or whatever—LW2 simply doesn’t know about that email address at the moment! The LW2 devs have promised a “final import” of LW1 data, which should fix this sort of issue (again, assuming that you have set your email here; if you haven’t done this yet, you should do it right now, and follow the instructions in the automated email LW1 sends you to verify that you control that address!); though of course it would be nice to have proper confirmation of this. Again, just my 2¢.
(The version of Firefox you mention is positively ancient, BTW—are you sure that you can’t update software on that GNU/Linux computer? It should be possible to do so without impacting system requirements much.)
I have set my recovery email four months ago (2017/11/14).
So it seems that I have to wait until I’ve been locked out of lw1.0 and only then I can try if I can log into lw2.0. If anything goes wrong (as it usually does with computer systems), I’ll be locked out of both and so I’ll be unable to communicate to the developers what went wrong. I shouldn’t have to say that this is highly undesirable—users should be able to test the new system before the old system is shut down.
Updating firefox seems to require (after several layers of depencies) updating udev—which requires updating kernel or it will might make the system unbootable. There are also circular depencies, changes needed to masked packages and manual configuration changes. At this point I’d need to back up my system, get a boot disk and prepare for significant donwtime. Additionaly updating firefox breaks many of the extensions that I’m using.
Good catch. It would make sense to keep some version of LW1.0 running for a while even after the “final import” is done, purely for the sake of supporting existing users in migrating to LW2. However, I understand that the reddit-derived LW1 code is practically unmaintained by now, so Trike (the folks who host LW1) aren’t willing to keep it going for much longer. This means that the site devs’ hands are somewhat tied at this point and the status quo is not really tenable.
Kernel updates are relatively foolproof, unless you did something fancy like compiling a patched version with support for some sort of custom hardware. And you can probably install a newer version alongside the old, without updating udev, so you can get a choice at boot and have a way to ensure that the new version works before you make your system reliant on it. Even if you can’t in fact do this (because the newer kernels turn out to be incompatible with some feature of the existing system, like old udev), all you really need is a “live” boot disk to make sure that your hardware plays nice with the new kernel—everything else should be recoverable.
BTW, it’s only the very latest versions of Firefox that break all old-style addons. IIRC, 52esr still supports them and is relatively current.
I don’t think there is anything stopping you from trying to create a test LW2 account to see if you will be locked out
Yeah, we are working on browser compatibility. I actually just figured out what was causing your specific bug, so that one should be fixed within at least the next two or three days.
Some navigation aspects are definitely hard to make work with javascript completely disabled (example: The hamburger menu), but we should be able to make it so that the site fails gracefully when some javascript stuff doesn’t work.
Www.greaterwrong.com
How do I reset/recover my password in greaterwrong? Or does my old lesswrong password work there?
Greaterwrong uses the account data on lesserwrong which got its data from lw1.0
If I remember correctly, the passwords were not trasferred from lw1.0 to lesserwrong—users were supposed to reset their password.
So it seems like I’m still going to be locked out.
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+.