Going full DevOps just for blog comments is not great ROI. If I couldn't use Disqus/FB Comments and was forced to self-host my own blog comments on my static blog, I'd just remove blog comments altogether.
Going full DevOps just for blog comments is not great ROI. If I couldn't use Disqus/FB Comments and was forced to self-host my own blog comments on my static blog, I'd just remove blog comments altogether.
Sure, I could’ve just live without comments, but that’s again forcing the discussion into other „centralized“ communities like Twitter or Facebook. So I threw in the time to create and set up Schnack.js to have the best of both worlds: a static no-hazzle website with self-hosted comments.
Also I grew up in a time where virtually everyone would have self-hosted comment systems on their static self-hosted websites. Only they used to be called guestbooks then. Working on Schnack really reminded me of that magic time.
I’ll give it a try during holidays.
Doesn't mean others wouldn't throw up a comment system somewhere, in the knowledge that the most important part of their site (the content) isn't affected if it doesn't keep up and they exactly do not need to invest the time and energy to "go full DevOps" for that.