8 Jun
2026
8 Jun
'26
6:02 p.m.
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.
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?
I'm also concerned about formatting them as
valid JIDs since this may get
confusing on the live network.
That's why a `.internal` TLD was used for, but as pointed out by other in this
thread, it's not the best choice. Probably `.alt` would be a better fit, as
it's a non-DNS namespace.