4 October 2026

So much news to cover!

The biggest change is that I’ve moved to Melbourne. I’ve been here for two months now, and living in vibrant Fitzroy. The other big change is that Bliptown has migrated to NetBSD. But more on the in a minute.

Not long after I arrived here I learnt that one of my favourite pieces of music, The Disintegration Loops, was to be staged in its entirety overnight at the beautiful Melbourne Museum. The show was sold out, which broke my heart a little because seeing this had been on my bucket list for years. But then a few days before the event I opened my email on a tram ride and saw a message offering a second round ticket, but I had to act now or the ticket would be offered to someone else. I did act, and shakily entered my bank card details to secure a ticket. The show was of course awe-inspiring, and I am now one checked bucket list item closer to death.

I was lucky enough to get a house sharing with only one other person, mere steps from the Fitzroy high street, and with enough room for a desk. I should be making better use of this, but I have spent most of my time at this desk working on Bliptown.

There is a theory called the Lindy Effect that posits the longer something has been around, the more likely it will stick around. The name comes from Lindy’s delicatessen in New York, which is ironically now closed. This effect surely applies to software. Until just recently Bliptown was running on OpenBSD, an operating system first released in 1996. This week I migrated servers, to an OS and infrastructure that has been around even longer; Bliptown is now running on NetBSD, which was first released in 1993, the same year as Jurassic Park. (OpenBSD is a descendent of NetBSD, and both are Unix systems.) Bliptown is written in Perl (est. 1987), and now the back-end file operations are handled by the “internet super server” inetd (first released in BSD 4.3 in 1986).

Migrating Bliptown from OpenBSD to NetBSD

During its first year, Bliptown has only suffered three instances of prolonged downtime (i.e. over a few mins), the most recent on Friday last week. All three times were due to the same piece of OpenBSD software — the reverse proxy relayd. OpenBSD has a reputation for unmatched code quality, so having the same part of the OS fail three times is concerning. I had also seen someone say that the code for relayd and httpd was languishing due to developer disinterest. I won’t go into furrther detail but it was enough to make me question OpenBSD’s reliability as a web server.

Something I liked about OpenBSD is its high level of integration — Perl, httpd, relayd, the pf firewall, acme-client and more are all part of the base system. This level of integration really makes system more than the sum of its parts. It’s reassuring to know that the same level of care and attention, by the same people, that went into making the OS a battle-ready tank, also went into say the reverse proxy. It makes it an easy decision to build your stack on components “in base.”

The problem for me was that when something in that base system failed, I had to understand that the system is really a combination of different sub-projects, each with their own level of care and attention, and some lagging. I guess what I lost was the idea of OpenBSD.

I’ve always liked NetBSD. It’s officially called “The NetBSD Project” as it operates primarily as a research project. The community are very nice and friendly, and as for longevity, SDF.org (est. 1987) have been running NetBSD since the turn of the century, and serves as a test bed for the project.

NetBSD doesn’t try to include everything in the base system. Sure it has Lua and Fortran, and NPF in the kernel, and a bare-bones HTTP server, but if you want a reverse proxy you install nginx, if you want an ACME client you install uacme. Same with your preferred sudo replacement (I’m using priv, est. 1997).

So by Friday night I had created a NetBSD server and had it running the Bliptown staging site. The Bliptown production site had migrated completely by Monday.

inetd + bliptown_helper

An important note about Bliptown is that it is a flat-file CMS, all web pages are files underneath, all users are regular system users, which means that all files are owned by different users. This is very different to how most CMS’s work. What this means is that in order for Bliptown to do file operations there are two options: operate on the files as root and then change ownership to the user, or (the safer option) forks a process that drops privileges to the user and then performs the file operations. This is the way Bliptown works.

Previously I had done this by running bliptown_helper daemon as root, then forking and dropping privileges for every file operation. With the server migration I thought it might be time to reasses my hand-rolled pre-forking daemon code and maybe hand the responsibility instead on software that has been battle tested for the last 40 years.

