Sat, 26 Feb 2005

top

spammers must die (reprise)

permalink

So I've disabled trackbacks since some bastard has started pinging pr0n sites at me, which is not that great of a loss since no one has pinged me since I started using Blosxom as my blogging engine. I wish I could eviscerate these spamming scum.

18:35:09 26 Feb 2005 > /computers/www/blosxom > permalink > 1 comments

Mon, 27 Sep 2004

top

spammers must die

permalink

I just spent a ridiculous amount of time cleaning up the spoor of some spambots targetting Blosxom blogs. I have enlisted the help of Doug Alcorn's modified writeback plug-in and his spam killing tools. We'll see if I can stop these dirty bastards.

18:04:45 27 Sep 2004 > /computers/www/blosxom > permalink > 0 comments

Wed, 23 Jun 2004

top

retrograde consolidation 3

permalink

Retrograde consolidation is a clumsy term, but I'm too lazy to think of something better.

Anyway, this title caught my attention: The Location Field Is the New Command Line.

The article goes on to point out that web applications are fundamentally different from desktop applications—the advantages of the web do not trump the advantages of the desktop, but, as anyone familiar with UNIX would understand, it's all about using the right tool for the job. Do one thing, and do it well.

20:13:40 23 Jun 2004 > /computers/www > permalink > 1 comments

Fri, 23 Apr 2004

top

allow initial numbers in category

permalink

I just realized that Blosxom won't let me use category names that start with a number (like, for example 3p-omni) and this is for good reason: so that dates don't get confused with category names and vice-versa. Of course, I was dissatisfied with renaming the category to something like thirdpersonomniscient, so I decided to hack on the source (which is probably a bad idea, but I can't do this as a plug-in)

The result is this patch that allows you to have category names that start with numbers. WARNING: this has not been well-tested!!! I have no idea what I may have broken by doing this. YOU MAY NUKE YOUR BLOG!!! You have been informed. Usage implies consent.

19:47:09 23 Apr 2004 > /computers/www/blosxom > permalink > 0 comments

Sat, 07 Feb 2004

top

URLs

permalink

I know I have way too much free time on my hands. but I am again contemplating switching blogging engines.

as lovely as Blosxom is, I'm not entirely down with the file-format. it is admittedly very nicely simple: the first line is the title, the rest is output as is (in my case, garden-variety HTML, but other bloggers have implemented other markup languages [ATX][textile][wikiwordish].) but, unlike XML, it is not as easy to spot errors in the markup, particularly with the pre-theme flavor files. (and if you dig around my site for a while, you will see instances plagued by HTML errors such as unclosed <a> tags and mismatched <span> tags.)

so, because of my masochistic nature, I am trying to write my own blog engine based on XML and XSLT. I am a little apprehensive as to what sort of load this will cause to my webhost despite the light traffic, but there is always static rendering, I suppose. In reality, I'll just be writing a more dynamic version of my hand-kludged blog engine that I had been using previously, with more Perl and less XSLT.

I'm still stuck on parsing the requested URL. I have decided on the popular format of /category/subcategory/2004/02/07/slug, although I'm still wondering about the extension. on one hand, slug.html is kinda crufty looking. on the other hand, I like Blosxom's notion of flavors. still, the only other flavor that I can think of that would be worth supporting at this time is RSS, and while good for indices, I can't see the utility of serving up individual RSS entries. and this in itself leads to some parsing ugliness. if I stick to the flavor idea, then my RSS feeds will be specified like /category/subcategory/2004/02/07/index.rss, and I realize that index is pretty crufty. but if I discard flavors entirely, /category/subcategory/2004/02/07/rss would probably be how I should specify a feed, but I think it would cause a parsing nightmare. I think I would have to hard code it, but that also strikes me as inelegant.

so it's still a work in progress. I've spent a couple of days on the parsing routine already, using Blosxom's routine as a take off point. I've also been screwing around with regex's, but I imagine that would be processor intensive. so we'll see.

anyway, I found inspiration about non-crufty permalinks here:

11:39:33 7 Feb 2004 > /computers/www > permalink > 4 comments