jdev - 2020-07-14

Does any client implement `XEP-0421: Anonymous unique occupant identifiers for MUCs`?

what do you mean by "support"?

it’s a server-side feature, isn’t it?

a client may make beneficial use of this though

Make use of it, e.g. for LMC?

Right now you don't see it LMCed when you were not joined by that time.

hm, I should add the 10 lines necessary to support it in aioxmpp ;)

then jabbercat can do it

:)

ah, though, to do it securely I’d have to disco#info the MUC on join… a thing I still don’t do :/

aaaaalso the thing needs an addendum in the security considerations, neat

Or we could you know, move it inside of the <{muc}x/>.

Ah hmm, that’d work only for presences, not messages.

Nvm.

jonas’, which part of security considerations?

pep., the part where it doesn’t say that a client MUST NOT rely on occupant-id unless the feature was discovered on the MUC

Ah what you said

hmm wait

I thought it said something like that

it doesn’t

Not in security considerations

“The <occupant-id> element MUST be ignored if support for the feature is not announced via Service Discovery (XEP-0030) [4], as malicious clients might forge occupant identifiers if the room does not support them.”

needs mentioning in the SC then

Sure, might be good to move it / repeat it there

jupp