Once more on weblogs, newsaggregators and responses

Sharpreader

Having allready blogged about RSS Bandit and NewsGator I took a look at sharpreader, another newsagregator, this time. Sharpreder looks and feels a lot like bandit without a built in browser. All worked fine but a little extra option puzzled me. In the context menu is an item “Link Cosmos'” which directed me to Tecnocrati. What that is excatly is not clear, seems to be some kind of blog-watcher. I can become a member for a couple of $’s  year. The info given is not very clear, I read things like “Get alerted when your Google Ranking changes”. Yuck, not my cup of tea. This is the only extra thing I can find in Sharpreader. The other extra, grouping posts, is found in Bandit and the DNJ weblog as well.

I will stick with RSS bandit. Please don’t take my opinion on the tools too serious. It is just my short impression between installation and (temporary) adoption or uninstall. As Donny knows I am not very patient :/ So if you really want to know what a tool is like you have to try it yourself.

Grouping posts

Using the aggregators, toying with .TEXT , it’s source and database as well as browsing the dnj weblogs I am beginning to get the idea how aggregators group posts. Every post has a full URL which points to it, like http://dotnetjunkies.com/weblog/petergekko/posts/984.aspx. A post can contain a link to another post, I just did so typing (copying in) the URL into this very post. Bandit (and sharpreader) will add a treenode with the link. It will do the same with the post linked too, there it will add a treenode with a link back to the post. .TEXT seems to do this by analyzing the content of the post, looking for URL’s. 😕

In a weblog you can add a comment. This comment has its own url as well, like  http://dotnetjunkies.com/weblog/petergekko/posts/987.aspx  (The URL’s used here are real life, feel free to try them. Inspecting the .TEXT database shows all posts and their comments happily together in the blog_content table. Every post has a a parentID field. In a normal post this is -1, in a comment this the ID of the post on which this post is a comment. This info is enough to build a full tree of comments and comments on comments. You can add a comment on a comment by browsing to the URL of the comment (there is no link to that on the page, you have to use the address bar) and add the comment just as you would enter a comment to a post. The comment ends up in the .TEXT database with the ID of the comment commented on as ParentID. Alas this is to much for Bandit, Sharpreader or .TEXT. Comments on comments don’t show up. But the info is there in the database so you can create visual threads Outlook express style in blogs.

On my wishlist.

Peter

This entry was posted in Uncategorized. Bookmark the permalink. Follow any comments here with the RSS feed for this post.
  • Scott Watermasysk

    Actually, .Text does not support comments to comments…

    I guess with the current db structure it is 100% possible…but at the moment, it does not happen. All comments are directly related to the current post.

    -Scott