Sam Ruby wrote: > > Peter Saint-Andre wrote: >> FYI. >> >> The authors plan to finish off this specification in the near future, so >> feedback is welcome. > > Are there any known implementations? In particular, subscribers? I'd > gladly start publishing if I knew that somebody was subscribing...
Chicken, meet egg. Egg, meet chicken. We are pushing hard to get XMPP server vendors to implement the XMPP publish-subscribe extension, on which this atom-notify work depends. That is happening now. We need to wait for that development work to show up in released code (should happen over the next few months), and then for that released code to be deployed. Personally I can't wait to deploy it at the jabber.org service, which runs ejabberd. Once it is deployed in some of the larger XMPP services, I think we'll see more widespread implementation on the client side because we're planning to use it for all sorts of fun social networking applications (real-time tune sharing a la Pandora or last.fm) and user avatars and so on. So the atom-notify functionality will be able to piggyback on that work on the server side and client side (it's just another payload). Also we may see services like Twitter and Jaiku pick it up -- at least I'm leaning on them to do so. ;-) Once this starts to come together I will report back or blog about it or somesuch... Peter -- Peter Saint-Andre https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
