RSS, OPML and the XML platform.
|
As promised, here's the poll to determine who are the top RSS thinkers. Thanks for the nominations. Vote closes May 6th.
I thought it would be interesting to poll my users as to who they think are the top RSS thinkers. That is, people in the industry who've contributed the most to the RSS debate. Let's start by compiling a list and then I'll create a poll. Who else should be added to this list?
Earlier this week, Google sent me the following email [extract only].
We wanted to inform you that we are planning to conduct routine maintenance to Google Calendar between 8AM and 9PM on Thursday, April 26th, 2007 .
I asked myself when is the last time Microsoft said that Outlook would have a 13 hour maintenance outage. Now, I don't use Outlook, but I can't imagine big corporations viewing Google's planned outage email and not locking into Outlook and Exchange for another 5 years.
I'm finally giving up on Twitter. I never got it and the constant bugs have driven me off the cliff. When I first signed up, I wanted to get the twitter messages on my phone, but for the longest time, I never received any messages at all. I then switched to Gtalk and that seemed to work, although with bugs (duplicates, missing). I then tried SMS again and nothing happened for a day. I switched back to Gtalk and it worked again. Twenty-four hours after I should've received the SMS's, they started to trickle in. Today, I can't post with Gtalk either. Are people really having better successes? Or are you guys simply very tolerant of all the bugs?
Scott Kingery has been complaining about Blogger being broken for quite awhile. In particular, he mentions that Blogspot blogs were still working, but self hosted blogs are not. There's a lot of angry people on the Blogger Help Google Group. Fed up with the lengthy outage, Scott has dropped Blogger and is now hosting using Wordpress.
For those that haven't heard yet, I sold Rmail to NBC.
I just got an email from Mark Pincus, founder of Tribe.net, where he discusses some recent changes at Tribe, including the following...
we sold the software to Cisco and most of the engineering team went along with the deal to reduce overhead.
I guess we can expect something from Cisco in our future. Tribe was one of the first online social networks, but has struggled in recent years. I can only assume with less engineers, new features aren't in the pipelines and bug-downtown will increase.
There's an awesome video making the rounds that tries to explain RSS for non-geeks. RSS in plain English instead of 1337. It's begging for some Digging.
http://www.commoncraft.com/rss_plain_english
http://digg.com/software/RSS_in_plain_English
Bloggers (and podcasters) now have their own magazine called Bloggers and Podcasters. With the Scobleizer on the cover of the first issue. The magazine has the required blog.
http://www.bloggerandpodcaster.com/
http://www.bloggerandpodcaster.com/theblog/
Andy Beal is asking if Viacom has a vendetta against Google. As I read this, here is what I came up with.
I'm betting there are more dots to connect, but clearly these guys should be getting along.
http://www.businessweek.com/technology/content/apr2007/tc20070424_455959.htm
Using Twitter and subbing to more than a handful of people creates a lot of noise. So much, that I have to sub some twits. Here are some reasons why I would be unsubbing your twittering.
I'm really thinking there's some great opportunity in Google's new AJAX Feed API. If you have a webpage that is a little thin on content, then you can use this service to add a little sidebar content. Let's go thru the steps of creating a bit of content using the API.
<script type="text/javascript" src="http://www.google.com/jsapi?key= ABQIAAAAAZAuqPpFrGeqNPBaRfnITxTW_YhViUY2BmmapWxnImsMBV7_XxQkg7DpGOrCCwM_GPvj50MfOhc9sg"></script>
<script type="text/javascript">
google.load("feeds", "1");
function initialize() {
var feed = new google.feeds.Feed("http://rss.groups.yahoo.com/group/rss-public/rss");
feed.load(function(result) {
if (!result.error) {
var container = document.getElementById("rsspublic");
for (var i = 0; i < result.feed.entries.length; i++) {
var entry = result.feed.entries[i];
var div = document.createElement("div");
div.appendChild(document.createTextNode(entry.title));
container.appendChild(div);
}
}
});
}
google.setOnLoadCallback(initialize);
</script>
<div id="rsspublic" style='border: thick solid orange;'></div>
Now, let's paste this into the blog entry
Note that you don't actually get all the entries. This is because you're not actually pulling the real RSS feed, but rather the version in the Google feed cache. In this case, I'm assuming that the Google does not cache older entries.
A pretty basic sample and very easy. Throw in a bit of formatting styles and you've got yourself some sidebar content.
The big blogosphere news of the day is that MySpace has released a Digg-like application called MySpace News. I'm gonna have to agree with Pete Cashmore and say it Kinda Sucks!
The bad...
The good...
Around the blogosphere...
I think there's concensus that this isn't impressive.
Have you noticed that everybody is jumping on the RSS bus lately?
The RSS Bus!
Originally uploaded by pheezy.
Whenever I try to post new links to del.icio.us, I get this same error.
Another great startup killed by Yahoo!?
Update: Joshua Schachter told me it was a temporary database issue. It seems to be fixed now!
Google has created an AJAX accessible feed cache called the Google AJAX Feed API. I've gotta figure out what Google's business angle on this is. It looks like they are simply trying to be good citizens. This is an extraordinary service that could be used to create an AJAX-based RSS reader like Google Reader without having to worry about the details of fetching feeds. Very cool!
Steve Rubel thinks that Web 2.0 is now out-of-control and is predicting a downturn.
Once the economy tightens - and it will, the Web 2.0 economy will cave and there will be a healthy shakeout.
Rogers Cadenhead points us to an interesting RSS extension introduced by Yahoo! Simply add the <xhtml:meta> element to control how Yahoo! indexes your feed. I assume this element is added as a child of the <channel> element.
<meta xmlns="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
http://publisher.yahoo.com/rss_guide/faq.php
Update: Sam Ruby has pointed to two more means of accomplishing the same with Bloglines and Google/LiveJournal.
http://tech.groups.yahoo.com/group/rss-public/message/1279
To prevent Bloglines from indexing your feed, you can use...
<access:restriction xmlns:access="http://www.bloglines.com/about/specs/fac-1.0" relationship="deny" />
For Google and LiveJournal, you can use...
<indexing:index="no" xmlns:indexing="urn:atom-extension:indexing" />
This is likely a good opportunity for the RSS Advisory Board to bring consensus.
Kent Newsome brings up a concern with Twitter that is pervasive in the blogosphere. Many conversations are one-way. He's also suggested that he'll unsub any twits that don't appear to be listening to him. I ask why this isn't happening in the blogosphere? Why do people persistently link to a-listers, who thru no fault of their own, don't have the time to respond to everybody. The blogosphere and twitter is about two-way conversations. Persistently linking to the same a-lister for that once-a-month or two return link is not a conversation. Kent has some great advice. Start talking with people that are listening to you.
http://www.newsome.org/2007/04/just-nod-if-you-can-hear-me.shtml
I'm moving The RSS Blog to a new location. Instead of a subfolder on kbcafe.com, it now has its own domain. There may be problems at first, please report them to me. All the archived items will remain on kbcafe and only new entries will be here.
AOL has begun using FeedBurner to publish and manage its RSS feeds. "We'll be providing AOL with detailed analytics about how its content is consumed beyond the AOL Web site -- such as within widgets, in feed readers and on blogs -- to help...
Dave Winer has created a new static version of Harvard's RSS website.
Henry Story on micro-killer apps...
Web 2.0 is all about micro killer apps. These are killer apps that are so simple its difficult to explain them to people. Each one of them does one tiny little thing very well. del.icio.us does bookmarking right. flickr does photo sharing and tagging. RSS/Atom helps keep track of changes to resources. Small is beautiful.
http://blogs.sun.com/bblfish/entry/the_micro_killer_apps
Henry is 99% correct. Web 2.0 IS about micro killer apps. I disagree that del.icio.us and flickr remain micro killer apps. They were micro killer apps. Now they are just micro apps killed by Yahoo! The set of micro killer apps is going to be in constant flux. MySpace and YouTube were also in that set. Today, MySpace is a cash cow and YouTube is no longer micro. Twitter is the newest Web 2.0 startup in that set.
Somebody pumped Scoble's link blog into a Twitter profile. Now you can get Scoble's linkblog on your phone or IM. That's a pretty cool user mashup.
http://twitter.com/scobleslinkblog/with_friends
http://scobleizer.com/2007/04/12/my-link-blog-on-twitter/
Last week, I blogged about Sam Ruby's trouble with RSS clients that keep requesting his old feed. Most of the response was WTF? Most developers didn't understand. I thought it was time that I went over this issue in order to disseminate this knowledge. When processing RSS requests, their are two HTTP responses which have special meaning that affect the life-cycle of the feed.
HTTP/1.1 301 Moved Permanently Location: http://feeds.feedburner.com/TheRSSBlogIn some case, the client software may want to prompt the user to confirm if this action is acceptable or if it should be ignored. In any case, the client should redirect to the new location.
HTTP/1.1 410 GoneAgain, the client software may want to prompt the user to confirm the feed removal.
Today, I added the Digg This javascript widget to compliment the existing del.icio.us one. The script is quite simple. Hope you like it!
<script src="http://digg.com/tools/diggthis.js" type="text/javascript"></script>
Technorati has a new widget that displays your blogs authority. Sample below.
The number is actually the number of blogs that link to you.
Technorati announced they have acquired PersonalBee.
I noticed today that twitter is creating an enormous amount of micro-content. Check this page. I don't see any reason why they couldn't ad some advertising to this micro-content later. All of this could be indexed by Google and generate a large number of referrers. Not the greatest business model, but could work.
http://twitter.com/kentnewsome/statuses/25289191
BTW, I finally got some SMS from Twitter. Unfortunately they were 24 hours delayed. The SMS that I shoulda received yesterday arrived today.
And of course, Kent Newsome is having trouble w/ LiveWriter to Blogger.
Update: Someone replied to this comment with a private email saying "the reason your sms was delayed is probably your network provider's (a.k.a., phone company) gift to you..." But I get SMSes all the time and they usually arrive immediately.
Twenty08 has released a plugin for AppleTV that reads RSS feeds. Support for Atom and video feeds is still on the to-do list.
I just noticed that BubbleShare has dropped the easy upload model that made the service popular. Now, you have to login to upload and share pictures.
Disclosure: I was the original Development Manager at BubbleShare and was a big pusher of the EASY model.
I've had twitter forwarding to my phone for the last 24 hours and I have yet to receive an SMS from them, even though I've clearly got lots of blurbs. I'm going to re-enable GTalk, since I get at least some of the blurbs there.
Rok Hrastnik points us to two new RSS services by Amazon. They now offer RSS feeds for product discussion forums and customer reviews by author.
I thought it might be interesting if I just list my top Web 2.0 bloggers. That's the people that I think write the best material on the Web 2.0 thingy. Note, I said bloggers and not blogs. Some of these guys share blogs with other bloggers. I'm specifically referring to their posts. The list is seven thirteen, that's because I found that many worthy. Feel free to leave a comment as to what other Web 2.0 bloggers you feel are worthy (no, not him).
According to the Photobucket blog, all photobucket widgets are now being blocked by MySpace. We haven't heard yet why MySpace made this move. This could be an evil play to get Photobucket users to switch to MySpace. How loud can you say evil? MySpace might also suggest that Photobucket has a lot of copyright-violating images and video. In the meanwhile, if you edit your MySpace profile, then when you save, all your photobucket widgets will get removed.
If you hear the whys from MySpace, then please post them here.
http://blog.photobucket.com/blog/2007/04/breaking_news_p.html
Robert Scoble thinks its in MySpace's right to block Photobucket. He's correct. But pissing off users isn't a great strategy for a consumer Web 2.0 startup.
Snipperoo calls it Widget Wars. Of course, Snipperoo is in the business of widgets and I'm sure they feel targeted.
Om Malik reminds us that this isn't a first.
Jason Chervokas points out that Photobucket images remain unblocked. It's only the videos.
StartupSquad repeats my suggestion that this might be an attempt to resolve copyright issues. They seem to have tried to post multiple videos to MySpace. Those that were copyright violations did not work. Those that were not copyright violations did work.
Todd Watson points out that the About Us webpage for MySpace says that "you can share photos, journals and interests." Note the absense of videos.
Greg Sterling says that this Web 1.0 attitude means MySpace is not a "Web 2.0" company.
Duncan Riley wonders if Photobucket is "screwed, or just plain screwed over." That is, can they survive without MySpace traffic?
I'm really amazed that people speak so highly of Twitter. I've been using it for the last week or two and I've noticed that it doesn't work more often than it does. Points:
Maybe it's just a bad week, but Twitter seems completely unreliable to this user.
Update: Also, I've never yet receive a twitter blurb on my cell phone via SMS. Only via Gtalk.
Top tips for implement RSS auto-discovery on your blog, your blogging system or your RSS client.
One of the most effective ways of getting your blog indexed is to ping a site called weblogs.com. Just recently, I added ping code to some new blogs and within moments Technorati was indexing these blogs like mad. Proof positive that Technorati is still using weblogs.com to find updated blogs. There are two ways of pinging the weblogs.com ping service. You can use a simple REST-like interface or an XML-RPC interface. The XML-RPC interface is slightly complex, so I've always opted for the simpler REST-list interface, but I'll describe both here.
XML-RPC Ping
The XML-RPC interface involves posting a small XML fragment to a specific URI. The URI is http://rpc.weblogs.com/RPC2. A sample XML fragment is shown.
<?xml version="1.0"?>
<methodCall>
<methodName>weblogUpdates.ping</methodName>
<params>
<param><value>The RSS Blog</value></param>
<param><value>https://rssweblog.com/</value></param>
</params>
</methodCall>
There is also an extended ping with three additional parameters, one of which is optional. The first parameter is the address of the webpage that has been updated, the second parameter is the address of your RSS feed and the third parameter is a delimited list of categories related to your blog. A sample XML fragment for the request follows.
<?xml version="1.0"?>
<methodCall>
<methodName>weblogUpdates.extendedPing</methodName>
<params>
<param><value>The RSS Blog</value></param>
<param><value>https://rssweblog.com/</value></param>
<param><value>https://rssweblog.com/</value></param>
<param><value>http://feeds.feedburner.com/TheRssBlog</value></param>
<param><value>rss|opml</value></param>
</params>
</methodCall>
The response will be another XML-RPC package that contains an error code and message.
<?xml version="1.0"?>
<methodResponse>
<params><param><value><struct>
<member><name>flerror</name><value><boolean>0</boolean></value></member>
<member><name>message</name><value>Thanks for the ping.</value></member>
</struct></value></param></params>
</methodResponse>
An flerror value of 0 indicates there was not error. If the value is not 0, then it should be 1 and the message parameter will contain details of the failure.
REST-like Ping
Although the XML-RPC ping is only slightly complicated, I prefer to use the REST-list ping because it is trivial. In this case, you execute a very simple HTTP GET or HTTP POST request with two required parameters and one optional one. The first parameter is the name of the blog that has been updated. The second is the url of the blog's homepage. The third and only optional parameter is the address of the blog's RSS feed. Sample shown with only the two required parameters.
http://rpc.weblogs.com/pingSiteForm ?name=The+RSS+Blog &url=http%3A%2F%2Fwww.kbcafe.com%2Frss%2F
You can also simply enter this URL in a web browser's address bar to accomplish the same. Sample C# code follows.
Uri pingUri = new Uri( string.Format ("http://rpc.weblogs.com/pingSiteForm?name={0}&url={1}&changesURL={2}",
UrlEncode(title), UrlEncode(link), UrlEncode(rss)));
WebRequest request = WebRequest.Create(pingUri.AbsoluteUri);
request.GetResponse();
Google Blog Search
I did notice that these same blogs were not appearing in Google blog search yet. I thought at one point Google was using weblogs.com to populate its database, but I assume that has stopped. The REST-like code above will also work for pinging Google Blog Search, but the formatted string changes slightly and takes only one parameter, the address of the RSS feed.
Uri pingUri = new Uri( string.Format("http://blogsearch.google.com/ping?url={0}",
UrlEncode(rss)));
Other Ping Services
There are many other ping services, but the vast majority of them have very few users and many of them simply don't work. If the ping above doesn't get you indexed by Technorati, then you might consider their XML-RPC ping interface.
This guy is pretty excited about RSS.
Continuation in a series of explanatory blog entries on RSS, today I wanted to explain how conventional RSS polling works.
Not Push
Remember first that RSS is not push. It's polling. The conventional way of implementing alert technology is via push because experience has taught us that push scales more effectively than polling. There were several attempts to create pushing protocols on the Internet, but they failed because network administrators were blocking incoming Internet connections to combat viruses. This is why RSS became so popular, because it broke thru the firewalls by using polling. Finally, we had alerts on the Internet.
Once an Hour
Nobody ever told us how often to poll an RSS feed, but most of the original RSS readers polled the feeds by default once every hour. This convention has persisted and even today many RSS aggregators continue to poll feeds once per hour. Based on my own evidence, the average RSS reader polls a feed about eight times per day. Why not 24 times? Because many RSS clients are native and only poll when the user is logged-on or even active.
TTL
Beyond the once an hour rule, RSS does have a few elements that give the readers hints about when they should be polled. The first such hint was <ttl>. This was originally put into RSS in order to accommodate peer-to-peer clients like Morpheus. The idea was that the RSS feed could live in a P2P network for seconds equal to the <ttl> before it is re-fetched from source. Unfortunately, RSS never took off in the P2P world and P2P itself has struggled to stay alive. Some publishers and aggregators have started to use <ttl> as the default polling interval in place of the 1 hour default. In fact, aggregators that cache feeds on behalf of many readers should always respect the <ttl> as a ceiling for how long they are allowed to cache the feed before refreshing.
skipHours and skipDays
Two other elements that affect how often a feed is polled are skipHours and skipDays. Unfortunately, these elements are rarely implemented or respected. Their application is obvious, but there are holes in the implementation. Theses element will contain a list of <day> and <hour> elements when RSS client should avoid taxing the source will excessive polls. The issues behind the elements are too confusing to be covered in this blog entry. I'll discuss them later in a separate entry. Just remember, these elements are rarely used or respected, so I would worry too much about implementing it perfectly in your own RSS application.
Weblogs.com
The last method that I'll discuss here was a key part of the early blogosphere. A website was created by Dave Winer that aggregates data of which blogs were recently updated. The website is called weblogs.com. Millions of blogs and RSS feeds are pinging this website each and every time they are updated. An aggregator that is polling a lot of feeds should pull the shortChanges.xml file on this website to determine which blogs have been recently updated. You can poll this file about once every 5 minutes for best results. The shortChanges file will contain a list of blogs that have been updated in the last 5 minutes. You can also pull the changes.xml file on this website once every hour. This changes file contains a list of blogs that have been updated in the last hour.
If you are writing a RSS aggregator, then I hope you'll take advantage of these techniques to better your polling behavior and reduce your bandwidth. Now go code something.
I configured the DNS and setup the Web server. Now, it's a matter of porting the data. Almost there.
This last week, I pointed to some flawed thinking about RSS. In particular, about how to determine if an <item> in an RSS feed is new content. Today, I realized that I pointed to the flaw, but didn't tell you how to do it better. The author suggested using <pubDate> as an indicator of new content. Of course, this doesn't always work as some RSS items update their pubDate when the item is modified. The best approach is to use the <guid> element, but even the guid element is optional. With all these optional fields and with RSS 1.0 and multiple version of Atom to worry about, just what is a developer to do? What I did was write a small little function that either returns the guid from an RSS item, or derives one from the remaining content. The algorithm is really simple, this is Really Simple Syndication. Here's the pseudo code:
if (exist(item.guid)) return item.guid.text;
if (exist(item.link)) return item.link.text;
if (exist(item.pubDate)) return item.pubDate.text;
if (exist(item.title)) return item.title.text;
if (exist(item.description)) return hash(item.description.text);
if (exist(rss10:item.link)) return rss10:item.link.text;
if (exist(atom03:entry.id)) return atom03:entry.id.text;
if (exist(atom10:entry.id)) return atom10:entry.id.text;
Since an RSS item must have at least one of <link>, <title> and <description>, you can always derive a unique id for RSS feeds. Now it's simply a matter of comparing the result of this function to the results of previously sent items and you know if this item is new content or not.
Please leave a comment, if you have ideas on how to make this better. I'm gonna try to write more information articles like this one going forward.
Michael Jensen is tracking the Why I Blog meme. By doing it manually, he was best capable of putting the tree back together. This is something that is missing from meme site like TechMeme, which simply put Robert Scoble at the top (or whatever other a-lister) and don't get to the root of the conversation.
I acquired a new domain where I'll be hosting this blog at some point in the future.
Dave Sifry published his State of the Blogosphere report, which he now calls State of the Live Web. Highlights:
Sam Ruby has been responding to RSS requests with permanent redirects and gone statuses for a year. It appears nobody is listening. My Rmail code worked. Hundreds of Google Reader users are being denied Sam's wit. Anybody working at Google should send this document to the Google Reader product manager. Or for that matter, send it to all RSS developers.
Alex Iskold at Read/WriteWeb brings up several misunderstandings of what RSS is in his article today called The Future of RSS. I want to point out these flaws and misunderstandings so that people don't make the same mistakes Alex made. Let's start with the basics. The RSS that he presents is invalid. In fact, if you try to validate it, then you don't get much of a response other than this is not RSS.
<channel> <title>Read/WriteWeb</title> <link>http://www.readwriteweb.com/</link> <description>Web Technology news, reviews and analysis</description> <lastBuildDate>Mon, 02 Apr 2007 15:23:01 -0800</lastBuildDate> <item> <title>Morfik Patents AJAX Compiler</title> <description>Morfik Patents AJAX Compiler...</description> <link>http://www.readwriteweb.com/...</link> <category>News</category> <pubDate>Mon, 02 Apr 2007 15:23:01 -0800</pubDate> <author>Richard MacManus</author> </item> <item> <title>EMI Music DRM-free</title> <description>Morfik Patents AJAX Compiler...</description> <link>http://www.readwriteweb.com/...</link> <category>News</category> <pubDate>Mon, 02 Apr 2007 15:23:01 -0800</pubDate> <author>Richard MacManus</author> </item> </channel>
He made two mistakes in writing this sample RSS. First, he forgot to wrap the RSS in the root <rss> element. Further, he uses the <author> element inappropriately. The <author> element must be an email address. It could be of the form <author>randy@kbcafe.com</author> or <author>randy@kbcafe.com (Randy Charles Morin)</author>, but it cannot be simply the author's name. If you want to put the author's name without an email address, then you should use the Dublin Core creator element (sample shown).
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Richard MacManus</dc:creator>
I rewrote his RSS using proper semantics. You can download it here. But even this version lacks the recommended <guid> element. That's not so much an error, but it makes your RSS less useful, as you'll see later.
Alex also makes a lot of common mis-statement about RSS. Let's address each.
pubDate Does Not Indicate New Content
Alex says:
The on-demand aspect of RSS is enabled by two timestamps - the lastBuildDate in the channel indicates the last time this channel changed, while the pubDate of the item indicates when the item was published. RSS aggregators (a.k.a. RSS readers) take advantage of these timestamps to decide when new content is available.
I'm sure many RSS aggregators use the pubDate to determine new content, but this is incorrect. For instance, an item could be re-published and the pubDate may move forward. This does not make it new content. RSS aggregators should be using the <guid> element to determine if an item is new content. Remember that missing element I mentionned earlier. In the case where this element is missing, RSS aggregators use a variety of techniques to determine which elements are new. Some use the pubDate, but that element is also optional and is not always present. Some use the title, again, it's optional too. Regardless, when a <guid> is present, it's the only valid element that should be used to determine if there is new content.
RSS is Not Push
Alex says:
RSS is basically a filtered push - the user subscribes (pulls in) to channels that he/she likes, and after that content is delivered automatically.
RSS is not push and it's surely not filtered push. RSS is actually based on polling, not push technology. Further, filtered push is where items are filtered based on some sort of preferences and pushed. I don't see what this has to do with RSS.
RSS Can't Do Everything
Alex says:
Suppose your bank wants to deliver you statements in RSS instead of email. However if you use RSS as it is today, then the bank statements would need to be encoded in HTML - meaning no financial application would be able to manipulate the data. When your Quicken software connects to the bank, the information gets downloaded in a structured format. But with RSS, it is simply not possible currently - because there is no way to describe bank transactions using standard RSS.
What he is saying is that you cannot transmit banking information to banking software using RSS without using an extension. This is not actually true. You could easily use microformats to do this. But what is really puzzling about this statement is why do you need RSS as an envelop for financial data in the first place. We have OFX, which predates RSS and works just fine. RSS can't be expected to do everything. Not that it can't. You can also use RSS as an envelop for OFX, but why not just use OFX? I don't expect my dishwasher to do the laundry, even if it can.
I've been testing Twitter this week. I set it up to ping my cell phone (SMS) and GTalk. Twitter confirmed both setups, but I've yet to receive any updates. Anybody know what I might be doing wrong, as it does not appear to work.
Robert Scoble is asking Which blogosphere search engine is now better? I think we mostly agree that it's either Technorati or Google Blog Search. But which? I guess that depends on what you want in a blog search engine. I search quite often for people that are liking to me.
Both have a porn blog listed on Blogspot listed as my most recent referrer. Frustrating! At the moment, Google is giving me better results in terms of actual non-splog non-porn referrers. Google is always faster; sub-second versus Technorati which takes 1 to 15 seconds, sometimes more.
David Sifry showed us the numbers behind Technorati. They are still growing; pageviews are up 141% in the last quarter. Congrats!
As part of Dave Winer's effort to bring sanity to Harvard's RSS website, he has added a namespace to Harvard's RSS. The namespace was required in order to host a copy of the RSS spec on an Apache server. In order to comply with this latest version of RSS, you put all the RSS elements in the namespace http://blogs.law.harvard.edu/techdev. Sample shown...
<rss xmlns='http://blogs.law.harvard.edu/techdev' version='2.1'>
<channel>
...
</channel>
</rss>