The idea to use inetd actually arose from my efforts to block malicious requests — commonly called “script kiddies.” The logs of any server connected to the internet are going to be flooded with requests to known vulnerable endpoints (usually of misconfigured WordPress sites). I wanted to immediately block any IP requesting one of these known endpoints.

I set an nginx location match to forward the IP of any such request to port 9666, where inetd would spawn a quick Perl script to add the IP to NPF’s block table.

The idea of running an “internet super-server” just to block script kiddies seemed like overkill, so I got the idea that maybe I could use it to also run bliptown_helper...

It turned out this was not only possible, but would mean I could jettison much of my code (goodbye maintenance burden) and no longer need to run a daemon as root.

Now I have inetd listening on port 9000 for a request from the Bliptown server, which then spawns bliptown_helper (now a simple script) and hands the connection over to it. It takes input from STDIN, drops privileges, performs the file operations, sends its output back to STDOUT, then dies.

If you’re thinking this sounds a little like CGI then you’d be right! It’s pretty close. However, the pitfall of CGI was that is required a single process per request, whereas Bliptown only needs a single process per user file operation.

That didn’t mean I wasn’t concerned about implementing a CGI-adjacent process model. It just meant a good time to improve the file operation code. Previously the helper would fork one process for one file operation. 99 filename changes? 99 processes. The pre-forking worker pool of 4 was pointless for such a (not uncommon) scenario. Now operations on multiple files are handled by one process.

Other News

Sick of GPG I wrote my own POSIX shell wrappers for OpenSSL public/private key encryption/decryption (and an associated Emacs mode for transparent file operation) called enc.

I’ve also revived my POSIX shell todo list manger from ten years ago, t_done. It now have an Emacs mode too.

Now I begin my mornings with a cup of coffee, my journal.md.enc in one Emacs window, and my t-done-mode todo.md in the other. It’s a good way to start the day.

16 June 2026

Last week I visited a friend up north in the countryside. We had dinner, drank wine, and listened to Sonny Rollins while we chatted about art, culture and politics. There are beautiful views from there. It made me think about how when I’m old I would like to live in the mountains, in a small house with a small yard backing onto some undergrowth. I would drive down to the village and get a coffee and a croissant at a charming little café where they know my name.

My friend returned my SP-404 mkII after having it for a few years. I am still trying out the features from the new firmware, but I have already run into a lot of bugs. However, the sound generator is a welcome addition; it creates a basic sine, sawtooth, triangle, etc. tone, then filters and envelope are applied to this via resampling. It’s an interesting workflow, and I’m enjoying the challenge of creating new sounds.

I spent a few days at my parents’ house. It was peaceful comforting, and part of me is sad to come back.

Currently listening: loscil – Adrift

9 June 2026

Although Bliptown proudly states it has no AI, I still employ AI to help me write it. I always keep it at a distance, letting it show me how something should work and then I will rewrite it in my own style. I never let agents run on my local machine (and never on the production server).

This poses a problem, because for AI to be helpful it needs to read the existing code. One way this works is for the AI to operate on the same platform as the code is hosted, like GitHub. I had got a free GitHub Copilot student subscription that initially gave me access to the latest ChatGPT and Claude, but then Claude was taken away, and then all but the free versions of ChatGPT were gone too. Also I felt uncomfortable about using GitHub.

I wanted some way for AI to read my code, but I didn’t want to use GitHub any more, and I didn’t want to allow it to operate on my computer.

Most AI CLI tools work on a permission system, but the permissions are built into the tools, so it seems trivial for the agent to just change or ignore them. I looked at various options to sandbox the agent, like the (deprecated) macOS sandbox-exec CLI, but it was too complicated and wouldn’t help on my Alpine Linux machine.

