It’s funny, yesterday I was thinking of why push techniques aren’t used to communicate between blogs. Then today I read this.
My idea was that blogs could have a list “friends” who are allowed to ping them when they have updated content. Just like blogs now ping weblogs.com for example, using XMP-RPC or REST. It would create small mini-Technoratis all over the blogosphere. So instead of a blog having only its own content it could also have a “buzzing in my network” page. What’s nice with the RWW article is that it reminded me of the Jabber protocol. That could be even more interesting to use in a one-to-many push call. So thinking a step further, why not use(extend?) the protocol to enable features similar to those in site-bound social networks like MySpace, Bebo, Facebook and Twitter. Like display online status, what I’m doing right now and so on.
Every blogger is master of his/her own blog, so there wouldn’t be any privacy issues, just only publish what you are comfortable with. There are millions of blogs, why not network them blog-to-blog?
Update: Through a comment on RWW I found out that this already exists someone is working on something similar.
Update2: The ISS thing seems more focused on messaging. That is not what I’m talking about here even though communication of course would happen through some kind of messages. Tell me if my idea isn’t clear or what you think of it if it is for that matter.

I think XMPP is going to take a while to hit mainstream, and when it does, total shift in the way things operate.
In the meantime, my team is working on something very similar to what you describe — essentially a ping server for web services. Whenever a user on a web service (think 30boxes, Jaiku, YouTube…) updates (adds a picture, writes a post, listens to music…) the service updates a central ping server via XML-RPC and says “User X has updated”. Interested parties can ping the list, do an intersection for who’s update that they care about and then query the web service API for that specific user.
Does that sound pretty close?
Comment by Eric — January 25, 2008 @ 10:56 pm
The functionality is the same but I was thinking that there didn’t have to be one central server. Your solution sounds nice, do you have a website?
Comment by Martin — January 26, 2008 @ 12:25 am
[…] I wrote this yesterday I’ve learned that the means for doing exists and is spelled XMPP. I first heard of […]
Pingback by DevCase » Operation Catch-Up-On-XMPP — January 26, 2008 @ 10:24 am
How about using pub/sub (XEP-60) as the core mechanism? There’s a Internet-Draft that specifies the approach: http://urltea.com/2iab
Comment by Joe Hildebrand — January 28, 2008 @ 5:55 pm
Yes Joe, absolutely. Thanks for the link and your work!
Comment by Martin — January 28, 2008 @ 7:49 pm