The Height of Absurdity

Now spammers of older versions of MT have become totally absurd. As much as I’ve always had trouble understanding the “reasoning” behind spamming comments to lure people to their stinking website, I simply cannot grasp why someone would want to spam with links to websites that don’t exist (i.e., website addresses that are merely a series of random letters), except that for such asswipes with too much time on their hands, it’s probably just a matter of “because I can.” You can’t add all those bogus URLs to a blacklist because there are simply too many, plus they all use bogus IPs.

I know there exists plugins to close off comments. However, with my extensive knowledge of PHP and MySQL, it’ll be just as easy to create my own script that I can set in a cron job and will shut comments after so many days. Alas, I’ll have to manually “rebuild” the blog once in a while, as I’m not about to try to figure out what the heck that whole rebuilding process entails. That rebuilding thing in MT has always struck me as unnecessary and cumbersome. I suspect it’s a vestige of the very early days of MT when there wasn’t any built-in MySQL support.

Sure, it’s a PITA to have to come up with something like this because of arseholes’ idea of fun. However, it’s still not enough to get me to migrate to a new version of MT or an entirely different blogging package. I’m more inclined to develop my own blogging software one day than to do that…

{4} Thoughts on “The Height of Absurdity

  1. Two words: Wlogpress and Textpattern.

    I’m running blogs on each with no spam problems. I still have one client running MT who gets hundreds of spam comments per week, even with all the anti-spam plugins.

    Though, if I ever get around to writing that CMS of my dreams, I’ll just use it. 🙂

  2. And what would be that CMS of your dreams? Mine tries to be at once feature-rich and abstracted so that it can fit as many sites as possible.

  3. Actually, I think my CMS is brilliantly simple! It’s not intended for the home hobbiest to use to setup a site, but for a developer to build a site with a solid back-end the client can use to run the site. Every entry has a list of variables (date, author, post date, pull date, content… whatever’s needed and flexible in the initial setup) and the site can be built to the specific needs of the user.

    I’m thinking specifically of churches who might want to be able to display the same information in a number of different ways. On one page, they’ll want to list the scripture readers for the next 4 weeks. Or, maybe John will want to know which weeks in the next quarter he is reading? From the same database, information will be available to post as calendar events and/or news articles.

  4. Although a hobbyist could figure out how to use my CMS, that’s not the market I’m targetting, either. I’m not working on a souped up blogging script. 🙂 It started with the idea of making maintenance of multiple sites easier and more consistent for me *and* of eventually giving clients full control of their content. For what you’re thinking for churches, I would try to make an abstraction to see if the criteria you have in mind could be applied to another “industry” (if you’ll allow me the poor word choice). Maybe that’s impossible, but if not, then it might be a matter creating a calendar module that could be “flavoured” for specific needs.

Comments are closed.