Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I found out how to link directly to a chat room on a Jabber conference server -- it took a bit of digging, and I wound up actually looking at the spec before I was sure I was doing it right. I confirmed here, so I'm pretty sure I've got it.

The results, though, are puzzling. If I click a link of the style xmpp:dude@example.com I get a new chat session with user "dude" at example.com, as expected. If I tack on a nonsense query (xmpp:dude@example.com?foobar), it's ignored, which is what the spec says should happen. However, if I use xmpp:room@conference.example.com?join, as in the link above, nothing happens.

I dug a little deeper, and found out that on my (Linux) system, xmpp URIs are handled via purple-url-handler, so I dropped to a terminal and ran it manually. The result was that any xmpp URI ran fine except one that includes a ?join query. The ?join query results in a dbus crash, pointing specifically to line 2356 of dbus-message.c -- a little Googling suggests this probably is dbus's less-than-elegant way of telling me that somebody is using dbus incorrectly.

Am I crafting my link correctly? Is this an OS or maybe application issue? Does this work on other platforms / browsers / etc? More importantly, is there any easy way to fix it?

share|improve this question
add comment

1 Answer

up vote 2 down vote accepted

The URI scheme used by XMPP is defined in XEP-0147 and extended for ?join in XEP-0045, point 15.7.2. In this form it is handled f.e. by psi and gajim -- so this standard is already being implemented by some XMPP clients.

I guess that if your software crashes in such a simple scenario, your software is buggy. You should report that to your distribution maintainers.

share|improve this answer
    
Now I just have to hunt down the bugtracker / maintainer for "purple-url-handler" and... wait? –  Coderer Apr 22 '10 at 22:22
    
@Coderer, Welcome in the open source world. That seems to be a standard route. If you want to fix it by yourself, you could try also checking packages from unstable/next release of your distribution. –  liori Apr 23 '10 at 11:56
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.