I'm too slothful to set up a real blogging system yet, so you will see nothing, because this archaic diary requires JavaScript to download individual entries.
If you're interested, I do this for two reasons…
- I can keep entries organized and separate without duplicating content (and do something else with them later, easily).
- I can support arbitrary HTML in my content (which using an off-the-shelf Markdown blog might restrict, and it also has the overhead of integration).
The next step would probably be to create a process that writes to this page the amalgamation of native content—such as this disclaimer—and blog entries, and run that every time I write a new entry. Ideally it runs automatically in a continous integration process.
So, I'm sorry, but in the meantime you'll need JavaScript to look at my diary.
Addendum 2026-07-25: It has been fun doing everything front-end and seeing how negligibly slow network requests are compared to already-included-on-page content. However, the maintenance annoyance is getting to me. I'm seeing how much boilerplate is being copied, multiplied by the expanding number of posts. Any header change, any new navbar button, any slight HTML change shared across all posts means a bit of copy-paste or find-replace. These are all known problems from the outstart, but from its humble beginnings I wasn't sure whether my site would reach this point. I'm considering upping to Hugo, which would turn this page content static. For now, we'll see.