After spending half a day implementing and testing Disqus integration on this site, and another half day Googling people’s experiences and opinions about Disqus, I decided, endlich, not to use it.
In its early days, this site was a wiki, and a few friends had access to the “secret” subdomain where it was published read-write. We had a great time for a couple of years having conversations on the site about the site itself and the subjects that it attempted to “tackle”. I miss having conversations here, but since I really wanted to have the site be statically generated (and hosted), any dynamic content had to be hosted elsewhere.
Thankfully, there are several (at least three) options for this kind of commenting-system-for hire: Disqus, Intense Debate, and Livefyre Comments. Before researching the pros and cons of Disqus I had never heard of Intense Debate or Livefyre. I immediately wrote off Intense Debate when I found out it was an Automattic project – I’m not a fan. And Livefyre? Well, I had never seen it “live” on the web, which suggested that the community of commenters that I would be drawing on would be much smaller than that available at Disqus. So really Disqus was the only service I seriously considered. Hence, the rest of my comments here name Disqus, but the other services have most of the same features and, importantly, problems.
Let’s step back and consider what these services really are. Disqus is basically a social networking system for hire. They do house calls: you integrate the service into your site, rather than having the conversation occur, say, on Facebook. It’s a bit like having your own Facebook – yes, with all the privacy bugbears that that entails.
I’ve already muddied the waters by using suggestive, but false, language. Disqus is “for hire” in the sense that you can bring their Facebook-like experience to your site, but, importantly, Disqus is “free”. Cost-free, that is. Just like Facebook, Disqus is truly a social network, and has all the problems that social networks have. Why is it “free”? Because by hosting your comments there they get access to a ton of immensely valuable behavioral metadata. And they sell it to advertisers.
So by using Disqus your commenters – your community – become a product.
If that weren’t bad enough, there are serious, unresolved privacy and censorship issues with the service.
First, all of a Disqus user’s comments are aggregated in one place – on their profile page on disqus.com – and are public. While this might not sound like a big deal – they are commenting in public after all – having all their comments together in one place makes it much easier to profile someone, to stalk or troll them, to “infiltrate” all the places they comment and annoy or harass them. If their comments weren’t public, or weren’t all aggregated, it might be possible but would much harder to do this; and making casual stalking or harassment harder seems like a good thing.
Second, it’s possible to “follow” a commenter, like on Twitter. And, as far as I understand, it’s not possible as a commenter either to see who is following you, or to block them. As above, this can easily be abused for nefarious purposes, such as stalking or trolling. If you follow someone, you can see in real-time where they are commenting, and jump on or harass them. You can easily make using Disqus so painful for someone that they stop using. Harassing someone for personal reasons makes this “feature” troubling, but if someone misuses it for political ends, then it becomes truly chilling.
Third, Disqus uses the services of a company called Impermium, who use machine learning techniques (like everyone else) to combat spam, profanity, and hate speech. The trouble with this is that, as a user of Disqus (either as a commenter or publisher) you are now forced to consent to the black-box intermediation of a basically unknown company. As Evgeny Morozov puts it, in his awesome, mind-blowing book To save everything, click here:
... a single Californian [sic] company makes decisions over what counts as hate speech and profanity for some of the world’s most popular sites without anyone ever examining whether its own algorithms might be biased or excessively conservative. Instead of celebrating the mythical nirvana of disintermediation, we should peer inside the black boxes of Impermium’s spam algorithms.
I find this troubling. (Curiously, it appears that Impermium has been acquired by Google. That will either soothe your rattled nerves, or make you even more suspicious. ;-)
Lastly – and problably “leastly” – using any outside commenting service has the usual “cloud computing” problems: your data (comments) is on someone else’s servers, and you have to trust that they won’t lose, or, more disturbingly, secretly modify them. If there were some kind of integrity hashing that could be relied on, that would help, but then, where are the hashes kept? Now you have to build a dynamic content system just to check the dynamic content system that you wanted to bring in...
As a counterpoint to this last point, people use Google Docs all the time and have no problem with it. Ditto other cloud services. It is simply part of the bargain we make when outsourcing to cloud providers.
In addition to privacy, and perhaps censorship, issues, people have usability issues with Disqus. By using an
<iframe> element to contain the rendered comments Disqus makes it very hard to style the comments to match the rest of your site. Why do they do this? Probably to make it hard to remove or alter their branding – but it’s pretty arrogant.
Other people complained that their readers had difficulty commenting. Signing in was problematic, or trying to use the Guest mode was awkward. Here’s a forum post that outlines several other issues.
Try Googling “disqus failure” and “i hate disqus”. You’ll see what I mean.
I’d love to hear feedback about Disqus – maybe positive experiences that outweigh the negative, or evidence that I’ve got the facts wrong about privacy or security. For now, you’ll have to use the “Send feedback” link at the bottom of the page, which simply sends me an email. Maybe someday there will be a better way to comment here. ;-)