Profiles are still kind of broken in that Markdown doesn’t work, so my profile has lost functionality compared on on old LW.
Q: Is stuff that was posted on old LW after the import to LesserWrong being merged in as well?
Individual comment links still don’t work great, due to relying on anchors; my browser “misses” a lot and I have to go back to the URL bar and hit enter again. A proper system of individual pages for comments like Reddit/old LW would be better, I think.
Yep, we imported all content that was posted to the old LW (we created a new database dump at 6PM yesterday). Let us know if you notice anything missing.
Re anchors: I think we should improve the way we do comment links. I am really not a huge fan of how Reddit does it, since I never feel like I have enough context, and always feel a bit lost on the comment page, but am also not happy with our current solution. Happy about more suggestions for this.
Yep, we imported all content that was posted to the old LW (we created a new database dump at 6PM yesterday). Let us know if you notice anything missing.
Great, thanks!
Re anchors: I think we should improve the way we do comment links. I am really not a huge fan of how Reddit does it, since I never feel like I have enough context, and always feel a bit lost on the comment page, but am also not happy with our current solution. Happy about more suggestions for this.
I mean, that’s what the context option is for. Old LW had the built-in add-one-context link, too, which reddit doesn’t, although adding one context at a time is pretty slow (Reddit of course has its context links that immediately provide 3 context, but doesn’t have these on the comment pages themselves). Personally I think “link to the comment, let the reader handle context-fetching” is fine. If you really think people are confused you can make the “add context” or “parent” links more prominent.
Edit: Sorry, this is unrelated but I just noticed it editing this comment. Apparently when I post a comment, any included Markdown is silently converted to equivalent-but-possibly-different Markdown. (E.g., I used astersisks to emphasize something, and they were converted to underscores.) Can I ask that this not be done? That those of us using the Markdown editor have our actual text unaltered when we go to edit it later? Thank you!
Edit: Sorry, this is unrelated but I just noticed it editing this comment. Apparently when I post a comment, any included Markdown is silently converted to equivalent-but-possibly-different Markdown. (E.g., I used astersisks to emphasize something, and they were converted to underscores.) Can I ask that this not be done? That those of us using the Markdown editor have our actual text unaltered when we go to edit it later? Thank you!
FYI, GreaterWrong does exactly what you ask (i.e., GW caches your actual entered raw text, and retrieves that cached text when you later edit your comment/post—regardless of how that entered text has been transformed for display by Less Wrong).
Apparently when I post a comment, any included Markdown is silently converted to equivalent-but-possibly-different Markdown. (E.g., I used astersisks to emphasize something, and they were converted to underscores.) Can I ask that this not be done?
I’m assuming this happens when using the pure-markdown editor? If not, consider switching to the pure markdown editor if you haven’t already (click ‘edit profile’). If so, I agree this is suboptimal but we probably won’t get to it for awhile (it involves digging into the gritty details of the markdown/html/draftjs converters)
(Among other things, simply making it so it’s _possible_ to use markdown on most text fields such as the User Profile is a fair amount of work that seems more urgent)
Alright!
Profiles are still kind of broken in that Markdown doesn’t work, so my profile has lost functionality compared on on old LW.
Q: Is stuff that was posted on old LW after the import to LesserWrong being merged in as well?
Individual comment links still don’t work great, due to relying on anchors; my browser “misses” a lot and I have to go back to the URL bar and hit enter again. A proper system of individual pages for comments like Reddit/old LW would be better, I think.
Yep, we imported all content that was posted to the old LW (we created a new database dump at 6PM yesterday). Let us know if you notice anything missing.
Re anchors: I think we should improve the way we do comment links. I am really not a huge fan of how Reddit does it, since I never feel like I have enough context, and always feel a bit lost on the comment page, but am also not happy with our current solution. Happy about more suggestions for this.
Great, thanks!
I mean, that’s what the context option is for. Old LW had the built-in add-one-context link, too, which reddit doesn’t, although adding one context at a time is pretty slow (Reddit of course has its context links that immediately provide 3 context, but doesn’t have these on the comment pages themselves). Personally I think “link to the comment, let the reader handle context-fetching” is fine. If you really think people are confused you can make the “add context” or “parent” links more prominent.
Edit: Sorry, this is unrelated but I just noticed it editing this comment. Apparently when I post a comment, any included Markdown is silently converted to equivalent-but-possibly-different Markdown. (E.g., I used astersisks to emphasize something, and they were converted to underscores.) Can I ask that this not be done? That those of us using the Markdown editor have our actual text unaltered when we go to edit it later? Thank you!
FYI, GreaterWrong does exactly what you ask (i.e., GW caches your actual entered raw text, and retrieves that cached text when you later edit your comment/post—regardless of how that entered text has been transformed for display by Less Wrong).
I’m assuming this happens when using the pure-markdown editor? If not, consider switching to the pure markdown editor if you haven’t already (click ‘edit profile’). If so, I agree this is suboptimal but we probably won’t get to it for awhile (it involves digging into the gritty details of the markdown/html/draftjs converters)
(Among other things, simply making it so it’s _possible_ to use markdown on most text fields such as the User Profile is a fair amount of work that seems more urgent)
Yes, sorry, forgot to state that explicitly, that’s what I’m doing and it does indeed still occur.