zlacker

[return to "I’ve removed Disqus. It was making my blog worse"]
1. est+h4[view] [source] 2025-09-30 09:23:55
>>ry8806+(OP)
I ditched Disqus for the exact same reason, too many ads

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.

◧◩
2. Cthulh+dd[view] [source] 2025-09-30 11:07:15
>>est+h4
.jsonl files are fine for low volume comment threads I think, but others have already mentioned the use of git for storage. Would sqlite or Cloudflare's own D1 (SQLite compatible, also available in their free plan) work as an alternative?
◧◩◪
3. est+Op[view] [source] 2025-09-30 12:58:52
>>Cthulh+dd
> Would sqlite or Cloudflare's own D1 work as an alternative

They certainly do, but for they same reason why people chose static site generators like Hugo over Wordpress, I'd like complete control of full data.

The good value of static-hosted comments is that you `git clone` for backup and `git push` for redudency.

I also dislike managing DBs. Think of all those mess with backups, migrations, imports, exports, difference between mysql/pg/sqlite/d1. Tons of operating cost just for the sake of few blog comments

It's just a bunch of .jsonl files, the last resort is direct inline those .jsonl into .html files when generating

[go to top]