Moving my blog comments to Giscus

In my last post, I explained how I added a comment system to my blog using Utterances. It worked well: lightweight, simple, and tied directly to GitHub Issues. But I've now switched to Giscus.

Why the change?

Utterances uses GitHub Issues, which is fine for basic comments, but it has limitations. Replies are scattered around and you can't react to other comments.

Giscus, on the other hand, uses GitHub Discussions. You can easily reply to other comments and replies are organized nicely under the parent comments. You can react to other comments. And issues are focused on, well, issues.

What does this mean for you?

If you have a GitHub account, you can still comment just like before, but now you can reply to others, react with emojis, and join a proper discussion thread. It feels more like a community space than a feedback box.

What did I learn?

Sometimes the simplest solution (Utterances) is the right starting point. But when you want richer interaction, Giscus is the natural upgrade. It keeps my site lean and accessible, while giving readers more ways to engage.

All utterances issue threads have been made Giscus discussions.

Comments are now powered by Giscus, right below!

(Real ones will know that Utterances was used for only 1 day...)