Then I built an alternative using free Cloudflare Worker
https://github.com/est/req4cmt
It's a simple service that transform comment POST form data to JSON, append to a .jsonl file, then do a `git push`
It renders comments by `git fetch` from a .jsonl file from a remote repo, or simply via raw.githubusercontent.com if your repo was hosted by Github.
The advantange over Github issue/discussion based comment plugins:
1. All data is stored a .git
2. no login of any sort
Github OAuth login might leak all your repo data along with your `access_token` to the plugin provider.
The `git push` works for any remote. You can choose github/gitlab or whatever.
isn't that better IF the commenter has a GH account? (if you're writing a personal tech blog, then it's not a problem, your readers are Github users already)
Github issue or discussion based plugins require OAuth
If you look closely, some OAuth scope requires "Act on your behalf". Others require "repo" scope which means read your private data.