The Ongoing Struggle

I've been working on a new way to provision the operating system (Debian) on BitFolk's hypervisor servers.

I have loads of different fail2ban jails.

A couple of days ago something happened that left me absolutely mortified.

Split ticketing?

Recently I watched a Rust video by Andy Balaam covering a test-driven implementation of one brand of the Fizz buzz game.

In the previous article about rethinking my backups I had a TODO item regarding moving away from using intermediary dumps of database content.

Growing difficulties with rsnapshot spurred me in to a long-overdue rethink of how I do my backups.

WARNING This article contains descriptions of medical procedures on the eye.

Backstory The other day I was looking through a log file and saw one of BitFolk's IP addresses doing something.

Recently I found one of my web services under attack from clients using Tor.

Example On the host $ ip address show dev eth0 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether aa:00:00:4b:a0:c1 brd ff:ff:ff:ff:ff:ff […] inet6 fe80::a800:ff:fe4b:a0c1/64 scope link…

Collaborators Last night we went to see Daniel Kitson's "Collaborator" (work in progress).

A few months ago I needed to include some data — that was generated and held remotely — into a MediaWiki article.

This site, being a static one, presents some challenges with regard to accepting comments from its readers.

I've taken the decision to not reuse the same URI structure as my old Wordpress blog, but cool URIs don't change, so I'm going to have to redirect all those old links — or at least the ones I think are marginally "cool".