The problem isn't having comments on your blog, it's having locally scoped identities to comment on your blog. It essentially removes all cost for "destructive" participation, whether it be spam, harassment or other trolling. This is solved either by moving commenting entirely off-site to a larger network, or by using identities from a larger scope.
Shameless plug: I built Cactus Comments ( https://cactus.chat/ ). It's an open-source comment system federated on the Matrix ( https://matrix.org/ ) network. This means you can use your Matrix identity to comment on any site that uses Cactus, without the tracking of something like disqus. Works well with static site generators too.
In particular, any federated identity provider has a problem for this use case in that malicious actors can simply create their own domain - or multiple - and spam/troll from those. Blacklists essentially don't work as long as new domains can be created, so you end up with a whitelist, which kinda counteracts the federation concept.
It needs something where getting blemishes on your ID is actually something you want to avoid. And where fresh IDs is not effective to bypass this.