[Edit: Issues, Bugs, and Requested Features should be tracked at Google Code, not here -- matt, 2010-04-23]
Less Wrong is still under construction. Please post any bugs or issues with Less Wrong to this thread. Try to keep each comment thread a clean discussion of each bug or issue.
Requested features... sure, go ahead, but bear in mind we may not be able to implement for a while.
A specification of desired tag and sequence behavior for a future version of Less Wrong (don't expect this tomorrow):
Tags should be applicable by any user to their posts. Clicking on a tag should, by default, show the matching posts latest-first, but the switch to read oldest-first should be prominent.
When viewing the posts matching a tag, the URL from the index page to each post should contain the tag query, such as /post/?tag=self_deception. It is preferable to use a query rather than a cookie or any other such methods, because it is desirable to be able to link to posts with a particular tag emphasized.
When visiting a post with ?tag=self_deception, the following navigation bar should be visible:
<< Prev | [Post title up to N chars] Tag: Self_Deception [Post title up to N chars] | Next >>
post body
<< Prev | [Post title up to N chars] Tag: Self_Deception [Post title up to N chars] | Next >>
Note that the "Prev" and "Next" must not appear before the post title. Overcoming Bias does this, and as a result, Google often mistakes the text of the "Prev" link for the page title! Searching under that title will turn up the page that has that "Prev" link, not the real link - even though the page title is accurate, Google seems to pay more attention to the first words appearing on the page.
"Tag: Self_Deception" should link to a search on the Self_Deception tag, but should not be prominently underlined/linky without a mouseover.
Obviously, the URLs for the "Prev" and "Next" links should contain ?tag=whatever.
All such pages returned should be marked as not the canonical version. See http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html
Navigating through posts with ?author=Yvain should behave the same as above, except that "Tag: Self_Deception" goes to "Author: Yvain".
Sequences should be created, titled, and owned by a particular author, with arbitrary rather than chronological ordering, but with other author's posts being insertable into the sequence. By default, sequences appear oldest-first rather than newest-first, unlike tags and authors. Aside from this, ?seq=quantum and "Sequence: Quantum Physics" as above.
Being able to mark a post as being part of a particular sequence by default that shows up with no query (overridable by ?seq= or ?seq=none) would let me get rid of a good deal of "previously in series" cruft.
Because tags (especially with choosable sort order) give us a good deal of the functionality of sequences, implementing this behavior for tags can be prioritized above the same behavior for authors and sequences, in order to save some time and let me to do some poor man's sequences to start with. Tags get us 80% of the functionality, sequences get us 90% of the functionality, and anything more in the way of dependency-tracking can be put off into the more distant future.
It is acceptable to start with if various URLs within the page do not reflect the tag used to navigate to that page. We just want a basic tag-navigation system up as fast as possible.
It would be cool if fluid widths let users expand the page to see more of the post titles in "Prev" and "Next", or if narrower pages hid more of the post titles, but this is again not core functionality.
Being able to specify an RSS feed that goes through a tag/author/sequence at a specified N posts per day until the user is caught up, will help users catch up; this also needs the ability to pause for vacations, move back a few days, scroll forward on a click, and otherwise behave intelligently. In short, it's another major feature that should not be rolled out until after core functionality is implemented.