Followup to: Announcing the Less Wrong Sub-Reddit
After the recent discussion about the Less Wrong sub-reddit, me and Less Wrong site designer Matthew Fallshaw have been discussing possible site improvements, and ways to implement them. As far as I can tell, the general community consensus in the previous post was that a discussion section to replace the Open Thread would be a good idea, due to the many problems with Open Thread, but that it would be problematic to host it off-site. For this reason, our current proposal involves modifying the main site to include a separate "Discussion" section in the navigation bar (next to "Wiki | Sequences | About"). What are now Open Thread comments would be hosted in the Discussion section, in a more user-friendly and appropriate format (similar to Reddit's or a BBS forum's). If my impression was mistaken, please do say so. (If you think that this is a great idea, please do say so as well, to avoid Why Our Kind Can't Cooperate.)
We have also identified another potential problem with the site: the high quality standard, heavy use of neologisms, and karma penalties for being wrong might be intimidating to newcomers. To help alleviate this, after much discussion, we have come up with two different proposals. (To avoid bias, I'm not going to say which one is mine and which one is Matthew's.)
- Proposal 1: Posts submitted to Less Wrong can be tagged with a "karma coward" option. Such posts can still be voted on, but votes on them will have no effect on a user's karma total. There will be a Profile option to hide "karma coward" posts from view.
- Proposal 2: A grace period for new users. Votes on comments from new users will have no effect on that user's karma total for a certain period of time, like two weeks or a month.
- Proposal 3: Do nothing; the site remains as-is.
To see what the community consensus is, I have set up a poll here: http://www.misterpoll.com/polls/482996. Comments on our proposals, and alternative proposals, are more than welcome. (To avoid clogging the comments, please do not simply declare your vote without explaining why you voted that way.)
EDIT: Posts and comments in the discussion section would count towards a user's karma total (not withstanding the implementation of proposal 1 and proposal 2), although posts would only earn a user 1 karma per upvote instead of 10.
EDIT 2: To avoid contamination by other people's ideas, please vote before you look at the comments.
I did not mean to say that the software existed in a perfect form, only that the design and separation of concerns exhibited by Usenet was exactly what was needed, and that the nicest news readers had an extremely well-designed interface -- exactly as useable as Thomas's wishlist.
A straight NNTP frontend would be quite nice -- it solves the reading, tree-navigating, and catchup problems. What it leaves unsolved is voting, private messages, and drafts. Of these, I only see the first as critical.
Of the ways to get such a separation of concerns, publishing the database via NNTP seems the easiest to me. It's still nowhere near a trivial "plug these two pieces of code together", of course. I'm not familiar enough with the reddit codebase to know how well it maps to NNTP, and how long it would take. My rough estimate would be a month or two to get something useable from a programmer working full time.
Then we have to figure out how to do voting, which means (a) defining an extension to the NNTP protocol, (b), implementing it on the server, and (c) patching a few clients to use it. This I'd expect to take on the order of a week or two, if everything else was working.
I have to chuckle at "the nicest news readers had an extremely well-designed interface". Which news readers do you mean? I mostly used trn and the newsreader in lynx, though I tried slrn, tin, rn, pine, the newsreader in Netscape Communicator and IIRC a text-mode client named nn (but not Emacs GNUS, which I did not have the hardware resources to run). When I stopped using trn, I promised myself I would never again use software with a user interface as badly designed as trn's user interface.
ADDED. My low opinion of trn's user interface does no... (read more)