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

--===============7041489865808299150==
Content-Type: multipart/signed; boundary="nextPartxHUEeLcPRQ2V4hNKrVsRAQ";
 micalg="pgp-sha512"; protocol="application/pgp-signature"

--nextPartxHUEeLcPRQ2V4hNKrVsRAQ
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, 09 Jun 2026 09:07:32 +0200
Message-ID: <[email protected]>
In-Reply-To: <[email protected]>
MIME-Version: 1.0

Hi Singpolyma,

Le mardi 9 juin 2026, 03:02:22 heure d=E2=80=99=C3=A9t=C3=A9 d=E2=80=99Euro=
pe centrale Stephen Paul=20
Weber a =C3=A9crit :
> >I need that for serverless, but it has several other use cases as explai=
ned=20
in
> >the protoXEP, and we don't have equivalent AFAIK for that (OX would be t=
he
> >closest, but more complicate and difficult to use in those case).
>=20
> I think it's not going to make much sense to me until I see it in the=20
> context it's actually going to be used in... even if being a separate XEP=
=20
> still makes sense.

I'll be working on that (serverless) soon.

However, I already have a XID implementation (with possibility to sign/veri=
fy=20
any kind of data).

> >It's inspired from Peer ID from libP2P, and relatively simple to impleme=
nt=20
and
> >use.
> >
> >> I'm also concerned about formatting them as valid JIDs since this may =
get
> >> confusing on the live network
> [SNIP]
> But even so it still looks like a JID and can parse as a JID and could en=
d=20
> up in a part of the code that expects it to be a JID... I'm not sure this=
 is=20
> what we would want if it's for other purposes?

That's actually a feature, it makes it usable everywhere where a JID is=20
usable, and compatible with xmpp: scheme.

See the example I'm mentioning in business rules: using a XID for "publishe=
r"=20
attribute in pubsub make it portable Right now, if you change server, you m=
ust=20
change every single item due to that (I've already been hit by that).

On the live network, even if it where confused, that would resolve to nowhe=
re,=20
so the developer would quickly find the problem.


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

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

iQEzBAABCgAdFiEEsNZvWyEnjW9SVudbKqmcu6xuKwwFAmonu7QACgkQKqmcu6xu
KwykowgAqnIfZ0snO3Ix/AideQrqk2NlAzNtEZMkKNXk12a34bEp3Qrs7Qhihqc7
RzUbJtzPKrbtF1KT9uucVTRqXTJxZN4aBiXKhojWKUMF5ug3/bkFYM2iF5OHSluQ
jPN2aD8vLafKmGwWOegE+UBvdR0yHtyd8vvAQpkjZpohhUHGX6KhbNCmmvKKfD4f
gyJ8wXKfR/9MsKk/Lt7n8uRXoAKqfRaFely0s1zKJan7VtvKWMxCThc0Nl9HYSJK
7lVHnjS1s9N2My4NdYrDHLyJ/V3q2mkIIp3aA5X2W5bJLonP0GPPGfDv7EK/9rHt
OqrH8oiEek1eoZbOEkujVkBPOXXEsw==
=10tz
-----END PGP SIGNATURE-----

--nextPartxHUEeLcPRQ2V4hNKrVsRAQ--




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

--===============7041489865808299150==--