[Psi-Devel] Feature request: Handling of im: URIs
stpeter at stpeter.im
Fri Nov 9 10:04:29 PST 2007
textshell-I1QKlO at neutronstar.dyndns.org wrote:
> On Fri, Nov 09, 2007 at 04:17:05PM +0200, Norman Rasmussen wrote:
>> On Nov 9, 2007 3:59 PM, Kevin Smith <kevin at kismith.co.uk> wrote:
>>> I may have misunderstood what you wanted. I thought you meant handling
>>> of xmpp: links within Psi, whereas now I guess you meant using Psi as
>>> the default handler for system xmpp: links. The latter is Textshell's
>>> baby in the IPC stuff. If you're interested in the former, it
>>> shouldn't be too hard.
>> Mmm, personally if getting xmpp links to work correctly with-in Psi is
>> easy, then I think we should go for that.
> That's mainly the missing part of the current code. And it's not quite that
> easy because we need to do it in an secure and unobstrusiv way.
> And i didn't see any xmpp / im uris send via xhtml-im or normal chat
> messages yet, so i think it's not really higher priority than gettig the
> ipc and this work.
In general I think that xmpp: URIs will be found on web pages. So for
instance you might find links like this:
<a href='xmpp:jdev at conference.jabber.org?join'>jdev chatroom</a>
It would be good for the browser to pass that URI along to Psi and for
Psi to do the right thing (in this case, prompt the user to join the
I don't think that IM users will send these URIs very often. We have
better ways to handle such use cases natively over Jabber (chatroom
invitations, roster item exchanges, and the like).
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 7338 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.affinix.com/pipermail/psi-devel-affinix.com/attachments/20071109/b434eaf1/attachment.bin
More information about the Psi-Devel