Changes On This Site

Scott pushed new changes to weblogs.asp.net sometime earlier this week. I hate very strongly dislike them. I don't hate them because the posts are shorter. I don't hate them because they make you click through to the posts. I hate very strongly dislike them for 3 reasons:

  1. No more blog list on the home page. I liked it much better when it was grouped by number of posts. Then, you didn't go to the bottom of the list, because nobody cares about someone who posts 3x and then loses interest.
  2. RSS feed truncation. What's the point in having a feed if you're not going to syndicate the whole thing? I thought there was an optional feature that could be used to do this... why am I being forced to do it if I don't want to? Why is it being forced on my readers?
  3. It doesn't solve the real problem.

So what is the real problem? The problem is, there are too many people blogging here. The question I have is, why on earth are MS people being syndicated in two different uncategorized places? Why do other members of the community have to deal with this crap? Microsoft doesn't like to be called the Borg, but the weblogs.asp.net feed is like being plugged into the Hive Mind. It's a jumbled, disorganized disaster. Microsoft has zero blogging strategy, and it shows.

So, if you're going to shorten the aggregate home page, fine. But you'd go a long way to saving on bandwidth costs if you just moved the Microsoft people to blogs.msdn.com once and for all, and gave weblogs.asp.net back to the community where it belongs.

My point is not so much that I'm bagging on Rob or Scott or anyone else. I'm a huge .Text fan. They're getting a lot of crap right now, and they only kind of deserve it. Some community discussion would have been nice, or some private warning. But my point is that Microsoft as a company has no corporate blog strategy whatsoever, and the community is getting the short end of the stick because of it. Something has to be done, and it's not just ScottW and Rob's problem. It's Bill and Steve's problem.

4 Comments

  • The answer is to host on your own server. You'll note where my blog is hosted. Group blogs will always suffer from these kinds of things. The downside of that is that you don't get as much traffic as quickly. But, it's more sustainable.

  • I couldn't aggree more. If we had better catagorization on the site then people would only subscribe to the stuff that interests them. Hell, if we had good catagories then I wouldn't even offer the "Everything" feed. I think we would save a bunch that way from people only subscribing to things they care about. There are people internally that also have the same concerns. That said...



    Hopefully this is a short term solution to a short term bandwidth cost issue and longer term we can be more stratigic about it.

  • I always enjoy how you speak your mind, Robert. I agree with you.

  • The problem is that blogs.mdsn.com just points to weblogs.asp.net. They're just doing a bit of trickery to make it look like it's coming from a different site. Do an NSLOOKUP on both names, they point to the same IP address.



    Remember the blogs on gotdotnet? They were migrated to weblogs.asp.net.

Comments have been disabled for this content.