On Jul 9, 2008, at 1:41 AM, Nick Vidal wrote:
Hi,
Adam Pisoni wrote:
He also would need a way of authorizing flickr to publish to that
node on
his behalf (OAuth)
For this, Nathan's response is perfect:
It's simpler than that. You would "affiliate" Flickr's XMPP
bot/component/whatever as "publisher" to the node
Much simpler indeed. This skips OAuth entirely. XMPP controls your
roster, your nodes, and who has access to these (read/write
privileges).
Actually, OAuth can have its place. You can use OAuth as the protocol
Flickr and the user use to accept Flickr JID as a publisher to your
node. The OAuth component on your jabber server would then add flickr
jid as a publisher of your node.
So OAuth used on the intereaction between Flickr and user, classical
XMPP pubsub to do the enforcing. I think this will probably be the
easier first because right now I don't know many clients that support
control over pubsub nodes.
But neither servers support OAuth. So real life: right now, flickr
would host the pubsub nodes and could use the friends and family
settings plus the connections he already has to keep the whitelist.
Best regards,
--
Pedro Melo
Blog: http://www.simplicidade.org/notes/
XMPP ID: [EMAIL PROTECTED]
Use XMPP!
