Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Migrate from Disqus #118
Hi, this is the maintainer of @staticmanlab, a public GitLab instance of Staicman. #107 has added Disqus support. However, please revert it due to some shortcomings of some common third-party commenting systems.
To see more reasons for migrating from Disqus, you may view
You may avoid these problems by switching to Staticman, which makes use of GitHub/GitLab Pull/Merge Requests instead of issues. Under Staticman's model, static comments are YML/JSON files stored in the remote GitHub/GitLab repo (usually under data/comments, configurable through the path parameter in root-level staticman.yml), and through a static blog generator (Jekyll/Hugo/etc), the stored data are rendered as part of the content. This gives a total ownership of a static site's comments.
Thanks for raising your concern. However, I don't like the idea of storing user comments in my repository. At minimum, each post should then have an explicit confirmation box requiring users to agree their data is owned fully by me.
Disqus has a slight performance impact but for example Google Analytics has worse. Seeing how widely used platform Disqus is and being able to inject both the discussion area and comments count as simple React components makes the tradeoff acceptable. The Lighthouse score for SEO is still at 100 so there's no reason to worry about it either.