Blog posts....censorship?

So apparently some in the community are under the impression that blog posts in this community are censored - especially if the post is critical of Microsoft.

That is *not* the case.

However, anonymous posts do require a moderator to approve them. So...if the moderator goes on vacation, the posts aren't updated. 

As a matter of practice, posts in this community are set to only receive comments for 30 days - a default setting.  Is 30 days long enough?  60 days?  90?  Does it make sense to have a single blog post thread continue for  over 30 days?  If there is a consensus that blog post duration in this community needs to be modified, please speak up.   

There are several other post threads that could be characterized as critical of Microsoft, and those posts remain...and will continue to.  Of course, obscene language, and/or personal attacks aren't appropriate.  Posts that stray from the thread topic will be either deleted or not published (if waiting for approval).

Happy Friday!

Comments

• Anonymous
  March 28, 2008
  As a blog site admin myself, I HAVE to shut down the comments after 30 days otherwise those older posts just turn into spam catchers.

• Anonymous
  March 31, 2008
  There's ways to implement captcha's or other spam-thwarting techniques... I can't say on this specific blog but I know I've come across old blogs before that were "new to our organization" issues that I would have liked to comment.  In those situations the blogs were closed to new comments. Personally I still find BB forums more useful because of their interactive exchanges and subscribing directly to threads to get responses on new posts.

• Anonymous
  April 07, 2008
  I have been censored more frequently for comments that were straight and on-topic than for comments that wandered or that responded to personal attacks with personal attacks. In at least one case the Microsoft employee who censored my straight on-topic accurate comment also censored the straight on-topic but erroneous comment from another Microsoft employee which my comment was responding to. Closer to home for this blog, a few years ago there was a discussion of MSDN searching, and I was allowed to correct an erroneous statement one time, but I was censored when I tried to correct a second erroneous statement which pretended to reply to my first comment.  Though MSDN searching eventually improved a bit. Sure, blog owners can censor facts as much as they want, they own their blogs.  Just don't expect to gain any credibility when you say it doesn't happen.