Newsletter Archive / CDN Images, Smart Typography, Performance Improvements


Date: Tue, 30 Dec 2025 08:25:26 +0100
From: support@blip.town
Subject: CDN Images, Smart Typography, Performance Improvements

Hello again and thanks for testing Bliptown! Apparently none of you received update #1 so it’s available here: https://blip.town/news/2025-12-19

Onto the updates!

Images served by Bunny CDN

The biggest user-facing change is that Bliptown now serves images via a CDN (content delivery network).

Initially my plan was to serve everything including images, from the server, without intervention from a big tech company. This quickly proved too idealistic, because artists want high quality images of their work, and loading every image from a single server in Nuremberg can become tedious.

The solution is to use a CDN so images are cached on servers all around the world and the visitor gets the closest one.

The de facto standard CDN is Cloudflare, which has a free tier and Bliptown’s usage would almost certainly remain free for life. But I don’t like being a non-paying customer, and I don’t think all of the internet’s data should flow through one company.

The alternative I chose is Bunny CDN. Bunny is based in the EU and has a pay-as-you-go model with a minimum monthly payment. Serving images via the CDN required rewriting requests to be served by the CDN:

user.blip.town/doggy.jpg -> cdn.blip.town/user/doggy.jpg

And responses:

cdn-origin.blip.town/user/doggy.jpg -> /home/user/site/doggy.jpg

This was all easier than I had anticipated and the results were immediate, with much faster load times for pages with images!

I plan to add a link in Settings to manually purge the user’s CDN cache.

Smart typography

You can now type in ASCII "straight quotes" and multiple dashes --- which will be dynamically transformed into smart typography.

Single and double quotes are transformed into smart/curly quotes, a double dash -- is transformed into an en-dash, and a triple dash --- is transformed into an em-dash.

This happens on-the-fly and doesn’t touch your original page source.

Preforking bliptown_helper

Bliptown runs on the server as several different processes. There’s the main bliptown app, which runs as an unprivileged user and preforks into four child processes. Then there’s the bliptown_helper process that performs all the file-based operations, and runs as root. Until today, it would fork upon request, drop privleges to the user making the request (you) then perform the file operations. This technically did allow concurrency, as long as requests didn’t come in too fast, but is a very old model of process control, and meant that there wasn’t a process ready when the user made the request.

Now, bliptown_helper has been rewritten to prefork into four child processes, all running as root, but ready to drop privileges when a request comes in. Each process performs the file operations, then dies, and the supervising process spawns a replacement process.

This is a more modern and robust approach to concurrency and should mean the website runs faster when working with files.

Technically this is still one process per file operation, which means 100 processes for 100 file delete operations. It could be rewritten to take a list of operations and have the worker process perform all before dying, and maybe I will, but for now I like the simplicity more than the efficiency.

Notable bugfixes

  • Main page background colour can now be set on the body element and is inherited to nav, main, and #viewport elements.
  • Fixed 500 internal server error when saving settings due to SQLite custom_domain UNIQUE constraint.
  • Fixed page style that allowed header on mobile to scroll.
  • OpenBSD tar requires -f - to read from stdin.

As always, Bliptown is completely free and open source software. The source code can be explored here: https://blip.town/code

Sincerely,

–
Paul W. Rankin
https://blip.town

← back