On Mon, Mar 11, 2024 at 4:28 PM Jonas Schäfer <[email protected]> wrote:
> - Server assist should specify exactly when the modification of the <message/> > stanza happens. In particular, the interaction with MAM, Carbons and > potentially IM-NG should be spelled out (i.e.: is the <displayed > xmlns="..mds.."/> part of the archive and/or the carbons reflection?). You are right. I will prepare wording to be added after the XEP has been accepted. > - Server assist could be extended to make the server discard the message iff > the <displayed xmlns="..mds.."/> element is the only content in that message. > That way, server assist could also be used with non-contacts or similar > situations. I’m against this for the following reasons. * The server assist was added because of the feature request that the server parses <displayed xmlns="urn:xmpp:chat-markers:0"/>. However this puts unnecessary burden on the server because the server then has to look up the stanza-id from the message-id (which is used by Displayed Markers (Chat Markers)). So with that feature request / requirement in mind NOT allowing otherwise empty messages doesn’t take anything away. * It is not that hard to just do a regular PEP publish * Overloading the semantic of "sending a stanza to x" with "performing an operation on the account that involves x" is a slippery slope that I’m really trying to avoid. I don’t want to set precedence to for example to use "<message to="foo"><block/></message>" to block "foo". This has come up in the group chat before. Maybe I'll add something to the Design Considerations cheers Daniel _______________________________________________ Standards mailing list -- [email protected] To unsubscribe send an email to [email protected]
