Hi,

I dont read anything in the XEP about Real JIDs.
The XEP allows to block MUC Jids perfectly fine like

user@domain/resource
ex. [email protected]/testuser

And if i block such a JID, i think the server will block all presence from
that.
Now i know there is no good way of blocking MUC participants, the best
thing you can do is a kind of "ignore" functionality with privacy lists.

But i think a note in the XEP is needed that MUC Jids should not be added,
and if, that its clear this is only a one way blocking, which can lead to
privacy leaks.

regards
philipp


2017-10-20 11:27 GMT+02:00 Jonas Wielicki <[email protected]>:

> On Sonntag, 15. Oktober 2017 21:00:28 CEST Philipp Hörist wrote:
> > Hi,
> >
> > There is no information in the XEP regarding behavior in MUC, so how does
> > this exactly work?
>
> In general, it can’t because the MUC server doesn’t necessarily have any
> way
> to interact with your "home" server, thus it can’t know your blocklist. As
> you
> already understood.
>
> > The MUC doesnt know that i blocked a user, so it sends my messages also
> to
> > the blocked users.
> >
> > Also my server blocks all presence from the blocked user, so i dont even
> > know he is in the channel.
>
> Your server is unlikely to know the real JID of the user in the MUC,
> unless it
> does some deep parsing of the MUC messages. Thus, you should be receiving
> presence from the blocked user in the MUC, since their JID is masked.
>
> Not sure if that helps. At least in a non-anonymous MUC, it helps to block
> received messages locally and/or notify the user that a blocked user is in
> the
> MUC, but message delivery can’t be prevented.
>
> kind regards,
> Jonas
> _______________________________________________
> Standards mailing list
> Info: https://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: [email protected]
> _______________________________________________
>
>
_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________

Reply via email to