Isso VS utterances

I deploy my static blog via rsync. I also have Isso [0] on it. No need for a back-end web framework or anything.

[0] - https://isso-comments.de/

I use Isso myself, which is pretty easy to implement into a site created with Hugo.

I just use isso (https://isso-comments.de/). It's simple and elegant, easy to integrate, and just works without requiring people to login/signup, and allows moderation.

If I were you, I would consider whether a self-hosted solution such as Isso Comment might also be an option. I personally don't like it when my comments are stored at third parties.

I would use one of the static website generators for such a page. I use Hugo myself. If you want a comment function, Isso would be worth a look.

Isso (Self-hosted, Python) (tutorial)

I have found isso to be good for static sites. It allows posters to remain anonymous (which encourages more open discussions) and is self-hosted and simple.

https://posativ.org/isso/

I was looking into both customer conversation and chat recently and I mixed things up. Sorry.

The one I looked at for 'chat' : https://github.com/posativ/isso

We can use utteranc.es, a lightweight comment widget built on GitHub Issues to integrate authed comments in our blog.

utterances (open-source)

Typically, a comment requires server side code and a lot of messy management. It’s a pain. These comments rely on a tool called utterances. Utterances uses GitHub’s issue tracker which was designed to track bugs, as part of that it includes extensive comment and discussion capabilities. If an issue doesn’t exist, utterances will automatically create that issue for you. It created this issue for the comments in this page...

Go to https://utteranc.es and follow the instructions to set up the commenting system.

Giscus drew significant inspiration from utterances, which utilize an issue-based comment system instead of discussions. I experimented with utterances initially, but I found it less convenient due to its reliance on an issue tracker for conversational purposes.

If you're building a blog for developers, you can use a third-party commenting service that requires login with github, for example https://utteranc.es/

On the comment note, this might be useful: https://utteranc.es

Not super out-of-the-ordinary, but I host my personal blog on GitHub Pages, is built with Actions, and use Issues (via Utterances) for the post comment system.

Utterances - A lightweight comments widget built on GitHub issues. Use GitHub issues for blog comments, wiki pages and more!

Can you elaborate why 3, a git-based comment system, is beneficial? When do comments need to be merged?

PS There is a small web sdk that enables comments on sited via github issues. see https://github.com/utterance/utterances