The new blog system Meteor needs a comment system. Theoretically, it could directly integrate with mx-space's built-in comment system, but my skills are too lacking, so I chose to directly integrate the new comment system Artalk. Since Artalk supports multi-site, it's only natural to replace the comment system Twikoo on Legacy with Artalk.
Artalk provides features such as login and comment notifications, which are not implemented by the API provided by mx-space. So, to solve it once and for all, let's just use Artalk.
Twikoo was what I encountered when I first built my own Hexo blog. At that time, its features were already becoming quite complete, and it had the following very valuable characteristics:
It was precisely because of these characteristics that it became my top choice for a comment system, and it has accompanied me for four whole years (2021-2025).
In 2024, I noticed Artalk. It supports multi-site and many features—I felt a sense of excitement.
However, it has a hard requirement: you must own a server.
To be honest, I wanted to replace Twikoo back then, but I didn't have a server!
The solution I tried was: Deploying Artalk image via Tencent Cloud SCF Cloud Function + Mounting Tencent Cloud File System for storing Artalk configuration files + Cloudflare Worker reverse proxy to remove the mandatory download header added by Tencent Cloud.
The whole process was quite bumpy, and then...
Finally gave up, yeah.
The week before last, I was very fortunate to receive a $200 Digital Ocean credit through the GitHub Student Developer Pack.
This week, I made up my mind to replace Twikoo with Artalk.
And that's how this article came to be.
Goodbye, Twikoo!
Hello, Artalk!