Some suggestions (desperate pleas, even)
post by Jiro · 2017-11-09T23:14:14.427Z · LW · GW · 5 commentsContents
5 comments
- A way to see all replies to your own comments or posts
- Setting defaults for sorting rather than having to manually sort by recent every time
- Put the see all comments link in a reasonably easy to find place
- "All posts" which actually shows all posts without requiring that the user separately click on each one in order to read it
- If you can't eliminate the huge gutter space, at least provide an option to reduce it
- A way to edit the raw text of a post. It is hard to struggle with a malicious parser. When I typed "expand(underscore)less", "expand(underscore)more" below using real underscores, the parser decided I want to italicize everything between the two underscores.
- Maybe a bugzilla to report bugs? Reporting bugs here or on intercom is suboptimal.
- Edit: I tried to submit this post and it didn't appear. If your post is being held it should tell you that your post is being held because otherwise this is hard to distinguish from a malfunction. Also, when you submit your post it doesn't say where it's submitted to--I meant to submit this to Meta.
Also, I'm still having trouble reading this. It's only working on Chrome. Firefox has formatting problems; certain icons (search, "expand(underscore)less", "expand(underscore)more", "navigate(underscore)before", "navigate(underscore)next") show up as text instead of as icons. IE looks good but doesn't show the conversations icon and doesn't do anything if I click "LOGIN".
5 comments
Comments sorted by top scores.
comment by habryka (habryka4) · 2017-11-10T17:45:23.960Z · LW(p) · GW(p)
Maybe a bugzilla to report bugs? Reporting bugs here or on intercom is suboptimal.
We have a Github: https://github.com/Discordius/Lesswrong2/tree/devel
comment by Arandur · 2017-11-10T14:41:25.231Z · LW(p) · GW(p)
Adding to the Markdown parsing comment: if we're going to type in Markdown anyway instead of having a proper WYSIWYG editor (make no mistake; I prefer the former!) (Although I see that highlighting text causes a WYSIWYG panel to open up, which I think is excellent), I think it makes sense to separate the raw input from the formatting. I would prefer a system such as Reddit or Stack Exchange have, where the text-box shows the raw Markdown, and the resultant formatted text is displayed elsewhere for review. Combining the two into one area makes fine editing more difficult.
I'm inclined to believe that this would also go some way toward fixing Jiro's underscore issue, since "[struggling] with a malicious parser" is somewhat easier when you have easy access to the parser's input and output. It might not help as much as I think, though, and it would indeed be easier not to have to struggle. (Jiro, as a workaround I would recommend surrounding the offending text with backticks, e.g. `expand_less`.