cxwudi / personal-blog-source

Source files for my Hugo website

Hi there 👋

This is CXwudi. A Mikufan with some serious coding skills.

Projects

I maintained several personal projects:

• VocaDB Video Downloader: A set of CLI apps for archiving Vocaloid PVs from various sources, based on VocaDB API and youtube-dl.
  • Niconico Video Downloader: The predecessor, now archived but kept for historical reference.
• YouCal: A CLI app for exporting YouTrack issues with dates into one iCalendar file, importable by both Gmail and Outlook.
• Song Finder VocaDB: A semi-automated GUI app for batch song searches on VocaDB. It's a toy project for experimenting Compose Multiplatform.
• hoshizora.sql (Originating from VocaDB's archived repo): A dockerized CLI program for loading a VocaDB dump into MariaDB, ideal for frequent and large offline queries, avoiding flooding the official VocaDB API.

I've maintained several libraries, available through JitPack:

• Kotlin/JVM Inline Logging: A custom SLF4J wrapper for Kotlin, optimized at the bytecode using Kotlin's inline class.
  • To use: implementation("com.github.CXwudi:kotlin-jvm-inline-logging:<version>")
• Kotlin/JVM Idiomatic Exec: An idiomatic Kotlin DSL for Java's Process API.
  • To use: implementation("com.github.CXwudi:kotlin-jvm-idiomatic-exec:<version>")
• VocaDB OpenAPI Client Java: A Java Client for the VocaDB API, automatically generated and refined.
  • To use: implementation("com.github.VocaDB:vocadb-openapi-client-java:<version>")

Also some other highlights:

• LibreChat Docker Deployment: A cleaner and better way to deploy LibreChat using Docker, differ from the official deployment guide.
• Conduit (RealWorld) Example App: WIP full-stack Conduit example app for practicing and learning Compose Multiplatform and Http4k. (Project paused, see discussion)

personal-blog-source's Issues

Change waline's emoji link from jsdelivr to other CDN like unpkg

like https://waline.js.org/guide/client/emoji.html#%E9%A2%84%E8%AE%BE

Always need to keep things simply and maintainable

I think the hello world post that DoIt theme's maintainer HEIGE-PCloud written is a great example for hinting us that we need to keep things simple.

Because the simpler we have, the easier to adapt to different situations. For example, what if the DoIt theme is no longer maintaining... (Although I hope HEIGE-PCloud can always maintain this great theme)

Clarify the copyright issue of featured image

As a content producer, We have to be extremely careful about copyright

We maybe can first, ask the famous artist in my QQ list

Create a shall script for Vercel only to run different commands from production and preview build

use https://www.storyblok.com/tp/different-build-commands-branch-name-vercel

Fix TOC wired positioning in more narrow screens

Change my creative licence to Attribution 4.0 International

Which allows commercial action upon my contents, as long as they credit me

Licence link: https://creativecommons.org/licenses/by/4.0/

Security & Privacy concerns

This is very important, we need to take it very seriously

//TODO

Clarify the copyright on the about page to not included other resources like feature images

Currently the about page only states that we are using CC-BY 4.0, but doesn't speficy the range. It should state clear that what is the exception. The exception includes:

• Featured Images
• Links and references to other posts

Add LICENSE

We need to be careful that LICENSE only applies for the repo, but not the content part.

Hence, we need to copy a TXT version of #30 into the content folder

What contents (category & tags) do we have

Category: (Also defined the range of contents that the blog allows having)

• Vocaloid & CFM (V家和C社)
• ACGN (ACGN)
• Technology & Comp Sci (科技与计算机科学)
• Slice of Life (生活片段)
• Gaming (游戏杂谈)

CI/CD for publish

Use https://github.com/cpina/github-action-push-to-another-repository to push the ./public folder to another repo called personal-blog-public

and sync personal-blog-public to coding.net and let both vercel and coding.net hosting the blog from public source.

The reason why we won't want vercel to directly build from source is that

• in case if all website is down, users can still see the personal-blog-public and checkout the generated markdown files

But the downside is increasing GitHub Action usage.

however, for testing propose, we can let vercel dark launch a test blog by directly build from this repo.

Our Waline system seems to not working for Chinese mainland audiences

Because our new post doesn't have the view count incremented, while people are liking my post in QQ

I guess we have to change the serverUrl to a custom domain. Good thing is that this custom domain is only used in this blog, so we don't have to worry about long-term compatibility

How to hide sensitive info in `config.toml`

As #20 shown, we can't make environment variables work for - (e.g. zh-cn would not work)

So we need another way to hide sensitive info in config.toml. But how?

What is this blog for

We even not having time to post on WeChat, will we have time to maintain a blog

• we need to have a place to properly store all my 个人收集的xxxx年V家新曲合集
• we want a WeChat朋友圈 but for friends from everywhere globally (in China, in Canada, everyone can see)
• fulfill the need of writing articles, but don't want them to be controlled by the service provider (Hence self-building a blog is the best idea)

Non-goals:

• we don't want to share close-friend content. The blog is publicly visible, so anyone can see it (including 🍵)
• don't share something too emotional (again this is not WeChat朋友圈)

Refer to #1 about what content does the blog has.

Upgrade waline to v2

HEIGE-PCloud/DoIt@fc1d8c6

Should we open source this repo?

Originally we want to open source because we want Vocaloid fans to be able to find the post in repo if website is down. But with TOML config where we allow output to markdown, we may can just open-source the generated HTML repo, and leave this source code repo as closed-source

Use dev container

Why not

But only problem is how to ssh git push inside

[issue] How to listen old Vocaloid songs

Discussed in #54

^{Originally posted by CXwudi June 12, 2023}

Field	Value
Title	How to listen old Vocaloid songs
Url	https://blog.mikufancx.cyou/posts/202305/listen-old-songs/
File	https://github.com/CXwudi/personal-blog-source/tree/main/content/posts/2023/vocaloid-entry-guide/listen-old-songs/index.en.md

A bilibili users point out two arcade music games with 200+ Vocaloid songs, worth to mention.

They are maimai and CHUNITHM

Here are txt files listing all vocaloid songs, as a reference of :

• maimai list.txt from here
• CHUNITHM list.txt from here

"About" section rewrite

Current "About" section is just a self-intro. That's good, but it should includes:

1. What is this blog used for, what contents does this blog have
2. Self-intro

For 1, we have #15 and #16

Should we open source this repo? 2

in #3, we analyzed the reason for close sourcing:

1. generated site already provided markdown file that can be viewed directly in git hosting site.
2. a repo with HTML sources only has better compatibility (all git site that support website hosting always support just reading index.html)

However, let's re-think the above two reasons:

1. although the markdown file is generated, it almost just a shallow copy of your source markdown file (by just removing the header...)
2. for some git sites that only support reading index.html, we just use two GitHub actions together (Hugo Action + git push Action) to just push the generated HTML sources to the target git site only

So should we open source this repo?

Need a brand new avatar

Such an avatar is like choosing an avatar as a Vocaloid Producer.
So we can't take image from Pixiv or drawer's twitter

Move `content/posts/` into a new private repo to protect the blog post

see https://www.taniarascia.com/git-submodules-private-content/

Customize the footer to include the GitHub and Coding link of the source file

Since the repo is already open-sourced due to #7, why not include the link to this repo

Customization can be done by just copying the current HTML and add our own code. Then put the HTML codes into [params.footer] custom field

Create favicon from Gravatar and use it as avater

using https://hugodoit.pages.dev/theme-documentation-basics/#favicons-browserconfig-manifest

Make use of Envrionment Variables

we should not hardcoded some important URL/config in config.toml, instead, use Configure with Environment Variables

Migrate to CI based deployment

Instead of relying on Vercel to run the build, we should define our own CI to run the build and then deploy to Vercel.

This will also allow platform-independence (in which we are considering moving to CF pages)

some settings should also be shared into a .env file so that dev container can use

POC GitHub Action to generate site and push it to coding.net

can try https://github.com/liziwl/git-push-action
if doesn't work, try https://github.com/seanmiddleditch/gha-publish-to-git next

More setting on Waline

We already have a working Waline instance, but nothing has been fine-tuned, such as GitHub login, force login, notification (just use email one), more useful and secure environment variables and etc.

We already added custom emojis from Waline doc

Btw, waline already embedded Akismet for anti-spam, base on doc. But we added our own AKISMET_KEY

Add and setup sponser

why not

China block gravater, causing the avater not shown from China

This is what it looks like...

Solutions:

1. upload to sm.ms
2. write a script to fetch gravatar into a local file. run it whenever we want to update
3. use 3rd party gravatar CDN accelerator

The issue page is not for readers, but for blog maintenance

Please use Discussion to ask/report questions: https://github.com/CXwudi/personal-blog-source/discussions/categories/content-issue-report