I've gotten some great feedback by email and bboard on how others
like to write phlogs. Thanks to those who have replied. I've
discovered that the UMN gopher client sometimes truncates text when
displaying a type-1 entry (normally directories but also CGI's),
something I never noticed as I use lynx. As I was writing and
thinking about this, some functional goals for the phlog came to
mind:
* It has to be simple to maintain
* The phlog needs to be readable under various clients
* The phlog entries need to be in reverse chronological order
* Phlog posts should be visible to the veronica-2 indexer
I'm less concerned about feedback by way of comments - few people
used them and email/bboard seems to be working fine.
So here is what I think will work to meet all the goals: A static
phlog based on the myriad of tools available for this at SDF. They
all do essentially the same thing - maintain a gophermap for you so
that posts are in the right order. I used one I wrote previously,
'phlogit', and I may go back to that. Some phloggers update their
gophermap manually each time they post something, this is also an
option. Next is linking to the directory containing the post text
files directly, so that they get indexed by veronica-2. This isn't
really useful for human consumption as far as reading a journal,
since gophernicus lists files in alphabetical order, but with
meaningful filenames it does get you into the search index.
