disqus基础模式

[JasonLin1230]

• 故障：disqus基础模式暂时无法实现，cdn反代源站504

• 原因：disqus.com源站设置了保护，无法直接反代

• 解决方案：现在，我需要一个国外的服务器作为中间层进行跳转

[VincentTam]

Hi, this is the maintainer of @staticmanlab, a public instance of Staticman, which brings comments to static web sites.

Disqus has a plethora of shortcomings that deter many bloggers, say

1. privacy issues
2. slow load speed
3. no markdown support
4. poor SEO
5. high cost of migration

ℹ️ You may see Pelican-Elegant/elegant#288 for more links to posts about migrating from Disqus.

You may avoid these problems by switching to static comments powered by Staticman, which makes use of GitHub/GitLab Pull/Merge Requests. 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.

For working examples of Staticman, you may see

1. a popular Jekyll theme called Beautiful Jekyll, which has incorporated my port of Minimal Mistake's Staticman integration.
2. zcrc.me Source: a personal Jekyll blog with Markdown support and preview.
3. my personal blog Source powered by my tweaked Beautiful Hugo, with nested comments and comments preview.
4. a group of my Staticman demo sites on Framagit.

ℹ️ There're many ways leading to Rome, like JAM stack, Netlify Comments, etc.

[JasonLin1230]

Hi, thank you for your suggestion, I will seriously consider it.:grin:

[VincentTam]

Hi, thank you for your suggestion, I will seriously consider it.

Nonetheless, the official Staticman instance isn't quite stable, as reported in eduardoboucas/staticman#285 and eduardoboucas/staticman#296. To get Staticman in minutes, I suggest following the steps in Beautiful Jekyll, then read the outdated official docs to get an idea, and then pick your favourite theme from my list of demo sites.