kidoniko-blog / pinglun

0 stars 0 forks source link

一期一会:人间走一遭,不过一秒万年和万年一秒 | 满地都是小星星呐 - KidoNikoのBlog #1

Open kidoniko-blog opened 5 years ago

kidoniko-blog commented 5 years ago

https://kidoniko.coding.me//post/yi-qi-yi-hui-ren-jian-zou-yi-zao-bu-guo-yi-miao-wan-nian-he-wan-nian-yi-miao/

耽美文学爱好者/邪恶暴政对抗者/魔都/小透明/MBA11坚守者
推荐食用:中篇小说《满地都是小星星》陆+ 音乐 夜空中最亮的星 Acappella版

我们总为了挣扎而低落,却又因为每一次间歇性的幸福到来而撑过。如此生存着。
——《满地都是小星星》陆
厚德博學 敬業樂群 ——北邮校训
人生就像玻璃窗上的苍蝇,前途一片光明,却找不到出路。

kidoniko-blog commented 5 years ago

调个gitalk才知道程序员们调通一个bug是多么的不容易了

kidoniko-blog commented 5 years ago

gitalk依赖于Github的仓库里的issue,我不了解申请OAuth的用途,错以为要申请到Coding.net的OAuth,此一坑。Gridea的对接设置里面(也就是网站这边的调用环节)的仓库和Owner不知道填哪边的,此二坑。期间改到Disqus调通了,发现被墙,用不了,此三坑。啊啊啊

kidoniko-blog commented 5 years ago

总结一下,Gitalk只不过利用一下github的issue功能实现评论,跟我网站挂在coding上没半毛钱关系,而我网站这边调用的时候当然要填上git上对应的repo和github的用户名。就这点破事我个小透明搞了一上午啊啊啊啊啊。所以再傻瓜的东西给我用还是不够傻瓜啊。

VincentTam commented 5 years ago

gitalk依赖于Github的仓库里的issue,我不了解申请OAuth的用途,错以为要申请到Coding.net的OAuth,此一坑。Gridea的对接设置里面(也就是网站这边的调用环节)的仓库和Owner不知道填哪边的,此二坑。期间改到Disqus调通了,发现被墙,用不了,此三坑。啊啊啊

Hi, this is the maintainer of @staticmanlab, a public GitLab instance of Staicman. Here's some shortcomings of some common third-party commenting systems.

  1. Gitment, Gitalk and Utterance support only GitHub, and they require user login before commenting. This can scare away many non programmers from leaving a comment to your posts. Besides, comments are part of the site's static content, not a software package problem. As a result, using GtiHub issues for comment storage is wrong in principle and bad in terms of SEO.
  2. Commento is not free as in free beer. For a personal blog with small traffic, you might find a monthly fee of $5 too expensive.
  3. Disqus and Isso contain a 3rd-party script to be loaded during page rendering. The code block for loading each of them shows that the static comments are not rendered as static HTML code. This hinders search engines from grabbing the comments, which are part of the site's content. As a result, that leads to suboptimal SEO.
  4. Disqus is difficult to access for non programmers in the PRC, as reported in https://github.com/Huxpro/huxpro.github.io/issues/258#issuecomment-430842480.

To see more reasons for migrating from Disqus, you may view

  1. https://victorzhou.com/blog/replacing-disqus/
  2. https://old.reddit.com/r/programming/comments/b9022a/switching_off_of_disqus_reduced_my_page_weight_by/
  3. https://medium.com/remys-blog/ejecting-disqus-4120e9985823

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.

Some tutorials for configuring Staticman with GitHub/GitLab repo:

  1. 利用StaticMan为博客添加评论功能
  2. 使用Statiman给博客提供评论功能(二)

:information_source: There're many ways to Rome, say JAM Stack, Jekyll AWS comments, etc.