Where do we go from here?
I’ve been getting hit with a lot of comment spam once again. Strangely enough, I haven’t received comment spam for a while. This is partly due to a little trigger that I have running onmy .Text database that helps check the content before it’s committed to the database. It essentially runs through a few rule checks including the processes of scanning for known words found in typical spam. The trigger isn’t perfect, but it’s effective. Every so often, I need to update the list of words based on the spam I’m receiving. I haven’t had to do that for a while – until now.
Why is spam picking up once again? Maybe there are new “spam” words that my trigger isn’t catching. Frankly, with this new round of spam, I’m getting tired of updating my spam rules. It’s time to hop off the blogging engine that I’ve been using since Day 1. It’s also important to note that this particular blogging engine, hasn’t updated it’s underlying source code since January 2003. It has since rolled into Community Server.
I tried Community Server back in the day, before it was easy to convert the .Text content into CS friendly content. There just wasn’t the ease nor the time to convert all the content back than. Blogging engines have matured and (I’m assuming) their spamming protection has matured as well. The time has come to finally update my blogging engine. The question I have is which engine to I want to “upgrade” to?
I’m struggling with a couple of things. One, now that I’m working for the man, should I jump on over to http://blogs.msdn.com? I’ve seriously considered it. For one thing, my traffic would jump by gazillion fold from ~20 readers to, well, a gazillion. However, moving over to http://blogs.msdn.com would take the control out of my hands. And as we all know, people with Type ‘A’ personalities like to maintain control. Nothing crazy mind you, just the ability to… i don’t know… scan your log files 10 times a day to see who’s linking, reading and searching on your blog. Ok… I don’t scan them 10 times a day… maybe 10 times every few months (I don’t want you to think I’m obsessive).
As I’m sitting here at the Deeper in .NET event in Milwaukee, Scott Hanselman is presenting a session on dasBlog and a behind-the-scenes look on how it works.I’vechecked into dasBlogon a couple of occasions and havealways been intrigued by it. First, it’s built on top of .NET (huge plus), but so is Community Server.dasBlog is file driven vs. database driven. Not a big deal, but it sure is nice to have to have to worry about a database when you don’t have to. dasBlog is stillan open source project found onGotDotNet.com whereas Community Server isnow a product. True, there’s a free version available but it’s stilla commercial product. Being a developer, I like to dig into code to see howother bit-twiddler’s work.
I’m still on the fence. Do Imove to http://blogs.msdn.com and lose all control or upgrade my site to an evolving blogging (and really cool) engine such as dasBlog? I’m sure you (my 20 readers) will find out soon enough.Any help in the decision making process is appreciated.






Dave Bost is a Technical Evangelist for Microsoft and co-host of the Thirsty Developer Podcast.