Then I found llm, a Python tool that takes the prompt from STDIN and, sends it to a model, then prints the response to STDOUT. Beautifully minimal. No AI runs locally. No complicated sandboxing system needed.

I wrote a PROMPT.sh that would print high-level model instructions about Bliptown, then the name and content of each file. I can pipe this into llm then provide an additional prompt on the command line and voila — the model has full knowledge of the entire project.

Currently listening: Grouper – Ruins

8 June 2026

Finished my final assessment for university. I presented Ascent, my final semester’s work. I can now focus on Bliptown. I haven’t done any coding for months and I am rusty. The terrain of the code seems less familiar and I need to feel my way around.

I’ve been thinking a lot about a video game I want to make. It’s 2D top-down game where you pilot a little ship, similar to a submarine, around a black and white landscape. You shoot enemies with lasers and torpedoes, but the core of the idea is that you construct spatial musical creations by placing various kinds of nodes (bangs, synths, filters) and telling them to move in interesting ways to interact with each other. There is a void that is continuously encroaching on the play area and by creating music you can hold it back. I want to learn Lua and write it in LÖVE2D.

Started implementing test coverage for Bliptown. It’s quite rewarding to run prove and see each test report it’s okay then “All tests successful.” Eventually I will run these tests before every change to the code to guard against regressions.

Currently listening: Ryoji Ikeda – op.

30 May 2026

This morning I went out for coffee at the nice restaurant around the corner. I wrote my morning pages there. It put me in a good mood so I’m glad I did.

I’ve disabled WAL on the site database, which reduces the amount of moving pieces and risk of file corruption.

I am overwhelmed with the amount of media (films, music, books, articles) I want to consume. I fear that I won’t have enough time.

Currently listening: Wish – The Kite

27 May 2026

Went through the nail-biting process of upgrading Bliptown dependencies today. Major versions of Net::SSLeay and Mojo::SQLite. Added a busy_timeout to the database in preparation for disabling WAL, which apparently has file corruption issues. I’d rather Bliptown be a tiny bit slower sometimes than have a corrupted database.

I still need to prepare for upgrading to OpenBSD 7.9, which will require taking a snapshot and building another VM, performing the upgrade and seeing if all goes well, before upgrading the production server.

I have been looking into doing a Master of Fine Art research degree at VCA (University of Melbourne), instead of a Master of Contemporary Art coursework degree. The MFA can be completed part-time over four years, whereas the MCA is full-time only, and with RTP I think I will be exempted of fees (no HECS). This would mean making a single body of creative work equivalent to a 40,000 word written submission. Am I ready to do that? It’s silly but I’ve always wanted an “MFA” instead of an “MCA” or “MVA” (what I’m studying at QCAD).

It has been raining all day. I have my week’s washing on the line.

Currently listening: James Blake – Playing Robots Into Heaven

23 May 2026

Today is my mother’s birthday. We had a nice long phone call. I implemented the dump(8) backup schedule on Bliptown. I watched Roland’s videos on the firmware updates for the SP-404 mkII versions 3.0, 4.04 and 5.50. (Version 5.0 is only about integration with Serato and not of interest to me.) The sound generator (a poor-man’s synth), live looper, and side chain compression are game changers. Although the sound generator is limited, resampling with onboard effects makes it quite capable.

Currently listening: Burial – Antidawn.

22 May 2026

Visited three galleries today with my postgraduate class: ProppaNOW, Milani Gallery, and Vacant Assembly. Something about these made me sad and I left needing a coffee. The coffee place only did takeaway coffee but I found out after I had already paid.

Since I found that Bliptown’s host’s VM snapshot backup wasn’t reliable I’ve been researching dump(8) as a file-level backup solution. It’s a very old program and the manpage even talking about managing separate tapes.

I registered the “Bliptown” business name.

18 May 2026

Rained all day. I like the rain. Accomplished very little.

Currently listening: Robert Haigh – Human Remains.

17 May 2026

