很久没有使用bloglines了，最近Google新发布了RSS Reader。我才想起BlogLines，去上面转了一圈，Google学BlogLines学得很到家啊。但是在大规模数据得存取上，Google明显高出BlogLines一筹。BlogLines后台应该还是延续数据库思维：一定要精确告诉你，你订阅的FEED上有873条新内容，而Google就只告诉你(100+)：因为能翻10页以后的用户不会超过2%。而结合了ajax设计，类似于GMail界面的浏览模式（尤其是列表方式），也是我非常习惯的快速浏览方式。相比之下：Bloglines在速度方面就要差多了。

再仔细看看：BlogLines的新功能，看来，社群化是BlogLines努力的方向之一。另外就是发现了一个claim功能：认领你自己发布的Feed。

认领流程如下： 0 输入你的blog地址：bloglines会分别生成2个key，一个ckey（用于证明你能发表内容），一个ukey（用于证明你能拥有网站）； 1 发一篇blog：里面包含feedkey：

2 修改首页模板：包含一个：

结果：如果bloglines在首页上同时发现了ckey+ukey，并且在feed中只发现了ckey就成功了。

本篇就用作激活贴，激活之后可以将多个重复的数据源index.rdf index.xml atom.xml 标记为重复的feed

2006-10-06 更新：关于BlogLines和ZhuaXia的FEED合并功能首次发布时间，感谢TinyFool和DBANotes提供线索 Have no fear, Publisher Tools are here! − Early last week, Jeremy Zawodny posted about moving his blog and disappointment with how aggregators handle 301 (permanent) HTTP redirects. In fact, there have been a number of high profile bloggers who have recently felt the pain of moving their feed including Robert Scoble and ResourceShelf by our Ask.com colleague Gary Price. Bloglines has always tried to ease the pain of moving your blog. If you set up a 301 redirect, Bloglines will automagically set that feed as a duplicate to the new feed after a week or two. Our customer support team has also responded to requests to mark feeds as duplicates. But we knew publishers needed a smoother process.

Fri, 30 June 2006 10:25:01 PDT http://www.bloglines.com/about/news#108

抓虾的管理员对重复FEED的处理： http://www.zhuaxia.com/blog/?p=42