Discuss: Comments Feature in FastPages

Many people are using Disqus, however, they show adds to users, and have a reputation for showing particularly click-baity ads such as “your information has been compromised”, etc. Therefore, I am inclined not to use or recommend them for fast pages.

Any thoughts? Suggestions? Considerations?


cc: @jeremy @xnutsive


Cure my own itch perspective: if anything, I’d use github issues as comments. A reader wants to reach out because they couldn’t run the post and reproduce the results, or they have suggestions? Open an issue. Seems natural.

Building a tool that other people use perspective:

  1. Do folks really need comments? Even if we add a comment engine, should it on or off by default?
  2. Are folks scared of posting github issues as comments and is this solution too complicated?
  3. For non-open source blogs, people will need to create a repo for their blog comments to be stored in. This can be setup easily with github api, but adds complexity to the whole system.
  4. Discuss will be easier to customize since some jekyll themes are already Discuss-aware and work with it.

So I’d definitely do this on my own blog with github issues (not necessarily utterances, but probably with it), but as a general option, I’d probably go with disabled-by-default, but optional Discuss based comments.

1 Like

Thanks for the perspective @xnutsive I took your advice and opened a PR adding support for this using utterances in fastpages, but it is turned off by default.

It looks really great by the way! And I also really love the fact that it is open-source, ad-free, and you own your data (keeping with the tenants of fastpages)


That looks cool! I love the fact that if you choose to open source the blog repo itself, you can use the same repo issues for comments. Interesting to see how that would work out.

1 Like