Had a coffee with a friend first thing at a nice restaurant around the corner. I need to visit that restaurant more often. There’s a beautiful view out over the suburbs and to the distant mountains. We talked about his plan for an artist/psychologist/pilates venue and about Bliptown. He gave me some more music recommendations:

Set up the Bliptown Roadmap.

Currently listening: Moby – Ambient 23.

16 May 2026

Asked a friend for music recommendations and received the following:

I was listening to these this evening. I quite liked Now You Exist, although I’m trying to spend more time listening to music with lyrics. Now I’m listening to my 2023 best-of playlist. It was the last year I made a year’s best-of playlist.

7 February 2026

Verify A/AAAA records before attempting to renew a domain with acme-client. Added Cache-Control headers to cdn-origin.blip.town requests. (This compliments the previously added ETag headers.)

6 February 2026

Split update_domain_list for acme-client and relayd because the order of adding a custom domain needs to be:

  1. Update domain list for acme-client
  2. Provision new certificate
  3. Update domain list for relayd

5 February 2026

Implemented CDN purge upon uploading files. This will purge files uploaded with the same name as previously cached files, and for new files will do nothing. We couldn’t just check if a file already exists or not because a file could have been deleted while still cached.

4 February 2026

Fixed edit page to link to files with absolute and relative filenames (previously this didn’t work for included files with absolute filenames). Fixed an issue where Bliptown was only creating new file handles for logs when I restarted it, as it wasn’t receiving USRSIG1. Added two-columns layout.

Added daily generating of /software.txt.

31 January 2026

Added a favicon.ico instead of just favicon.png since browsers seem to ignore the latter. Added Host header logging to the analytics and skipped rendering any referrer URLs that match this (i.e. ignore internal referrers).

30 January 2026

Implemented a new file manager that traverses directories instead of listing files recursively, and provides breadcrumbs navigation. This was a big undertaking that spanned several days. It required list_files take a catchall parameter so you can have paths like /files/foo/bar. Preventing directories being renamed inside themselves was tricky. Only empty directories can be deleted, although any hidden files will automatically be deleted too. Helper responses will now be logged unless in production.

25 January 2026

Implemented OpenBSD::Unveil in bliptown_helper. Implemented viewing snapshots changes (a simple call to git show). Check for valid hashes before running git commands. Fixed repositories initialising without user.name or user.email.

Used system calls instead of invoking a shell for bliptown_helper commands.

Fixed CSS for inputs in Safari.

23 January 2026

Fixed stats to show seven weekdays instead of showing seven 24-hour periods. Removed global logging in favour of logging via relayd. Tried to create a log format for GoAccess to read relayd logs but instead opted just to abandon GoAccess for logs.

Added a block_php script to run continuously and add any IPs requesting .php URL paths to rate_limit block table.

21 January 2026

Implemented Mustache placeholder {{ variables }}. Made child pages inherit parent page metadata (except for layout). Added {{ prettydate }} special placeholder and formatted date user option. Incremented database schema to 6.

Added ration-cinema image layout.

20 January 2026

Fixed positioning of header on mobile. Rewrote Bliptown::Model::Page as object orientated. Added gallery-N-columns layouts. Various fixes.

19 January 2026

Bliptown is now licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International licence. Previously the source was licensed under the Apache 2.0 license, and although Creative Commons is uncommon (and even discouraged) in the software world, it is common in the art world. While I’m not interested in supporting strangers running my code, I am derriving a huge benefit from Mojolicious and the OpenBSD ecosystem, all of which are open source.

Improved stats to list each of the past 7 days, even those without hits.

18 January 2026

Implemented analytics. I took the design from Herman at Bear Blog to log the requesting using a CSS background-image URL on a body:hover #analytics where #analytics is an empty div. The referrer is passed as a parameter. Each request URL path has a random string so that multiple requests are not cached. The request’s referrer itself is the visited page. The IP is hashed and logs are deleted after 8 days; the hashing algorithm was initially md5 but I changed it to HMAC SHA1 with an app secret to better comply with the GDPR. Finally, logged in users are discounted for their own site.

