XMPP Spaces URIs

Timothée Jaussoin <[email protected]> Tue, 9 Jun 2026 14:15:30 +0200
Newsgroups gmane.network.jabber.standards-jig
Message-ID <[email protected]>
This is a multi-part message in MIME format.
--===============7096533394902190862==
Content-Type: multipart/alternative;
 boundary="------------OSUbr6B6QRZRz9MEzrREi9tW"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------OSUbr6B6QRZRz9MEzrREi9tW
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Hi!

XMPP Spaces are now described in https://xmpp.org/extensions/xep-0503.htm=
l .

A XMPP Space is a Pubsub node that contains bookmarks pointing to MUCs.

We would like to have a proper Space URI that allow users to invite=20
easily others to their Spaces. This will be added as a section to XEP 050=
3.

So far a Pubsub node is described in=20
https://xmpp.org/extensions/xep-0060.html#impl-uri

I'd like to have something short and transparent so I'm proposing=20
something like this:

Proposal 1: xmpp:spaces.server.tld?;node=3Dx56ae32&space

I'm wondering if something shorter like this is possible ? (where the=20
client is resolving the "space" parameter as the Pubsub node)

Proposal 2: xmpp:spaces.server.tld?;space=3Dx56ae32

The goals are

  * to prevent non "space-ready" XMPP clients to open it as a Pubsub
    node by mistake
  * have something=C2=A0 short and easily shareable (Discord is having
    something like this https://discord.gg/AP5HFj7w)

If one of the proposals is okay for you I'll propose a PR on 0503 and=20
make the changes in Movim (I'm sure nicoco will be able to do it in=20
Slidge, the other 0503 implementation).

Because this is having effect on the XMPP uris format I'm wondering if=20
there's some kind of rules or specific requests to follow ?

Regards,

edhelas

--------------OSUbr6B6QRZRz9MEzrREi9tW
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html>
<html>
  <head>

    <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF=
-8">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    <p>Hi!</p>
    <p>XMPP Spaces are now described in
      <a class=3D"moz-txt-link-freetext" href=3D"https://xmpp.org/extensi=
ons/xep-0503.html">https://xmpp.org/extensions/xep-0503.html</a> .</p>
    <p>A XMPP Space is a Pubsub node that contains bookmarks pointing to
      MUCs.</p>
    <p>We would like to have a proper Space URI that allow users to
      invite easily others to their Spaces. This will be added as a
      section to XEP 0503.</p>
    <p>So far a Pubsub node is described in
      <a class=3D"moz-txt-link-freetext" href=3D"https://xmpp.org/extensi=
ons/xep-0060.html#impl-uri">https://xmpp.org/extensions/xep-0060.html#imp=
l-uri</a>=C2=A0</p>
    <p>I'd like to have something short and transparent so I'm proposing
      something like this:</p>
    <pre class=3D"prettyprint prettyprinted" style=3D""><span class=3D"pl=
n">Proposal 1: xmpp</span><span
    class=3D"pun">:spaces</span><span class=3D"pun">.server</span><span
    class=3D"pun">.tld</span><span class=3D"pun">?;</span><span class=3D"=
pln">node</span><span
    class=3D"pun">=3Dx56ae32&amp;space</span></pre>
    <p>I'm wondering if something shorter like this is possible ? (where
      the client is resolving the "space" parameter as the Pubsub node)</=
p>
    <pre class=3D"prettyprint prettyprinted" style=3D""><span class=3D"pl=
n">Proposal 2: xmpp</span><span
    class=3D"pun">:spaces</span><span class=3D"pun">.server</span><span
    class=3D"pun">.tld</span><span class=3D"pun">?;space</span><span
    class=3D"pun">=3Dx56ae32</span></pre>
    <p>The goals are</p>
    <ul>
      <li>to prevent non "space-ready" XMPP clients to open it as a
        Pubsub node by mistake</li>
      <li>have something=C2=A0 short and easily shareable (Discord is hav=
ing
        something like this <a class=3D"moz-txt-link-freetext" href=3D"ht=
tps://discord.gg/AP5HFj7w">https://discord.gg/AP5HFj7w</a>)</li>
    </ul>
    <p>If one of the proposals is okay for you I'll propose a PR on 0503
      and make the changes in Movim (I'm sure nicoco will be able to do
      it in Slidge, the other 0503 implementation).</p>
    <p>Because this is having effect on the XMPP uris format I'm
      wondering if there's some kind of rules or specific requests to
      follow ?</p>
    <p>Regards,</p>
    <p>edhelas</p>
  </body>
</html>

--------------OSUbr6B6QRZRz9MEzrREi9tW--

--===============7096533394902190862==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Standards mailing list -- [email protected]
To unsubscribe send an email to [email protected]

--===============7096533394902190862==--