9 Jun
2026
9 Jun
'26
12:07 a.m.
Hi Singpolyma,
Le mardi 9 juin 2026, 03:02:22 heure d’été d’Europe centrale Stephen Paul
Weber a écrit :
I'll be working on that (serverless) soon.
However, I already have a XID implementation (with possibility to sign/verify
any kind of data).
That's actually a feature, it makes it usable everywhere where a JID is
usable, and compatible with xmpp: scheme.
See the example I'm mentioning in business rules: using a XID for
"publisher"
attribute in pubsub make it portable Right now, if you change server, you must
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 nowhere,
so the developer would quickly find the problem.
Best,
Goffi
>I need that for serverless, but it has several
other use cases as explained
in
the protoXEP,
and we don't have equivalent AFAIK for that (OX would be the
closest, but more complicate and difficult to use in those case).
I think it's not going to make much sense to me until I see it in the
context it's actually going to be used in... even if being a separate XEP
still makes sense. >It's inspired from Peer ID from libP2P, and
relatively simple to implement
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 end
up in a part of the code that expects it to be a JID... I'm not sure this is
what we would want if it's for other purposes?