EuDs

EuDs

EuDs's Blog
twitter
github
HomeArchivesAbout

xLog User Experience

#记录#折腾#博客405
AI Translation
This post is translated from Chinese into English through AI.View Original
AI-generated summary
The author shares their experience using xLog, an open-source blogging community. They initially hesitated to use it due to concerns about its sustainability. However, after listening to a podcast and seeing xLog mentioned, they decided to give it a try. They found it easy to use, especially with the provided editor. They also appreciated the concept of web3 integration and the potential for a larger audience. However, they still prefer manually writing summaries and found that xLog did not recognize their existing excerpt. They mention the inconvenience of manually importing their posts from xLog to their main blog. They express interest in merging the importing process with their regular blogging workflow.

I heard about xLog this open-source blog community a while ago due to the promotion by the author of RSSHub. But I have always agreed with the idea that "the death of a blog is not the lack of updates, but the inability to access it." And xLog is still a relatively new thing, so I haven't had the intention to use it.

Origin#

But today I listened to No.27 and Qwerty Learner's Open Wing Chat on Technical Optimization, Product Operation, and Front-end Insights, and I thought it was very well done. I saw that they published it on the xLog platform. So I had a change of heart and decided to give it a try, considering it as a backup. Here are a few points worth mentioning about the user experience:

Actual Experience#

  • As advertised, it's easy to get started. After connecting my web3 wallet and email, I can import my existing markdown files and set up a blog. I think it's great.
  • The provided editor is a nice addition for me because I'm used to editing in vscode.
  • AI-powered summaries. I still prefer to write summaries manually. But it seems that xLog can't recognize my existing excerpt:. However, it does support other attributes like date:, tags:, and title:.
  • Web3. Compared to other blog communities, web3 is a major feature of xLog. This concept has been around for a while, but it's still relatively new to me. This is the first time I've encountered this aspect while using xLog. I find many of the concepts quite interesting, and I think I should take some time to understand how it's implemented.
  • Community. Being a community means that more people may see it. They say that writing a blog is for oneself, but it's also nice if more people can see some of my thoughts. However, I don't want to fall into a situation where I become too focused on metrics like page views and likes, and lose sight of the original intention of writing a blog (I think I will write a post to reflect on what the original intention is). That would be a loss.

Conclusion#

My previous process for writing a blog was usually like this:

  1. Have thoughts and record them locally.
  2. When I have time, I select some thoughts from the local ones that can be used as blog posts. I make some modifications (polishing, anonymizing) and publish them on euds63.github.io.

But now, if I want to update on EuDs, I need an additional step.
3. Manually import it to xLog.

The first two steps cannot be eliminated. And I still consider euds63.github.io as the main hosting platform for my blog. As for the third step, although the workload is not too large, it is still a bit troublesome. So my current idea is to merge the third step with the second step. I wonder if there are any related APIs available.

Loading...
Ownership of this post data is guaranteed by blockchain and smart contracts to the creator alone.