4 ms·

I looked into using Utterances a while back, but decided against it. From my blog post [0]: This product requires an external server to be up and online at all

by pknopf 7y ago

I looked into using Utterances a while back, but decided against it. From my blog post [0]: This product requires an external server to be up and online at all times. And while they do promise to be always free without ads, they don't promise to be always available. And while they are open-source and I could always decide to host my own Utterances server/bot, I'd prefer to host nothing at all. This isn't a super deal breaker, because in the end, all content is stored in GitHub Issues. [0] https://pknopf.com/post/2018-10-13-comments-for-static-sites-using-github-issues/ https://pknopf.com/post/2018-10-13-comments-for-static-sites...

machbio 7y ago
you could have pushed solution a bit more to create the github issue when creating blog posts - like use a github token to generate issue when the issue does not exist for blog posts.. utterances feature that I liked is the bot that creates the issue for you automatically and also scans the github repo for comments based on title..
- pknopf 7y ago
  > you could have pushed solution a bit more to create the github issue when creating blog posts I guess, if my solution were a "product", as opposed to a one-off.