30 December 2004

E-feed, Bloglines, 30-Dec-04 UTC 17:55:21

E-feeds that appear in the host like blogger still do not appear in Bloglines.

Appears as though the XML feed does not appear until entire site republished.

Also, each individual entry must be pinged.

As a check Feedster produced no result for this blog entry.

Tests

1. Bloglines does not show the target XML-feed entry

2. Republish the blog: 30-Dec-04 UTC 17:59:57

Results

No changes in bloglines. It appears as though Bloglines only takes the "most recent" XML-feed addition, and does not take things published earlier.

In other words, when BlogLines gets pinged, it does not appear as though Bloglines takes information related to "earlier updates"; rather it only looks as the most recent entry.

If there is no change to the most recent blog-entry in the XML-feed, then Bloglines says, "There's no change" ... even though previously-posted [not published] blog-comments may have been subsequently published, pinged, or updated.

Recommendations

It would be nice if there was a method for the aggregator to look at all blog-comments in the XML feed, rather than the most recent entry, and see what has changed.

Further, rather than relying solely on pings, it would be nice if the aggregators looked at all comments in the XML-feed to see what is updated.

It would be nice if the user did not have to ping after each update, but if the aggregators-pingers worked together to go back in time along the XML-feed to compare the most current information with that which had been previously submitted.

In short, it would be nice if the user, when they pinged the services, could rest assured that the aggregators would compare multiple blog-entries back in time, not just the most recent one.

Having this "backward-comparison" feature in the ping-aggregator interface might assist developers. This would cut down on the number of pings; and increase the quality of the XML-feed in the aggregators.

Users sometimes submit "multiple pings" because they want to make sure that a given feed-entry posts. In some cases, despite the ping the entry does not appear in the aggregator.
E-feeds that appear in the host like blogger still do not appear in Bloglines.

Appears as though the XML feed does not appear until entire site republished.

Also, each individual entry must be pinged.

As a check Feedster produced no result for this blog entry.

Tests

1. Bloglines does not show the target XML-feed entry

2. Republish the blog: 30-Dec-04 UTC 17:59:57

Results

No changes in bloglines. It appears as though Bloglines only takes the "most recent" XML-feed addition, and does not take things published earlier.

In other words, when BlogLines gets pinged, it does not appear as though Bloglines takes information related to "earlier updates"; rather it only looks as the most recent entry.

If there is no change to the most recent blog-entry in the XML-feed, then Bloglines says, "There's no change" ... even though previously-posted [not published] blog-comments may have been subsequently published, pinged, or updated.

Recommendations

It would be nice if there was a method for the aggregator to look at all blog-comments in the XML feed, rather than the most recent entry, and see what has changed.

Further, rather than relying solely on pings, it would be nice if the aggregators looked at all comments in the XML-feed to see what is updated.

It would be nice if the user did not have to ping after each update, but if the aggregators-pingers worked together to go back in time along the XML-feed to compare the most current information with that which had been previously submitted.

In short, it would be nice if the user, when they pinged the services, could rest assured that the aggregators would compare multiple blog-entries back in time, not just the most recent one.

Having this "backward-comparison" feature in the ping-aggregator interface might assist developers. This would cut down on the number of pings; and increase the quality of the XML-feed in the aggregators.

Users sometimes submit "multiple pings" because they want to make sure that a given feed-entry posts. In some cases, despite the ping the entry does not appear in the aggregator.
" />