.___..        .__ .  .              .__.    ,                       ,      .
  |  |_ * __  [__)|_ | _  _   * __  [__]. .-+- _  _  _ ._  _ ._. _.-+- _  _|
  |  [ )|_)   |   [ )|(_)(_]  |_)   |  |(_| | (_)(_](/,[ )(/,[  (_] | (/,(_]
                         ._|                     ._|                       
(This Phlog is Autogenerated)
May 25, 2020

I haven't written for a while, although I've wanted to. I got a little
blocked up by this little project I started in on and actually managed to
finish. It started with useful intentions, then almost went off the rails,
and then got back on the rails, I believe. This is the trajectory of
pretty much all my projects.

The project is this phlog. I found all the cut and paste linking of new
entries pretty annoying, so like a good little programmer I set out to
automate it. My first stab at it was a bit too much, and it all had to do
with my day job as a web programmer. I decided to make my gopher hole a
dynamically generated page from data in a flat file database, all through
a cgi python script on request.

It turns out python is too slow, and my enjoyment of the perversity of
making a fully db driven gopherhole quickly turned into embarrassment in
unnecessarily replicating the complexities and drawbacks of the web here
in the sacred gopher space.

So instead, I wrote a script to take a directory of text phlog entries,
marked-up in a really simple format and create gophermaps from them and
auto index the entries in the main phlog gophermap. So now all I have to
do is write a txt file, and run the script, and then you can read. Whoever
you are.

At the moment it save me some time linking and formatting. Maybe I'll do
something fun and add colors or update my root gopherhole with the latest
entry.