I had to rewrite my log rotation code in hourly.local because newsyslog sleeps for 5 seconds upon every run, and I was running it once per user. Instead it now builds a single rotate.conf and runs once for all users.

I also fixed a mistake where I was using the same salt for every password. This was due to a misunderstanding of how hashing salts work. It worth using Mojo::Util generate_secret instead of rolling my own random secret generator for 2FA secrets.

Heinz managed to rate limit himself via relayd so I reconfigured for more generous per-second requests.

14 January 2026

Implemented very basic sorting on the Files page by name/size/date, which allowed removal of the user setting in the database. Replaced the use of regular expressions in the file filtering (which was a security issue) with glob pattern matching from Text::Glob.

13 January 2026

Finally fixed logfile rotating. The HUP signal was only being sent to the parent process when it needed to be sent to the parent and workers. I also changed to a USR1. In /etc/newsyslog.conf:

"pkill -USR1 -u bliptown -U bliptown -f script/bliptown prefork"

I removed Bliptown::Model::DomainList and folded its code into Bliptown::Controller::Settings. bliptown_helper now validates domain names before performing domain actions. Refactored the use of parentheses in bliptown_helper for clarity.

12 January 2026

Added the ACME challenge route, which I thought was only HTTP. Added consistent IPC exception handling of error messages back from bliptown_helper.

9 January 2026

User can now include JavaScript at the end of <body> by adding it to a _scripts.js file. Added the user skeleton files to the repo.

I’m pleased that my pf rate limiting from yesterday has already caught some bad guys.

2026-01-08 Thu

Implemented [[wikilinks]]. This is something I’ve wanted to do since the beginning. Editing Bliptown pages was always supposed to work like editing a wiki, where creating a new page was as simple as linking the word to it and clicking the link, which would land you on editing the new page. Now text surrounded by [[double square brackets]] will be converted into a link to that relative URL. But [[/absolute links]] work also.

Try it with the heading of this post!

Also implemented graceful shutdowns for bliptown_helper. Something else I’ve wanted to do for a while, as restarting the daemons is always mildly terrifying. This way the master daemon receives a TERM signal, then signals the workers, which will finish what they’re doing before shutting down, and once they’re all shutdown then the master daemon exits cleanly.

Finally, implemented rate limiting with pf. If an IP makes 99 simultaneous connections or 10 connections within one second it will be blocked for 24 hours after its last attempted connection.

6 January 2026

Implemented logging, both at global and user levels. I thought I would need to use Mojolicious::Plugin::AccessLog but I was able to implement it with just the Mojo::Log object.

5 January 2026

Attempting to separate blip.town from staging.blip.town was too tricky so I bought the domain bliptown-staging.com and set that up to mirror the production site as closely as possible. It uses the same source files and its database is taken from a daily backup of the main database. Technically users can login via the staging site and make changes, but I don’t see this as a problem.

Added a backup button in the Files page, so users can manually create a page backup even if they don’t have automatic backups turned on.

Fixed a bug where /new/foo would not redirect to /edit/foo when foo exists.

1 January 2026

Fixed a regression where user login would hang because the URL object did not call to_abs. Also fixed an error where login on any subdomain would redirect back to blip.town to set the cookie.

Split user_login into smaller subroutines. Added some more uses of $c->config. Added link to home on error pages.

30 December 2025

Merged in the prefork branch, which is a rewrite of bliptown_helper to prefork into four workers ready for IPC messages. Each worker performs one operation then dies, and the main loop repawns a worker until there are BLIPTOWN_HELPER_PREFORK number of workers. I’m quite happy with this code.

29 December 2025

Fixed an annoying CSS bug that allowed the nav header to scroll on mobile when the menu was closed. Also changed some CSS to allow the user styling background colours on body rather than nav, header and main.

