chief.sc is both in Ghost and Suffix

For almost a decade, I've used the chief.sc domain in bit,ly, as a custom domain for my short URLs, typically Medium posts on my own publication chiefscientist.org.

At some point bit.ly caught up to my free account with a custom domain, and I could no longer use it to create new shortcuts. The old ones worked, so I let it be. Then this year I vibecoded omnighost, an Obsidian plugin for bidirectional publishing to Ghost blogs, and decided to create a Ghost blog at chief.sc to post there instead of the chief scientist.org Medium, which lacks a proper API and only allows a one-shot draft shipment.

That left all the old chief.sc shortcuts dangling, as I pointed chief.sc to an external Ghost hosting service.

Then I built my own next-gen URL shortener, suffix.org, with such innivations as a CLI, stored photos and files, teams, etc. I added several cool domains to it.

But then I build my own DNS tools, rgbdns, and returned to my own hosting at cron.sh. The host a.ns.cron.sh, besides being a nameserver, was also a Ghost host. I used to run djbdns in EC2, it went to bitrot, and I brought up a Bitnami AMI with a Ghost a couple years ago when it seemed the easiest way to get a self-hosted, configured Ghost. However bitnami is clunky, editing configs is bespoke, and generally it falls apart. So I reused that as a nameserver. But then it occurred to me that I can actually self-host chief.sc as a Ghost blog and build features both in suffix.org and Ghost to ensure URL reservations in each are respected, so they can coexist on the same domain.

So I built it into suffix, as an URL reservation system available to authorized integrated clients. The Ghost integration is a patch.