Letting go of giscus

Although giscus can be an excellent commenting system for many static websites, it no longer serves that purpose for this one.


Back in March, I began using the giscus commenting system on this site, mainly as an experiment. Although having it around was geekily interesting over the succeeding seven-and-a-half months, I’ve now removed giscus from this site.

Here are the reasons why, in no particular order:

  1. It’s a load — The hosted giscus app, which runs on Next.js, dumps onto a page a few hundred kilobytes of JavaScript and, where comments are available, other content. On some sites, that might be a negligible percentage of the page’s total load; but, for this more spartan one (which, I’m pleased to say, is a “member” of the 512KB Club), that’s a big tub of guts. While I’ve previously described some workarounds for that, they work poorly or not at all in certain browsers.
  2. It requires using GitHub — To me, giscus’s dependence on the GitHub Discussions API doesn’t matter, because I suspect my typical visitor either already has a GitHub account or has no objections to getting one. Still, I’m seeing renewed anti-GitHub sentiment these days, so I can’t pretend that it’s not a source of friction for a non-trivial number of tech-savvy visitors.
  3. It requires kneecapping my CSP — To allow giscus to work, the site must allow inline scripting. However, that critically weakens the site’s Content Security Policy (CSP). Indeed, I said back in May that “if I stop using giscus, that’ll likely be one of the key reasons why.” And so it is.1
  4. The level of participation hasn’t been worth it — This is related not to giscus in particular but rather to commenting systems in general. Regardless of which such system I’ve ever used on this site, I’ve just never received enough comments to make it worth putting up with nits such as the items noted above. And that’s not just because of the site’s low traffic; I’ve found it true even when a post suddenly goes semi-viral because, say, it was the subject of a Hacker News thread or received mention on someone else’s widely seen Twitter account.
  5. The email route is still here — When I first began putting the “Reply via email” button at the bottom of each post, I hoped for the result reported by other site owners who had dumped commenting in favor of reply-via-email: i.e., more thoughtful and nuanced interactions with my readers than would be likely with any commenting system, giscus or otherwise. Happily, that’s what I’ve had ever since.

All this aside, I do still recommend giscus as a fine, easily implemented, and completely free/open-source commenting system for your static website if you’re willing to overlook, or otherwise unmoved by, the items to which I objected above.

Update, 2023-06-21: In June, 2023, I reversed this decision and began using giscus again.

  1. However, in all fairness: while dropping giscus allowed me to remove unsafe-inline from the site CSP, the Pagefind-powered site search still requires unsafe-eval. I’m not happy about that, either, but at least Pagefind’s documentation holds out hope for a future solution. Besides, in all candor, I consider site search a much more mission-critical capability as compared to commenting. ↩︎

Reply via email
View comments