Next Step for Phlogging                                   -*-Org-*-

* Comments

Use index queries, moles, maintain Gopher-style interface
(menus-and-files).

Dynamic article-with-comments-and-add-comment-query menu pages is
what I have in mind, ...

... but how much effort do I want to invest in Gopher? Isn't it
enough to have a variety of updated material in the gopherhole, with
attractive menus that highlight new material and enhance usability,
available for refeerence by myself and other Gopher fans? Although
moles have a lot of potential, the fact is that interaction beyond
index queries has never been a part of Gopher culture, and isn't
likely to become a part of it even if I come up with some great
programs.

Is there any point in pushing Gopher beyond its current envelope when
there is more flexibility, tools, and potential audience in HTTP?
  

* Selection Criteria Efficiency

Select files added/changed in last d days instead of n most
recently added/changed (used find -mtime instead of head).

* Entry Format

For text, HTML, and similar:

  Title as link to main file
  Lead paragraph (or line?)
  Timestamp & comment count as link to comments page (dynamic)

Put phlog entries on top page instead of just link to phlog
directory?

* File Variables

Ignore Emacs file variables "-*-...-*-" when parsing text file,
etc. title. 

* Planet Phlogosphere

A phlog aggregator: An index of recent additions and updates on SDF
phlogosphere sites.

* Phlog RSS

RSS image of phlog entries.

* Phlog Partitions

Instead of having all content pass through the phlog, develop a way
to supress some files from listing in phlog, or divide content into
topically-focussed subsites with separate phlogs. Or separate
materials of personal interest. There are some files that, while I
don't mind them being publicly accessible, are of little interest to
others (e.g. incomplete Otomarii-kai program). Having too many of
these clogging the phlog may discourage regular readers.

This problem is due in (large?) part to Blosxom which includes entire
file contents in its blog list and RSS feed (i.e. it might not be a
problem if viewing were limited to the gopherhole with tirph menus).
What about Blosxom plugins for article "jump"?

* Delete Coordination

Way to delete files without having to manually delete on all mirrors.

Use a revision control system? Consider Ikiwiki?

* cron Jobs

... for tirph, rawdog.

* Gopher MUD

* fortune printing problem

* Language challenge

Rewrite tirph in C or Common Lisp.