Comments on: Peer To Peer Blogging http://www.devcase.com/blog/peer-to-peer-blogging Dev, Tech, Web, Stuff Tue, 06 Jan 2009 21:07:29 +0000 http://wordpress.org/?v=2.5 By: Martin http://www.devcase.com/blog/peer-to-peer-blogging#comment-30 Martin Mon, 28 Jan 2008 19:49:00 +0000 http://www.devcase.com/blog/peer-to-peer-blogging#comment-30 Yes Joe, absolutely. Thanks for the link and your work! Yes Joe, absolutely. Thanks for the link and your work!

]]> By: Joe Hildebrand http://www.devcase.com/blog/peer-to-peer-blogging#comment-29 Joe Hildebrand Mon, 28 Jan 2008 17:55:08 +0000 http://www.devcase.com/blog/peer-to-peer-blogging#comment-29 How about using pub/sub (XEP-60) as the core mechanism? There's a Internet-Draft that specifies the approach: http://urltea.com/2iab How about using pub/sub (XEP-60) as the core mechanism? There’s a Internet-Draft that specifies the approach: http://urltea.com/2iab

]]> By: DevCase » Operation Catch-Up-On-XMPP http://www.devcase.com/blog/peer-to-peer-blogging#comment-25 DevCase » Operation Catch-Up-On-XMPP Sat, 26 Jan 2008 10:24:16 +0000 http://www.devcase.com/blog/peer-to-peer-blogging#comment-25 [...] I wrote this yesterday I’ve learned that the means for doing exists and is spelled XMPP. I first heard of [...] […] I wrote this yesterday I’ve learned that the means for doing exists and is spelled XMPP. I first heard of […]

]]> By: Martin http://www.devcase.com/blog/peer-to-peer-blogging#comment-24 Martin Sat, 26 Jan 2008 00:25:31 +0000 http://www.devcase.com/blog/peer-to-peer-blogging#comment-24 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? 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?

]]> By: Eric http://www.devcase.com/blog/peer-to-peer-blogging#comment-23 Eric Fri, 25 Jan 2008 22:56:51 +0000 http://www.devcase.com/blog/peer-to-peer-blogging#comment-23 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? 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?

]]>