This post will serve as a place to discuss what features the new LessWrong 2.0 should have, and I will try to keep this post updated with our feature roadmap plans.
Here is roughly the set of features we are planning to develop over the next few weeks:
UPDATED: August 27th, 2017
Basic quality of life improvements:
Improve rendering speed on posts with many comments
(A lot of improvements made, a lot more to come)Improve usability on mobile
(After the major rework this is somewhat broken again, will fix it soon)Add Katex support for comments and posts
Allow merging with old LessWrong 1.0 accounts
Fix old LessWrong 1.0 links DONE!
Create unique links for each comment: DONE!
Make comments collapsible
Highlight new comments since last visit: DONE!
Improve automatic spam-detection
Add RSS feed links with adjustable karma thresholds
Create better documentation for the page, with tooltips and onboarding processes
Better search, including comment search and user search: DONE!
Improved Moderation Tools:
New Karma system that weighs your votes based on your Karma
Give moderators ability to suspend comment threads for a limited amount of time
Give trusted post-authors moderation ability on their own posts (deleting comments, temporarily suspending users from posts, etc.)
Add reporting feature to comments
Give moderators and admins access to a database query interface to identify negative vote patterns
New Content Types:
Add sequences as a top-level content-type with UI for navigating sequences in order, metadata on a sequence, and keeping track of which parts you've read DONE!
Add Arbital-style predictions as a content block in posts (maybe also as a top-level content type)
Add 'Wait-But-Why?' style footnotes to the editor
Discussion page that structures discussions more than just a tree format (here is a mockup I designed while working for Arbital, that I am style excited to implement)
...and we have many more crazy ideas we would like to experiment with
I will also create a comment for each of these under the post, so you can help us prioritize all of these. Also feel free to leave your own feature suggestions and site improvements in the comments.
Whatever the data-structure for the sequences is, the goal is to present the user a linear sequence of content (which might be dynamically generated from a dependency DAG).
It's really hard to keep track of your position in a tree, and practically all projects that I know of that tried to present complicated information a tree-view either failed or moved to a linear view eventually (for example Khan Academy)
Hm. What I want is a tree which is really just a linear structure functionally speaking (no automatic queuing of prerequisites or anything), but which allows more visual organization of a long sequence into parts for sanity's sake. I'd get >90% of the functionality I want just by being allowed to intersperse headers on a "sequence" page to organize sub-sequences. The sequences themselves currently have one more level of organization than that, with "books" and then "sections" -- so you can think of them as one long sequence with six sub-sequences and twenty-six sub-sub-sequences. That's the kind of hierarchical organization I'm asking for.