The Case For Comments

[osteophage]

Given that comments can be controversial on the indie web, it’s worth pointing out the use cases for comment sections as a feature. Comment sections are particularly suited to allowing for brief high-context replies, supporting public multi-way interactions, setting a (relatively) lower threshold for participation, and allowing the blogger to define the parameters for a discussion. These are use cases that cannot all be adequately addressed by commonly-suggested alternatives such as response posts or email. 

Crossposted to Pillowfort and my personal site. 

 

For reference, here is some of the context for making this post:

• How to Hit the Target by Missing Completely, a followup about the negative responses to They Paved Paradise and Put Up a Static Site
• Why Comment Sections Suck, a response post in objection to I want to comment on your blog post
• Try writing posts, not comments and a response In defence of comments
• Responses to this 32BC forum thread

Discovering that comments could be this controversial came as a surprise to me because I come from a blogging tradition where comments are generally valued. We speculate on reasons why comment rates aren't higher, we ask which factors contribute to comment culture, and we generally express a preference for comments over email. This relationship to comments is second nature to me.

Given my own investment in comments, I’ve noticed how often this feature has been deprioritized in conversations about indie web onboarding. When people talk about how the indie web should be easier, the suggestions for easy blogging options that are actually indie tend to be Pika, Bearblog, and Pagecord. These options may be fine for those who just want a place to publish some text, but all three of them lack a comment section, and that’s a limitation worth taking seriously as a deterrent to participating in the indie web.

So on that note, here are some scenarios, advantages, and priorities that justify an investment in comments.

Brief Replies With Immediate Context

Comment sections are good for the kind of replies that aren’t enough to warrant a whole separate response post. A response post needs to begin with a descriptive link along the lines of “Yesterday, a blogger posted XYZ,” and a response email needs to begin with a preface to explain what prompted the email. This amount of preamble can feel like overkill in a lot of situations. For example, when answering a question, cracking a joke, comparing notes, or just goofing around, sometimes a comment is the best fit.

Public Multi-Way Interactions

Comment sections are good for facilitating better, richer discussions by allowing readers to see previous responses and strike up a conversation with each other. They can look through to see what’s already been offered as recommendations or advice, chime in to endorse or dispute others’ suggestions, and just generally build on each other rather than always starting from square one. These are benefits that cannot be as easily replicated with one-on-one interactions like email.

For examples, see for instance this discussion about publishing and genre, this discussion of streaming services, or some of the comment threads in which I have encouraged folks to make a website.

Lower Threshold to Participation

Comment sections are good for when you want a lower barrier to entry and more participation rather than less. For example, making a post with a comment section can be a decent way to learn more about other people’s experiences with barriers to the indie web. If I had made a post like that and just told people to email me, I doubt even half as many people would have responded, which is undesirable when I’m trying to cast a wider net and get a breadth of responses.

Managed by the Blogger

Comment sections are good for allowing a blogger to set their own parameters on how to discuss or engage with a given post, with more authority than would be appropriate when the blogger is a guest in someone else’s space. For example, when sharing a blogpost link on a forum or a chatroom, the blogger is bound by local rules that take priority. If a blogger wants to set their own terms of engagement, then a comment section can be the best fit.

For example, in my post In Defense of the Pillowfort Reblog System, I preemptively set some parameters on what kind of responses I’d accept on that post because I was putting forward an opinion on a contentious issue that had already been heavily discussed. I wanted to ask people to engage with my specific points, rather than just airing their thoughts in general. Situations like these are due cause for wanting a designated comment section where a blogger’s own terms of engagement can be enforced.

So, to reiterate:

Comment sections have distinct use cases that cannot be adequately replicated by the alternatives. Comments are well-suited to brief or high-context replies, public multi-way interactions, and casting a wide net. They also grant bloggers the authority to set parameters on how to engage, without overstepping on someone else’s turf. Other communication methods can slot in for some of these, but none of them can stretch to really cover all the advantages all at once, which is why comment sections are still important for those who want them.

Note: guest comments are screened. This means that if you submit a comment without an account, it will not be published until manually approved.