UPDATE [Mar 26, 2023]: I wasn’t using the microblog at all, so I went ahead and deleted the VM being used to host it.
I recently read a blog post titled What to Blog About by Simon Willison. It suggested the idea of posting TILs which stands for “Today I Learned”.
Did you just learn how to do something? Write about that.
I love blogging, but I don’t like writing about things that one can easily find in other places online (e.g. documentation) or that other people have already written about. For example, I once wrote about Managing Services on Google Cloud Run with its Admin API Client in Java but removed it later because I felt that the actual docs on the topic were sufficient.
However, I still want to share small hacks or stuff that I find interesting more often. Besides, I thought that hosting my own microblog would be a fun project and hosting it myself means that my content truly belongs to me.
A lot of folks I know have been creating accounts on various Mastodon instances. Initially, I was planning to host my own Mastodon instance on my old laptop server using Tailscale Funnel. However, Tailscale Funnel doesn’t support custom domains at the moment so that was out of the question.
I started reading about the minimum system requirements for hosting Mastodon in the cloud. From there, I stumbled upon ActivityPub, which is a W3C protocol that Mastodon implements. I also realised that Mastodon may be too heavy for my needs, since I was going to be the only user on my server, and started to look for lighter alternatives. That is when I discovered microblog.pub.
I decided to get started with a regular $6/month Debian 11 droplet on DigitalOcean with some credits I had in my account (thanks to the GitHub Student Developer Pack). I SSH’d into the droplet, created a new user, added the server as a node on my tailnet, and set up relevant firewall rules using UFW.
$ sudo ufw status verbose Status: active Logging: on (low) Default: deny (incoming), allow (outgoing), deny (routed) New profiles: skip To Action From -- ------ ---- Anywhere on tailscale0 ALLOW IN Anywhere 80/tcp ALLOW IN Anywhere 443 ALLOW IN Anywhere Anywhere (v6) on tailscale0 ALLOW IN Anywhere (v6) 80/tcp (v6) ALLOW IN Anywhere (v6) 443 (v6) ALLOW IN Anywhere (v6)
Next, I set up NGINX with certbot and updated my domain’s DNS settings to point the
til subdomain to the IP address of the droplet.
I cloned the
microblog.pub repository on the droplet and built a docker image for the service.
After updating the default profile values for the service, I started a container with docker compose.
Finally, I configured NGINX to route traffic to the docker container.
The docs recommend creating a 301 redirect from
The problem is,
ricekot.com is a static site hosted on GitHub pages, which means that redirecting with a 301 HTTP response status code is not possible.
Since I’m using Cloudflare DNS for my domain, I thought of creating a redirect rule for this situation. Cloudflare DNS supports proxying incoming traffic and transforming it with custom rules before it reaches a domain.
|Cloudflare redirect rule|
All I had to do next was, add
webfinger_domain = "ricekot.com" to
data/profile.toml, and restart the container.
My microblog instance was now ready to be connected to the wider Fediverse.
I confirmed that my account was accessible via other Mastodon services by searching for
@[email protected] on infosec.exchange.
Just in case, I also decided to backup the
data folder within the cloned
This folder is mounted inside the container and contains all the data specific to my microblog instance.
I set up Syncthing over Tailscale (which was required because of the UFW rules) and shared the folder with the other nodes on the tailnet.
|Syncthing folder metadata|
While setting up my microblog was a lot of fun, I’m not fully convinced if this is any better than a regular static site for my purposes. I’m not a huge fan of social media, and I’m not sure if I want to pay $6/month for sustaining this when my credits run out. For now, however, I think I’m going to start posting stuff I find interesting to my microblog, and we’ll see how it goes from there.