Posts tagged: BLOGS

In the past 24 hours I’ve seen a wave of comment spam resembling the late August outage. Mostly porn spam. Is it just me? I’m using the Akismet API from my homebrew code (negatives are simply rejected), but maybe this is a sign that I should start using the feedback part of their API to report false negatives.

This also gets me thinking about the need for an Akismet-like service that is run cooperatively, with multiple servers to avoid the single-point-of-failure problem. (And maybe more liberal licensing.) I think Akismet is cool; it’s just impossible not to think about The Next Cool Thing once the Current Thing starts giving you trouble.

I’ve yanked out my own crude anti-comment-spam tests and replaced them with a nice tidy call to the Akismet API. If this works out I’ll most certainly incorporate it into the Django version of the blog – there’s a nice Python interface as well.

---

seanrox commented on Thu Aug 24 14:58:33 2006:

Akismet is nice and works wonders on comment spam as you’ll see on your site.

The guys over at automattic.com really know their stuff.

…is, according to Technorati, Chinese. And likely will be forevermore.

I’ve recently moved the Wellblogs aggregator to my server from its former home. It’s a simple “planet” style presentation that shows the last week’s worth of posts across a few dozen blogs written by members of The Well.

The software is a Python engine written by Michael Josephson, and I’ve been very impressed with it so far. It’s based on Mark Pilgrim’s Universal Feed Parser, a MySQL data store, Cheetah templates, and some extra bits to gracefully handle the inevitable connection failures involved when fetching dozens of disparate feeds every hour. Getting everything working was a breeze, and as someone doing more web development in Python lately I’m finding the code interesting reading. Hopefully the blogs are too!

Interesting – About.com is moving to WordPress. I also learned from Matt’s blog posting, much to my surprise, that they were using Movable Type before. It feels very significant that the New York Times Company is migrating its $410-million-dollar baby over to an open source content-management platform. The usual open source components further down the stack – Apache, Linux, et al. – don’t have the same implications for feel and functionality that the content management layer does, and therefore this feels like more of a significant endorsement of open source.