This scenario is mostly relevant when Discourse is used for embedded comments on a parent website, not necessarily when Discourse is used as a completely standalone discussion community site.
Did people even read the article before commenting on it?
It’s tough, becase as you will learn from that experiment, for many, many people, the answer is, sadly, no.
I’ve been floating some ideas to combat that effect for quite some time now, and I noticed that one of the ideas – a literal quiz you have to answer before you’re allowed to comment on the article – was finally implemented by someone, somewhere!
Of course this does not scale at all, unless you fancy the idea of writing a custom quiz for every single blog entry you post. But it’s a fun concept to explore!
I think table stakes here are to visually indicate new users in some way. Discourse has done this since forever using a light grey “dim” username to indicate the new user is sort of ghostly and not fully substantiated because they just arrived.
In addition to the mandatory quiz, some other ideas I had that I think might also work:
Show, for new users, how much time they spent reading the article next to their username when they comment.
Steam does this to great effect. For every review of a game on Steam, you’ll see a small indicator next to the user indicating how much of that game they actually played. This is quite brilliant! When you see a negative review from someone that spent 10 minutes with a game, that is a very different thing than a review from someone who spent 10 hours with it.
This is a little hairy because it requires the parent site to reliably track read time somehow.
Show, for new users, how many other posts they read in the topic next to their username when they comment
This is a related technique that’s a bit more meta, since it is about the discussion and not the original article. It would certainly let you know how interested commenters are in listening to other commenters (and not potentially duplicating or rehashing old topics) before chiming in with their own comments.
Of course you could do both #1 and #2 to cover all your bases; show both article read time in minutes, and comment read time (plus count) in minutes.
Require users to read every comment (or a percentage of comments) before posting their own comment
This is certainly more draconian than the quiz, but also doesn’t require a custom set of content for every blog post. The only thing that gives me pause here is that, as the discussion gets bigger and bigger, this is an almost impossible bar. If there are 500 comments, is it realistic to expect a new commenter to read all 500 before posting? So perhaps a cap is in order; read at least 100 comments before being allowed to add a comment of your own, or something like that?
Require users to rate a few random comments (by other new users?) before posting their own comment
This is the path of Civil Comments, but it’s unclear how dedicated they are to this approach as they appear to have pivoted pretty hard away from being a commenting system. I still love this approach overall, and I think it might scale better than the other 3 options above. I like the idea of being forced to introspect a bit about what others are trying to say before commenting, and you could cleverly get new commenters to vet each other in this manner, by restricting the rating to just other new commenters versus long time veterans who are unlikely to be doing anything untoward.
Magical Mystery Machine Learning
There is also the “magical machine learning” path here, where services can vet a comment to see if it’s somehow toxic.
This is more akin to the spam filtering we do with Akismet, but conceptually it’s very similar.
What do you think of these ideas? How else can we combat the Ars problem, where people write comments without spending any time reading? Any other concepts I’ve missed?