"Norman Rasmussen" <[EMAIL PROTECTED]> writes: > - no one wants to implement pubsub in a client yet, because there's > no need - because no servers/transports/components implement it yet.
This is only half true. ejabberd has an excellent pubsub module (it has not been updated for the latest revisions to XEP-0060, but that is a minor detail in this context). It would be quite simple to write a component that fetches RSS feeds and publishes them to a pubsub node. You would have to decide a payload format (Atom seems appropriate), and then have a client request a subscription to a certain JID+node combination, and display the incoming messages. The client might want to use XEP-0173. Believe me - that's _all_ you need to do RSS through pubsub, and it's the preferred way of doing it, and it's possible today. The rest of this message says much about pubsub (for general education), but nothing of particular interest to make a Jabber client behave like a news reader. The uses imagined for pubsub include things that an ordinary user might want to publish zirself, e.g. avatar (today I'm a cute dog), mood (today I'm happy), activity (right now I'm writing an e-mail), tune (right now I'm listening to The Sound of Silence). These are different from a RSS-ish feed in that the contents is intimately tied to a particular JID, which means that you want to: a) find the "feeds" offered by a certain user, and b) find what user publishes to a certain "feed". Thus PEP was born. With "ordinary" pubsub, "feeds" are identified by a JID+node combination, e.g. JID is rss.example.com and node is "blog_of_legoscia". With PEP, the JID is your JID, and the node is the namespace of what you're publishing to this feed, e.g. [EMAIL PROTECTED] and http://jabber.org/protocol/tune for the User Tune protocol. And the protocol specifies that extensions to presence (namely XEP-0115, Entity Capabilities) are to be used to get automatic subscriptions to desired content. And more… the spec (XEP-0163) is still being changed. This requires quite a few modifications to the Jabber server, and I've started doing that for ejabberd (look at "pep" in the ejabberd-modules SVN tree), however my time is not infinite, and I definitely won't have time to do anything with it until next year. Development tends to happen in occasional chunks. Feel free to ask me about in on Jabber, though. All that said, if someone writes a bot or component that publishes RSS feeds to pubsub as described above, I promise to add support for it to jabber.el, for what it's worth. -- Magnus JID: [EMAIL PROTECTED] _______________________________________________ py-transports mailing list [email protected] http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
