Why Say Goodbye？

Main Reasons

The new blog system Meteor needed a commenting system. In theory, it could directly integrate the built-in comment system of mx-space, but since my skills were lacking, I chose to directly integrate the new comment system Artalk. Since Artalk supports multiple sites, it was natural to replace the Legacy comment system Twikoo with Artalk.

Secondary Reasons

Artalk offers features such as login and comment notifications, which the mx-space API does not provide. So, to make things easier, I decided to use Artalk directly.

Memory

First Encounter

Twikoo was what I encountered when I first set up my own Hexo blog. At that time, its features were already quite complete, and it also had the following very valuable characteristics:

• Free (Vercel + MongoDB Cloud)
• Stable (usually works without issues)
• Supports multiple notification methods

Because of these features, it became my top choice for a comment system and accompanied me for four years (2021-2025).

Hesitation

In 2024, I noticed Artalk, which supports multiple sites and many features. I was tempted.

However, it has a strict requirement: you must have a server.

Attempt

Honestly, I wanted to replace Twikoo at that time, but I did not have a server!

My attempted solution was: Deploy Artalk's image using Tencent Cloud SCF functions + Mount Tencent Cloud file system to store Artalk configuration files + Use Cloudflare Worker as a reverse proxy to remove Tencent Cloud's forced download headers.

The whole process was quite arduous, and in the end,

I gave up, yes.

Reunion

Two weeks ago, I was very fortunate to receive a $200 credit for Digital Ocean through the GitHub Student Pack.

This week, I made up my mind to replace Twikoo with Artalk.

And that led to this article.

Say Goodbye

Goodbye, Twikoo!

Hello, Artalk!