Background (TL;DR)

While setting up the new version of Staticman for my demo GitLab pages, I’ve read developers’ documentations, setup guide and some community blog posts so as to come up with my own guide. It’s originated and inspired from a variety of sources, and refined according to hours of testing. Consequently, despite the original intention to keep things simple, I’ve finally come up with a post with over a thousand words.

To pass my ideas in this post to visitors, it’s better that they have an overview of the contents before actually looking into the details. Therefore, a table of contents is nice-to-have feature for this blog.

Update: I suggest reading a newer tutorial.

To keep focused on the technical setup, please refer to the introduction of this series for the reasons of choosing Staticman and GitLab.

Goal

To set up unauthenticated commenting system on GitLab pages.

This post aims at providing a walkthrough to the GitLab repo setup. If you want to host your own Staticman API instance, you may refer to the next post in this series.

I put some “why” questions here so as to keep focus on the technical setup of the GitLab repo and the optional Staticman API server.

Why static blogs instead of dynamic ones?

• quicker loading time
• better reliability (can handle more request)
• no database needed
• greater control on content, styles and layout

Why static comments?

• allow feedback from visitors
• site owner owns the comment locally (unlike WordPress, Facebook, Disqus, etc)
  • no remote database needed, so no need to worry server errors from third-party commenting services.
  • greater control over the rendering of the comments (allow additional features such as Markdown syntax, and $\KaTeX$ support)
  • more accessible since static comments are incorporated as HTML elements into the post. No JavaScript is required to retrieve the comments, contrary to most third-party commenting services.

Before Staticman’s deployment, another commenting system called Pecosys was already available. However, it’s less convenient to handle visitor’s requests as emails.

Background

My churches are going green.

Problem

→ I downloaded a PDF from Haute-Garonne’s government site, filled in the form and saved it on a USB key. Then I printed it at a Konica Minolta bizhub photocopier yesterday.

Problem

I would like to submit Flying Grizzly’s form. I filled in every blanks and then I clicked the “submit” button below. I was greeted with a MISSING_REQUIRED_FIELDS error within a second.

{
    "success":false,
    "data":["replying_to"],
    "rawError":{
        "_smErrorCode":"MISSING_REQUIRED_FIELDS",
        "data":["replying_to"]
    },
    "errorCode":"MISSING_REQUIRED_FIELDS"
}

Discussion

The error code suggested that the form fields sent should be inspected.

Fixed issue #142

Two weeks ago, Google Webmasters complained about the broken urls in this blog’s Tags page. This was reported by Joakim Vivas as issue #142 half a year ago. Pascal had submitted pull request #165 to fix this. However, he self-closed his PR.

Since the last commit by Michael Romero, Beautiful Hugo’s owner, was five months ago, it seems that he has abandonned his project. Therefore, I used Kaushal Modi’s solution to fix this at commit ff536782.

Goal

To enable Chinese and Japanese input on (X)ubuntu 18.04 laptops .

My choices of input method

On my old Fujitsu laptop running Xubuntu, I’ve chosen Fcitx. This turns out to be a difficult choice when I install Rime.

Japanese input

Thanks to ひゃまだ, I’ve managed to switch between difference modes in Mozc.

Problem

After installing NPM throught Ubuntu’s default apt-get manager, I got permission errors. Though sudo can solve the problem, that’s not the right way in principle because NPM is supposed to hold different versions of Node.js packages for testing. It’s insecure to execute npm with sudo priviledges.

Solutions

1. Install Zsh to improve efficiency

2. Grab Oh My Zsh to instal NVM as its plugin.

    sh -c "$(curl -fsSL https://raw.githubusercontent.com/robbyrussell/oh-my-zsh/master/tools/install.sh)"
   

3. Use NVM (NPM Version Manager) to manage NPM.

   [Read More]

Background: 🈶 ⛪ → 🌿

→ 📧 In the recent decade, organizations are replacing courrier with email. The reason is two-folded. 🌿 First, the later is more environmentally-friendly. 📨 Second, the later delivers the content to the recipient quick as a flash.

📧 📎 When one sends an email, one sometimes wants to attach a file to an email. If one has to sign a paper document and send it by email, then one will probably need a scanner. (Despite the emergence of scanning apps on mobile devices, the quality of a scanner is normally better since the page is flattened during the scan.)

Main ideas

• – Ideal energy range for storage: 40%–80%
• The biggest enemy of electronic parts is heat .
• Avoid overchanging and unplug AC adapter when charging is complete. In particular, don’t leave a fully charged laptop connected to power supply. This can reduce the lifespan of the battery.
• Avoid deep discharges: recharge the laptop battery when its enery level drops to 40%.
• Reduce unnecessary programs running in background.
• If your hardware vendor supports Linux drivers for batteries, set the charging thershold to 80%.
  • Some Lenovo Thinkpads can benefit from those drivers.
  • Other vendors like Fujitsu offers such drives for M$ Windows only.

External URLs

1. Life Hacker
2. Omg! Ubuntu!