Welcomed another alpha tester into the fold: Darryn King.

28 December 2025

Implemented CDN for images and removed image caching. The new code is much simpler than the image caching.

Moved a bunch of code into $c->config. Fixed a bug where deleting nonexistent file foo.jpg would delete file foo.md.

24 December 2025

Fixed a bug where logfiles would be turned over and changed to root:wheel. Use grep -v to ignore newsyslog log lines. I’ve tried a few different ways of logging. I feel like I can implement basic logging myself with just a Mojo::Log object but it seems like I may need to use Plugin::AccessLog.

23 December 2025

Made some attempts to set up access logs. Mojolicious has several hooks that offering varying degrees of usefulness for logging. after_dispatch seemed like the obvious choice, but this only logs requests that go to a route. after_render was another option, but this lacks things like return code. Plugin::AccessLog works on after_build_tx but the problem with this is it has no access to the controller, which means I can’t access the stashed value of the logfile.

Stats will only be generated if the user has created /private/stats.html.

22 December 2025

I set up a duplicate instance of Bliptown on beastie, <bliptown_staging> in order to test changes in the actual production environment instead of Alpine Linux/macOS to avoid things like the tar bug. Fixed the bug where saving settings with an empty custom domain would violate the SQLite UNIQUE constraint by insuring a false value is sent as undef.

21 December 2025

In bliptown_helper, moved reading of the Sereal message into the forked process, and increased the very low (5) socket listen limit to kern.somaxconn (128).

Fixed a bug where tar wasn’t extracting git archives which was preventing snapshots being restored. Added checking for existing current cached image before creating new, and added a 5 minute timeout to in case the process gets stuck.

20 December 2025

Implemented a requested feature to keep <details> sidebar menu elements expanded when on that page. Much more difficult than it would seem. The sidebar menu is just Markdown so couldn’t be done with HTML. Not possible with CSS. Want to keep the site free from JavaScript.

The solution was to post-process the sidebar HTML with Mojo::DOM, find any <a[href=$slug]> elements, then iterate up over their ancestors for any <details> elements and add the open tag. Also I put on a selected class to allow styling the actual selected link.

Implemented smart typography. “So now I’m able — to do this!” I love how little code this was. I thought it would be difficult. My main win was using the preexisting recursion counter to only parse the Mojo::DOM at the top-level loop.

19 December 2025

Implemented snapshot downloads. This is just a simple git archive export to a temporary file, then serving the file with Mojo::Asset::File. Fixed a bunch of errors with system() calls.

18 December 2025

A substantial rewrite of the image caching logic to perform intensive tasks in subprocesses, and of bliptown_helper to perform every command in forked subprocesses.

Renamed the controllers from singular to plural, e.g. File to Files. Added the Git clone URL for snapshots with more than 0 commits. Accept JPEG, PNG and TIFF files for caching. Replace Perl’s Encode with Mojo’s encode/decode.

16 December 2025

Solved a 500 server error when generating an image cache with UTF-8 characters in the filename. (Glad I kept UTF-8 in Heinz’s filenames.) Added a new layout gallery-columns. Improved git_init to configure a repository to use core.excludesFile = /etc/gitignore which is much more robust than relying on added a .gitignore file in every repo. Although the HTML body is not intended for user styling, people are gonna do what they do, so I added some CSS overrides for common style changes. Changed the 404 on protected pages to a very polite:

Sorry, this page requires a login.

15 December 2025

Bliptown went down for 25 minutes. Luckily this happened at approximately 10:30am so I was able to deal with it. The immediate cause was found to be an empty SSL certificate chain and key. Any connection to https://blip.town would error. Manually trying to curl the certificate from Porkbun resulted in a timeout, which made me think the problem with their API. I downloaded the certificate directly from their site and installed it on beastie. Bliptown was back online.

