Copy

Task #4092

convert custom URI schemes to standard schemes from RFC 5122, etc.

Added by hans about 3 years ago. Updated about 3 years ago.

Status:ClosedStart date:11/19/2014
Priority:NormalDue date:
Assignee:hans% Done:

0%

Category:-
Target version:v14 - Armadillo's Agram
Component:

Description

RFC5122 defines a standard xmpp: URI system, and XEP-0147 defined standard actions that can be triggered using an RFC5122 URI. Apps like Adium implement these. Using them instead of the existing custom schemes would make things inter-operable.

xmpp.html Magnifier - a collection of xmpp: URLs for testing (1.89 KB) hans, 11/19/2014 04:45 pm

xmpp.html Magnifier - clickable test URLs (2.42 KB) hans, 11/20/2014 07:31 pm

Related issues

Related to ChatSecure:Android - Feature #2117: Add a URL prefix to the fingerprint QR code and add ChatS... Closed 10/17/2013

History

#1 Updated by hans about 3 years ago

It looks like imto://chatsecure/ is some kind of standard, but I didn't find a reference to clarify it. I did find a reference to the Skype URIs, which are very similar to the XMPP RFC5122 URIs:

skype:username?action

https://en.wikipedia.org/wiki/URI_scheme#skype:

#2 Updated by hans about 3 years ago

  • Subject changed from convert custom URI schemes (e.g. im:, imto:, etc) to standard schemes from RFC 5122 to convert custom URI schemes to standard schemes from RFC 5122, etc.

There is an RFC for the im: scheme:
https://tools.ietf.org/html/rfc3860

#3 Updated by hans about 3 years ago

It seems that iOS does not properly handle "opaque" URIs, i.e. non-hierarchical URIs that do not include an "authority". Or to put it most simply, a URI that does not have // after the :. I did a quick survey of apps on my Linux Mint machine:


 app               | xmpp: | xmpp:// | xmpp:///
--------------------------------------------------
ChatSecureAndroid     X        X          X     (including my most recent commits)
gajim                 X
jitsi                 X
pidgin                X                   X
Here are some test URLs:

#4 Updated by hans about 3 years ago

#5 Updated by hans about 3 years ago

FYI, RFC3860 describes the im: URL scheme.

#6 Updated by chrisballinger about 3 years ago

ChatSecure on iOS can handle xmpp: xmpp:// and xmpp:///

Adium can only handle xmpp: and xmpp:// but fails if you include the ?otr-fingerprint option unless you also include ?subscribe

#7 Updated by hans about 3 years ago

This is good news! Sounds like we should then advertise using the strict RFC5122 URL, i.e.:

  • xmpp:?subscribe;otr-fingerprint=98273491287349817243987124

#8 Updated by hans about 3 years ago

  • Status changed from New to Closed
  • Assignee set to hans
  • Target version set to v14 - Armadillo's Agram
implemented in:
  • commit:0c566ec0
  • commit:dd16cb3c
Copy

Also available in: Atom PDF