Re: Proposed XMPP Extension: XMPP Decentralized ID (XID)

Goffi <[email protected]> Tue, 16 Jun 2026 12:58:27 +0200
Newsgroups gmane.network.jabber.standards-jig
Message-ID <[email protected]>
--===============5286975489836242490==
Content-Type: multipart/signed; boundary="nextPartP66QZWwGSBaRcVikZIkQDQ";
 micalg="pgp-sha512"; protocol="application/pgp-signature"

--nextPartP66QZWwGSBaRcVikZIkQDQ
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: Goffi <[email protected]>
To: XMPP Standards <[email protected]>
Date: Tue, 16 Jun 2026 12:58:27 +0200
Message-ID: <[email protected]>
In-Reply-To: <[email protected]>
MIME-Version: 1.0

Hi,

Sorry for the late answer.

Le mardi 9 juin 2026, 17:29:38 heure d=E2=80=99=C3=A9t=C3=A9 d=E2=80=99Euro=
pe centrale snit via=20
Standards a =C3=A9crit :
> Just a bit of bikeshedding (I'm not gigabrain enough to comment on much e=
lse=20
here), but I would really prefer the term XDID over XID.=20
> I frequently see XID used as a synonym of JID in various communities for=
=20
various reasons, and it'd be annoying to assign an unrelated but similar=20
meaning to the term at the same time.=20
> Furthermore, the term XID omits the one word that even differentiates it =
from=20
the existing XID/JIDs: decentralisation. Why pretend the most important par=
t=20
doesn't matter?
> This was brought up in the XSF MUC, for which the only response was that=
=20
XDID is "uglier" than XID. I don't think we should be prioritising aestheti=
c=20
over meaningful and unambiguous terminology.

The actual response was to ask if "XID" was used in any spec or if there ar=
e=20
proof that it's widely used (and this has not been answered as far as I can=
=20
tell). The official acronym for XMPP identifier is `JID` for historical rea=
sons.

XDID would actually be confusing with https://www.w3.org/TR/did-1.0/ that w=
as=20
mentioned elsewhere in this thread.

"Ugly" is not prioritizing aesthetic: if humans have to share this ID, a us=
er-
friendly name is better.

However, I'm not fully opposed to change the name, but I find "XID" quite g=
ood,=20
and I don't recall seeing it used instead of "JID" (I sometime see the larg=
er=20
form "XMPP ID").

We can see during experimental phase if it is really confusing and causing=
=20
troubles, in which case another names will be explored.

Best,
Goffi
--nextPartP66QZWwGSBaRcVikZIkQDQ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEsNZvWyEnjW9SVudbKqmcu6xuKwwFAmoxLFMACgkQKqmcu6xu
Kwx6HAf9FmB887gCi3rldupwrmdhUPPmsLGG7+ObeqdKId/ZVssRXNXfXgV7BDLT
Vd2jCEqNwPrfJXpYE5EYi/LMrI+cEDO9xfha95rTcE69VVTXtoC8ANuHdcUQipFV
r+66DR/UW7yimNutOl24YwszuHLrE5XWU+8CHEwjQNliYhiL+mw1MOQPnMWbjmeg
I9GQuFt8G99CSEjEQHLqLKvSMgPN3TAJ3By+z+g0lb8aq4p0qKVrbWoDSSrUU9J+
Tv/GjJmv2pnx+4gk/7b0p1xmS0sMgektruPQNe8YdaVUat1bEgqm+g8lb3NcZLRC
e8NJCytUmpYrRZgwptvzG6NTqc4UiA==
=lBWr
-----END PGP SIGNATURE-----

--nextPartP66QZWwGSBaRcVikZIkQDQ--




--===============5286975489836242490==
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]

--===============5286975489836242490==--