Related Post

Viewing 2 Comments

    • ^
    • v
    I wouldn't call this a correction to the story. The facts are that on one day, the data wasn't there. Supporting elements to the story were that the users were complaining in the forum for a few days about the missing feature and being ignored. Also, the FeedBurner blog was completely silent. I sent an e-mail to one @feedburber.com e-mail I had, but never got a response. So my post was absolutely true, and not in a rush to publish, per se. Whether it was a bug that got fixed, or a PR issue that got resolved doesn't really matter, as FeedBurner did the right thing by resolving it, posting publicly on my blog, and writing back to TechCrunch, who would have made the story a lot bigger had it gone unanswered. I don't think I jumped the gun at all, just raised the issue publicly. Others... as they tend to do... followed on and spun it in their own way. I even had the graphic I used from my own site, with my own stats, "Borrowed" from one of the site's following.
    • ^
    • v
    I figured you would have attempted for clarification on the matter from Feedburner themselves and you did leave your post with an open question which gave them an avenue to answer to the problem.

    And given the data you had I can see why you went ahead with the story. If anything it showed Feedburner that not dealing with a problem - assuming that this was a bug related issue - isn't necessarily a good way of dealing with all. It only causes folks like you and I to write about it and raise questions concerning the whole affair.

    But I was right though - you were the first to respond with a correc .... errr ... followup post :)

Trackbacks

close Reblog this comment
blog comments powered by Disqus