Comments are disabled for now. I've been receiving a massive amount of spam because the captcha plugin doesn't work. I haven't tried the openID plugin; I might have to.

Google started blocking emails from Jamey's server (which sends me notification of comments) when it noticed the massive amount of emails that looked like spam, because, well, they were. We also get voicemail notification from that server, so the backup might explain why our voice over IP setup hasn't been working.

I still have Maria's one valid comment saved, I'll revert it after I get a good spam-blocking system setup. Feel free to email comments sarah at thesharps dot us.

Still trying to get the tagging plugin to work. I'm not sure what I'm doing wrong. The plugin is in my plugin directory (renamed to tags-sorted.py instead of tags-sorted.txt). I've set the tags URL to--oops, there's the problem, I needed a trailing slash at the end of the URL. Let's reload and see if that's really the problem...

Nope. I needed to add $tags to my html flavor's story.flav file. I'm still not seeing any entries in the tags folders that I created; I'm not sure what's up with that. I should probably get a better html flavor before I attempt to add a tag cloud.

Edit: I fixed it! I didn't understand what tag_url was supposed to be. A lot of people have Apache mod_rewrite for their blog urls, and they assume that everyone else does too. For a beginning install, tag_url should be the URL for the pyblosxom cgi script, followed by /tags/. E.g. http://minilop.net/cgi-bin/pyblosxom.cgi/tags/

Oh, and you need to add two variables to your config.py or sometimes looking up a tag will fail:

py['ignore_tags'] = []
py['relatedstories_header'] = ""

What a mess! None of it is documented in the plugin file.

This is my first post with PyBlosxom. The date for this post is part of the filename, and the pyfilenamemtime plugin will make PyBlosxom use that date for displaying the entry, rather than the file timestamp.