<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Scribkin - Latest Comments in What I Need is a Universal Receptor Protocol</title><link>http://scribkin.disqus.com/</link><description>where code and culture converge</description><language>en</language><lastBuildDate>Sun, 25 May 2008 19:42:53 -0000</lastBuildDate><item><title>Re: What I Need is a Universal Receptor Protocol</title><link>http://www.scribkin.com/2008/05/22/what-i-need-is-a-universal-receptor-protocol/#comment-528670</link><description>Oh man, very cool.  I wish I was more of a developer, this is really good stuff.  Thanks for digging up the links!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">eng1ne</dc:creator><pubDate>Sun, 25 May 2008 19:42:53 -0000</pubDate></item><item><title>Re: What I Need is a Universal Receptor Protocol</title><link>http://www.scribkin.com/2008/05/22/what-i-need-is-a-universal-receptor-protocol/#comment-525519</link><description>I did a little more research. If you can find an XMPP server that supports&lt;br&gt;some certain extensions, you would be nearly to your goal of the open&lt;br&gt;receptor!&lt;br&gt;&lt;br&gt;Namely,&lt;br&gt;&lt;a href="http://www.xmpp.org/extensions/xep-0060.html" rel="nofollow"&gt;http://www.xmpp.org/extensions/xep-0060.html&lt;/a&gt;&lt;br&gt;&lt;a href="http://www.xmpp.org/extensions/xep-0049.html" rel="nofollow"&gt;http://www.xmpp.org/extensions/xep-0049.html&lt;/a&gt;&lt;br&gt;&lt;a href="http://www.xmpp.org/extensions/xep-0002.html" rel="nofollow"&gt;http://www.xmpp.org/extensions/xep-0002.html&lt;/a&gt;&lt;br&gt;&lt;a href="http://www.xmpp.org/extensions/xep-0030.html" rel="nofollow"&gt;http://www.xmpp.org/extensions/xep-0030.html&lt;/a&gt;&lt;br&gt;&lt;br&gt;Some of those sound like it would really help your protocol. Especally that&lt;br&gt;subscribe publish one.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">DuckofDeath87</dc:creator><pubDate>Sat, 24 May 2008 19:43:03 -0000</pubDate></item><item><title>Re: What I Need is a Universal Receptor Protocol</title><link>http://www.scribkin.com/2008/05/22/what-i-need-is-a-universal-receptor-protocol/#comment-523624</link><description>Sweet!  In fact, I used to manage an XMPP-enabled server at my last job, a product called &lt;a href="http://www.communigate.com/" rel="nofollow"&gt;CommuniGate Pro&lt;/a&gt; (basically an Exchange server clone).    We weren't using that part of the software and it wasn't documented well, but definitely supported.&lt;br&gt;&lt;br&gt;Thanks for giving me a direction to start looking in.  I had completely forgotten about it.  I guess that reveals an embarrassing lack of research on my part.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">eng1ne</dc:creator><pubDate>Sat, 24 May 2008 09:06:19 -0000</pubDate></item><item><title>Re: What I Need is a Universal Receptor Protocol</title><link>http://www.scribkin.com/2008/05/22/what-i-need-is-a-universal-receptor-protocol/#comment-523027</link><description>XMPP. It is all about presence. Couple that with offline message retrieval (XEP-0013) and filetransfers (XEP-0096)&lt;br&gt;In theroy, a blog could also have a XMPP account. It could "message" its subscribers. if the server supported it, the server could send one message to a lot of folks. &lt;br&gt;&lt;br&gt;My understanding is that it handles meta data well. I have never heard of it being use like this, but I think it could work. Couple it with a completely different GUI than most normal IM clients and you would be in business! &lt;br&gt;&lt;br&gt;Best of all, the hard part is already done! There are already xmpp servers running. &lt;br&gt;There would still be a lot of work to get what you want, but I feel that your main thing is the push protocol, and XMPP gets that done.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">DuckofDeath87</dc:creator><pubDate>Sat, 24 May 2008 02:05:02 -0000</pubDate></item></channel></rss>