<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" > <channel><title>Comments on: See Who Is Linking To Your pPosts &#8211; Try TalkDigger</title> <atom:link href="http://www.connectedinternet.co.uk/2005/08/19/see-who-is-linking-to-your-posts-try-talkdigger/feed/" rel="self" type="application/rss+xml" /><link>http://www.connectedinternet.co.uk/2005/08/19/see-who-is-linking-to-your-posts-try-talkdigger/</link> <description>The latest tech, mobile and gaming news</description> <lastBuildDate>Sun, 14 Mar 2010 10:50:26 +0000</lastBuildDate> <generator>http://wordpress.org/?v=2.9.2</generator> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>By: Anonymous</title><link>http://www.connectedinternet.co.uk/2005/08/19/see-who-is-linking-to-your-posts-try-talkdigger/comment-page-1/#comment-161</link> <dc:creator>Anonymous</dc:creator> <pubDate>Sun, 21 Aug 2005 17:38:55 +0000</pubDate> <guid isPermaLink="false">http://www.siteground128.com/~connecte/2005/08/19/see-who-is-linking-to-your-posts-try-talkdigger/#comment-161</guid> <description>I understand that it can be frustrating to see that PubSub delivers more results than the other services. We here this constantly. As odd as it may sound, it frustrates me as well. I&#039;ve been working very hard for quite some time to get all the feed/blog search and monitoring services to agree to share information about the new data they discover so that we could, in fact, ensure that all services are processing the same data. You should be able to go to Technorati, Feedster, PubSub and IceRocket and see exactly the same data in each service. Your choice between services should be based on what they do for you -- not how much data they have. The mechanism we have been pushing is called the &lt;a href=&quot;http://groups.yahoo.com/group/feedmesh/&quot; rel=&quot;nofollow&quot;&gt;FeedMesh&lt;/a&gt;. Currently, Yahoo&#039;s &lt;a href=&quot;http://blo.gs/&quot; rel=&quot;nofollow&quot;&gt;blo.gs&lt;/a&gt; and &lt;a href=&quot;http://pubsub.com/&quot; rel=&quot;nofollow&quot;&gt;PubSub.com&lt;/a&gt; openly and freely publish notifications of all the feed updates that we discover. Thus, there is absolutely no excuse for any service to not have at least as much data as we do at PubSub.com. The only thing you should expect is that those &quot;selfish&quot; services that read from the FeedMesh but don&#039;t share their own data might be processing *more* data than we do. But, that is not the case. Personally, I think it is very much in the interests of blog/feed publishers and readers to do what they can to ensure that systems like the FeedMesh are successful. It is only through such sharing systems that we&#039;ll be able to even get close to a world in which all the services are processing the same data and they start competing based on the quality of the service they provide rather than they data that they have. Publishers and readers should be insisting that the services they use both read from and contribute to the FeedMesh... One easy way to put pressure on the folk that aren&#039;t cooperating is to simply stop pinging them directly. I believe that blog publishers should simply refuse to ping any site other than Ping-O-Matic (which feeds into the FeedMesh) or a site like Yahoo&#039;s blo.gs or PubSub that are active FeedMesh publishers. The more services we get sharing data via the FeedMesh, the more likely we are to stop the frustration of having to check multiple services to see all the posts that we&#039;re interested in. bob wyman CTO, PubSub.com</description> <content:encoded><![CDATA[<p>I understand that it can be frustrating to see that PubSub delivers more results than the other services. We here this constantly. As odd as it may sound, it frustrates me as well. I&#39;ve been working very hard for quite some time to get all the feed/blog search and monitoring services to agree to share information about the new data they discover so that we could, in fact, ensure that all services are processing the same data. You should be able to go to Technorati, Feedster, PubSub and IceRocket and see exactly the same data in each service. Your choice between services should be based on what they do for you &#8212; not how much data they have.<br /> The mechanism we have been pushing is called the <a href="http://groups.yahoo.com/group/feedmesh/" rel="nofollow">FeedMesh</a>. Currently, Yahoo&#39;s <a href="http://blo.gs/" rel="nofollow">blo.gs</a> and <a href="http://pubsub.com/" rel="nofollow">PubSub.com</a> openly and freely publish notifications of all the feed updates that we discover. Thus, there is absolutely no excuse for any service to not have at least as much data as we do at PubSub.com. The only thing you should expect is that those &#8220;selfish&#8221; services that read from the FeedMesh but don&#39;t share their own data might be processing *more* data than we do. But, that is not the case.<br /> Personally, I think it is very much in the interests of blog/feed publishers and readers to do what they can to ensure that systems like the FeedMesh are successful. It is only through such sharing systems that we&#39;ll be able to even get close to a world in which all the services are processing the same data and they start competing based on the quality of the service they provide rather than they data that they have. Publishers and readers should be insisting that the services they use both read from and contribute to the FeedMesh&#8230; One easy way to put pressure on the folk that aren&#39;t cooperating is to simply stop pinging them directly. I believe that blog publishers should simply refuse to ping any site other than Ping-O-Matic (which feeds into the FeedMesh) or a site like Yahoo&#39;s blo.gs or PubSub that are active FeedMesh publishers. The more services we get sharing data via the FeedMesh, the more likely we are to stop the frustration of having to check multiple services to see all the posts that we&#39;re interested in.<br /> bob wyman<br /> CTO, PubSub.com</p> ]]></content:encoded> </item> </channel> </rss>
<!-- This site's performance optimized by W3 Total Cache. Dramatically improve the speed and reliability of your blog!

Learn more about our WordPress Plugins: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (enhanced) (user agent is rejected)
Database Caching 5/13 queries in 0.008 seconds using disk
Content Delivery Network via cdn2.connectedinternet.co.uk

Served from: host.connectedinternet.co.uk @ 2010-03-14 12:45:24 -->