{
  localUrl: '../page/711.html',
  arbitalUrl: 'https://arbital.com/p/711',
  rawJsonUrl: '../raw/711.json',
  likeableId: '3827',
  likeableType: 'page',
  myLikeValue: '0',
  likeCount: '6',
  dislikeCount: '0',
  likeScore: '6',
  individualLikes: [
    'AlexeiAndreev',
    'BenPace',
    'EricRogstad',
    'AndreaGallagher',
    'StephanieZolayvar',
    'ChaseRoycroft'
  ],
  pageId: '711',
  edit: '2',
  editSummary: '',
  prevEdit: '1',
  currentEdit: '2',
  wasPublished: 'true',
  type: 'wiki',
  title: 'Improve comments by tagging claims',
  clickbait: 'Comment sections are more important for discourse than I thought. They can be improved by explicitly tagging an article's main claims as anchors for discussion.',
  textLength: '11150',
  alias: '711',
  externalUrl: '',
  sortChildrenBy: 'likes',
  hasVote: 'false',
  voteType: '',
  votesAnonymous: 'false',
  editCreatorId: 'EricRogstad',
  editCreatedAt: '2016-12-21 03:13:44',
  pageCreatorId: 'BenjaminHoffman',
  pageCreatedAt: '2016-12-20 17:19:41',
  seeDomainId: '0',
  editDomainId: '2137',
  submitToDomainId: '2069',
  isAutosave: 'false',
  isSnapshot: 'false',
  isLiveEdit: 'true',
  isMinorEdit: 'false',
  indirectTeacher: 'false',
  todoCount: '0',
  isEditorComment: 'false',
  isApprovedComment: 'false',
  isResolved: 'false',
  snapshotText: '',
  anchorContext: '',
  anchorText: '',
  anchorOffset: '0',
  mergedInto: '',
  isDeleted: 'false',
  viewCount: '151',
  text: 'I used to think that comments didn’t matter. I was wrong. This is important because [communities of discourse](http://benjaminrosshoffman.com/canons-what-for/) are an important source of knowledge. I’ll explain why I changed my mind, and then propose a simple mechanism for improving them, that can be implemented on any platform that allows threaded comments.\n\n[toc:]\n\n# Should there be comments?\n\n## Comments are optional.\n\nOrganizing discourse as a forum with comments introduces substantial structural rigidity. If you don’t like one of the regular posters’ content, too bad, it’s still cluttering up your feed. If you want to start contributing to the discourse, this comes at the cost of pulling everyone else’s attention, willing or no. In forums with high barriers to entry, this means that the move equivalent to “start your own blog” is not available to everyone. In forums with low barriers to entry, this can mean dilution by low-value posts, leading to the departure of discriminating readers. If standards are ambiguous, this can lead to an adverse selection process in which the contributors who are most conscientious about respecting community standards err on the side of not posting, and the least conscientious contributors flood the forum with low-value content, accelerating the process of pushing away the most discriminating participants.\n\nMy prior model of how written discourse should work was that people should publish in whatever venue they thought appropriate - often their own blog. If they find someone else’s writing interesting and want to comment on it, they can write their own post, and link to the thing they want to talk about. This has a few benefits. A link-based attention economy means that in order to get the attention of the readers of some content, you generally have to get the attention of the person generating the content. This means that higher-quality writing gets attention, and limits the effectiveness of low-quality trolling. Another benefit is that it allows for partly overlapping clusters. If a blog you like keeps linking to another blog, you can decide whether you like that one, and if you do, you can start reading it directly. Thus, you’ll be directed to blogs that are “nearby” in your local network, but not everyone reading your blog has to read the same set of nearby blogs.\n\nIn the early 2000s, a natural experiment happened. Americans on the right and left were both galvanized by the World Trade Center attacks and the consequent wars in Afghanistan and Iraq, and started writing. Two parallel blogospheres were formed - one on the left, and one on the right. And it so happened that some of the first prominent right-wing bloggers [didn't allow comments on their ](http://www.thedailybeast.com/articles/2012/07/16/most-comments-are-horrible-sites-look-for-ways-to-make-them-better.html). The result? The left-blogosphere developed parallel thriving communities on prominent blogs. The right-blogosphere had a “get your own blog” ethos, and were generous with their links and hat-tips. For more on this, see [Adamic and Glance 2005](http://www.ramb.ethz.ch/CDstore/www2005-ws/workshop/wf10/AdamicGlanceBlogWWW.pdf) (h/t [Kevin Drum](http://washingtonmonthly.com/2005/03/10/blogs-and-bloggers/)) and [Benkler and Shaw 2010](http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.170.2648&rep=rep1&type=pdf).\n\nMy first exposure to the blogosphere was mostly blogs on the right during the relevant period. When I heard tell of problems due to trollish commenters, and difficulties establishing clear standards for posting in forums, my initial response was, “Who needs a forum? If you have something to say, you should start your own blog.” I can no longer wholeheartedly insist that this is the whole solution. But I still think that the comments-links axis is an important one in discourse design, and it’s not obvious that the end of the spectrum “comments’ points towards is always better.\n\n## Comments matter.\n\nA friend recently expressed disappointment that an article they published in a forum got low-quality comments that they felt compelled to respond to. When I suggested posting on their own blog, and if necessary closing the comment section, they pointed out something I hadn’t properly considered:\n\n## Comments are a high-quality, high-sensitivity measure of engagement.\n\nIt’s great when someone links to your work - and perhaps linking would be more common without comment sections. It’s a strong signal that you’ve been heard, and someone thinks your message is relevant - but it happens rarely, and unless you’re already extremely popular, it won’t happen on most of your posts. It’s a bad feedback loop taken on its own; it measures the right thing, but gives extremely coarse-grained feedback. A more sensitive metric is website traffic - how many people did you get to look at your post? But this doesn’t tell you whether anyone was moved to do something on their own based on your post, just how many people felt moved to click through, and maybe share it on social media. It [favors feel-good posts](https://srconstantin.wordpress.com/2016/11/27/hiding-in-plain-sight/) and [outrage porn](http://slatestarcodex.com/2014/12/17/the-toxoplasma-of-rage/) over true insight and clear criticism. Judging by web traffic alone, my all-time “best” blog post is one about the [query language of the mind](http://benjaminrosshoffman.com/reading-writing-thinking-brain/). This probably happened because it was shared by some prominent figures in my community. But judging by engagement, [one of my first posts pointing out some specific problems with Effective Altruism](http://benjaminrosshoffman.com/effective-altruism-not-no-brainer/) seemed to be much better at starting productive conversations, based on the comment section. (It turns out to be my second most popular post of all time, but I couldn't have known that as quickly as I knew that I was getting good engagement.) As a result, I’ve written more posts like the latter, and gotten more in-person feedback that those posts were persuasive, than for posts on any other topic I’ve written on.\n\nA second reason comments are important, is that starting your own blog - or writing a whole blog post - is a pretty big deal when all you want to do is signal-boost an article you think is worth reading (upvoting or “liking” is a way to do this and only this, without interposing yourself between the reader and the content), or reply to a specific point that’s only relevant in the context of a particular article (in which case commenting is the natural solution). Oddly, the more hierarchically structured forums and blogs with comments welcome more interaction than the flatter structure of a purely posts-and-links blogosphere.\n\n# Improving comments\n\n## Selection vs treatment\n\nThere’s already been some discussion about how to make comments work better. For instance, Paul Christiano has [proposed](https://sideways-view.com/2016/12/02/crowdsourcing-moderation-without-sacrificing-quality/) a machine learning solution in line with his [approach to AI safety](https://medium.com/ai-control/model-free-decisions-6e6609f5d99e#.ldulpo9h4). Much of the discussion has been about efficiently promoting good comments and [detecting and removing bad actors](http://lesswrong.com/r/discussion/lw/o7b/downvotes_temporarily_disabled/). In short, it’s about improving the quality of observed comments through selection.\n\nI want to talk how to create, not selection effects, but treatment effects. I want to focus on making comments better - doing things that directly cause people who are trying in good faith to participate in the discourse to post better comments.\n\n## Problem: nitpicking\n\nOne problem that’s come up repeatedly in conversations about the quality of blog post comments is that they don’t respond to important points, and instead nitpick about minutia. I think this happens for a few reasons, including: It’s often easier to evaluate minor fact-claims than major claims. This is because many readers often aren’t comparing an article’s underlying model to theirs - they may not have a model - and so, look for details that it’s easy to say yes or no to. The obvious solution is to make it easier to identify and think about a post’s substantive claims.\n\n## Solution: tag claims\n\nThe Arbital team has recently implemented the feature of tagging claims made in an article. For instance, in Alexei Andreev’s recent [post](https://arbital.com/p/6vm/) about waiting to donate until the end of a fundraiser, there are links in the article to specific claims it makes or addresses, such as:\n\n - [6wp]\n - [6wm]\n\nWhen linking to my [blog post on GiveWell and "crowding out" considerations](http://benjaminrosshoffman.com/givewell-case-study-effective-altruism-1/), he adds a link to a related claim page:\n\n - [6y2]\n\nI’m pretty excited about this infrastructure. It gives the post author to foreground the considerations they think are most relevant, and gives commenters a set of default topics to argue about.\n\nIt also accomplishes the secondary goal of making comments more of a lasting, accessible record. If the comments about a claim are scattered over several related articles relevant to the claim, and also mixed together with comments on other topics, it can be hard to know whether you’ve seen the important discussions on a given topic. If, on the other hand, all those articles are tagged with the same claim, then you need only click through to the claim page, and you’ll find a record of comments by readers of all of the relevant posts - and only the comments relevant to this claim.\n\nHowever, Arbital isn’t an universal platform, and many people want to maintain their personal blogs or post to a public forum allowing comments. What can we do to improve comments there?\n\n## Threaded comments enable tagged claims.\n\nIn my [post](http://lesswrong.com/lw/o95/be_secretly_wrong/) advocating publishing private opinions on secret blogs, I posted three comments, one for each claim I wanted to make. Each comment ended with: "If you want to discuss this claim, I encourage you to do it as a reply to this comment.” Someone asked me to put the claim comments in boldface so they’d be easier to find. (For another example, see my comments on this post as cross-posted at [LessWrong](http://lesswrong.com/r/discussion/lw/obv/improve_comments_by_tagging_claims/) or my [personal blog](http://benjaminrosshoffman.com/improve-comments-by-tagging-claims/).)\n\nThe post didn’t get a huge number of comments but they felt maybe slightly more on-topic than usual. My claim-comments didn’t prevent people from introducing new threads, but they might have generated relevant responses that wouldn’t have been written otherwise, and they mostly got comments on the same topic grouped together. If you’re writing your own posts, whether on something like a forum or other group publication, a personal blog or website, or just ordinary social media, I encourage you to try this. Let me know how it goes.\n\n',
  metaText: '',
  isTextLoaded: 'true',
  isSubscribedToDiscussion: 'false',
  isSubscribedToUser: 'false',
  isSubscribedAsMaintainer: 'false',
  discussionSubscriberCount: '2',
  maintainerCount: '1',
  userSubscriberCount: '0',
  lastVisit: '',
  hasDraft: 'false',
  votes: [],
  voteSummary: 'null',
  muVoteSummary: '0',
  voteScaling: '0',
  currentUserVote: '-2',
  voteCount: '0',
  lockedVoteType: '',
  maxEditEver: '0',
  redLinkCount: '0',
  lockedBy: '',
  lockedUntil: '',
  nextPageId: '',
  prevPageId: '',
  usedAsMastery: 'false',
  proposalEditNum: '4',
  permissions: {
    edit: {
      has: 'false',
      reason: 'You don't have domain permission to edit this page'
    },
    proposeEdit: {
      has: 'true',
      reason: ''
    },
    delete: {
      has: 'false',
      reason: 'You don't have domain permission to delete this page'
    },
    comment: {
      has: 'false',
      reason: 'You can't comment in this domain because you are not a member'
    },
    proposeComment: {
      has: 'true',
      reason: ''
    }
  },
  summaries: {},
  creatorIds: [
    'EricRogstad',
    'BenjaminHoffman'
  ],
  childIds: [
    '75t'
  ],
  parentIds: [],
  commentIds: [
    '72g',
    '72h',
    '72j',
    '72k',
    '72l'
  ],
  questionIds: [],
  tagIds: [],
  relatedIds: [],
  markIds: [],
  explanations: [],
  learnMore: [],
  requirements: [],
  subjects: [],
  lenses: [],
  lensParentId: '',
  pathPages: [],
  learnMoreTaughtMap: {},
  learnMoreCoveredMap: {},
  learnMoreRequiredMap: {},
  editHistory: {},
  domainSubmissions: {},
  answers: [],
  answerCount: '0',
  commentCount: '0',
  newCommentCount: '0',
  linkedMarkCount: '0',
  changeLogs: [
    {
      likeableId: '0',
      likeableType: 'changeLog',
      myLikeValue: '0',
      likeCount: '0',
      dislikeCount: '0',
      likeScore: '0',
      individualLikes: [],
      id: '21189',
      pageId: '711',
      userId: 'EricRogstad',
      edit: '4',
      type: 'newEditProposal',
      createdAt: '2016-12-31 08:31:33',
      auxPageId: '',
      oldSettingsValue: '',
      newSettingsValue: ''
    },
    {
      likeableId: '0',
      likeableType: 'changeLog',
      myLikeValue: '0',
      likeCount: '0',
      dislikeCount: '0',
      likeScore: '0',
      individualLikes: [],
      id: '21157',
      pageId: '711',
      userId: 'BenjaminHoffman',
      edit: '0',
      type: 'newChild',
      createdAt: '2016-12-30 17:56:39',
      auxPageId: '75t',
      oldSettingsValue: '',
      newSettingsValue: ''
    },
    {
      likeableId: '0',
      likeableType: 'changeLog',
      myLikeValue: '0',
      likeCount: '0',
      dislikeCount: '0',
      likeScore: '0',
      individualLikes: [],
      id: '21024',
      pageId: '711',
      userId: 'EricRogstad',
      edit: '2',
      type: 'newEdit',
      createdAt: '2016-12-21 03:13:44',
      auxPageId: '',
      oldSettingsValue: '',
      newSettingsValue: ''
    },
    {
      likeableId: '0',
      likeableType: 'changeLog',
      myLikeValue: '0',
      likeCount: '0',
      dislikeCount: '0',
      likeScore: '0',
      individualLikes: [],
      id: '21008',
      pageId: '711',
      userId: 'BenjaminHoffman',
      edit: '1',
      type: 'newEdit',
      createdAt: '2016-12-20 17:19:41',
      auxPageId: '',
      oldSettingsValue: '',
      newSettingsValue: ''
    }
  ],
  feedSubmissions: [
    {
      domainId: '2069',
      pageId: '711',
      submitterId: 'BenjaminHoffman',
      createdAt: '2016-12-20 17:19:41',
      score: '79.50669989821867',
      featuredCommentId: ''
    }
  ],
  searchStrings: {},
  hasChildren: 'true',
  hasParents: 'false',
  redAliases: {},
  improvementTagIds: [],
  nonMetaTagIds: [],
  todos: [],
  slowDownMap: 'null',
  speedUpMap: 'null',
  arcPageIds: 'null',
  contentRequests: {}
}