There was still a large backlog of outbound mail stuck inflight. After succeeding fetching the certificate locally, I remembered having recently changed the host-level firewall. The firewall, which had previously allowed all outbound traffic, now had a single rule, which only allowed ICMP traffic out, nothing else. As soon as I fixed this the backlog of emails was flushed, and calling the script to fetch the certificate succeeded.

This lead to a concentrated rewrite of daily.local that is now safer and failure tolerant.

Also implemented restoring snapshots, which was quite simple given the amount of scaffolding I’d already done. In the snapshots page, clicking on a snapshot and then “Restore” will restore all files of that commit to /snapshots/<HASH>. This is almost like restoring a version of your site available under the /snapshots path, except that of course absolute links will still take you out.

14 December 2025

Implemented basic snapshot UI. This is basically a wrapper around git log, with the output parsed into an array reference of hash references. It was easy to get bliptown_helper to pass a command to git; the hard part was getting the output returned to the app. It was ultimately not a huge patch but getting my head around requests and responses on sockets took me a while. At least now every bliptown_helper command can return a response and an error back to the app. Much more professional.

12 December 2025

Fixed the persistent issue where leaving whitespace around a file inclusion directive would result in empty <p> tags. Fixed a regression where clicking New would attempt to create the current page. Fixed a CSS issue where expanding content within #viewport would result content scrolling out of the viewport.

11 December 2025

Rewrote bliptown_helper to use Mojo::File instead of Path::Tiny, because it seemed to make sense to only use one API. Also improved the update_domain_list function to only update the relayd/acme-client files if the content has changed. Added a workaround for the longstanding iOS bug where <details> disclosure markers would display as emoji.

10 December 2025

Wrote a bunch of documentation. Made the file inclusion regex match only patterns on their own line. Wrapped <pre> elements in a one-column layout.

9 December 2025

The absense of a _sidebar.md file will now render the site without a sidebar. Implemented private pages. Anything in the path /private will be a return 404 for anyone but the logged-in user. This allows building a whole part of a site while keeping it private, then moving/renaming the files to make it public. Rewrote the Files page forms as separate. The rename and delete forms use the filter as a hidden input, then act of those filtered files. This allows the rename input to action on pressing enter, and is neater.

7 December 2025

Reverted the code for topbar layout. Neglected to test this before I pushed it to production and crashed the website. Lesson learnt. The design is built on the idea that the best artist pages follow certain design priciples. Adding both sidebar and topbar navigation undermines that. Bliptown should be opinionated, and that means sidebar navigation.

6 December 2025

Bliptown was sporadically returning an SSL error on my phone. Frustratingly, this seemed to only happen when I was out. When it happened again today, I realised that it was isolated to my mobile connection, which explained why sites would load again once I got onto home wifi. Some digging suggested certificate pinning, but I wasn’t doing that. It turned out that the server wasn’t listening on IPv6. I had specified listen on egress in relayd.conf but apparently this only binds to one address. The solution was to specify both the actual public IPv4 and IPv6 addresses.

5 December 2025

Limited including user styles to just user pages. This allowed a rewrite of the default CSS to use semantic HTML instead of #blip-* IDs. Added a hack to allow users to hide the drawer toggle plus but reveal it with ?toggle=1 in the URL path (this will please Jackson). Implemented an experimental topbar layout; the user just creates a _topbar.md and it will override the sidebar and use a topbar layout. I even figured out how to have sub-lists automatically display as drop-down sub-menus. I’m very much undecided on this. It’s not as robust as the sidebar layout and may fail on mobile.

4 December 2025

Seems like as good a day as any to start a devlog. I’ll keep these to under 512 characters (an OpenBSD block). Upgraded Alpine to 3.23.0 which included a newer CMake. This broke Data::MessagePack::Stream because it vendors an ancient version of msgpack. Rewrote Bliptown::Model::IPC and bliptown_helper to use Sereal instead of MessagePack. Made Bliptown open source, released under the Apache 2.0 licence.