Error comments on The Web Browser is Not Your Client (But You Don't Need To Know That) - Less Wrong Discussion
You are viewing a comment permalink. View the original post to see all comments and the full post content.
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (47)
Before we get deep into protocols, is there any kind of a spec sheet anywhere?
Saying you want better software for discussions is... horribly vague. I have a strong feeling that we should figure out things like lists of desirable features, lists of undesirable misfeatures, choices of how one list will be traded off against the other list, etc. before we focus all the energy on stomping JSON into tiny little pieces.
I had a list of...not features, exactly, but desirable elements, in the first post. I intended to update it from comments but didn't.
I want higher and deeper X-)
Higher in the sense of specifying desirables from some set of more-or-less terminal goals. For example, you say "centralized from the user perspective" -- and why do we want this? What is the end result you're trying to achieve?
Deeper in the sense of talking about base concepts. Will there be "posts" and "comments" as very different things? If so, will the trees be shallow (lots of posts, mostly with few comments, no necroing) or deep (few posts, mostly with lots of comments, necroing is encouraged)?
Will there be a "forum"? "subforums", maybe? Or will there be a pile of tagged pieces of text from which everyone assembles their own set to read? Will such concept as "follow an author" exist? How centralised or decentralised will things be? Who will exercise control and what kind of powers will they have?
That's not a complete set of questions at all, just a pointer at the level which will have to decided on and set in stone before you start discussing protocols.