diff options
| author | Maxime “pep” Buquet <pep@bouah.net> | 2019-03-23 17:04:47 +0000 |
|---|---|---|
| committer | Maxime “pep” Buquet <pep@bouah.net> | 2019-03-23 17:06:07 +0000 |
| commit | 2dda6b80d46e2d07175348777db69f58b7735ac3 (patch) | |
| tree | 735e55dded7f52d6dccb7fd418b843cbe0ebaee5 /examples/user_location.py | |
| parent | 5629e44710cb1b75fdd8d71ad7c8f8dc94a81304 (diff) | |
| download | slixmpp-2dda6b80d46e2d07175348777db69f58b7735ac3.tar.gz slixmpp-2dda6b80d46e2d07175348777db69f58b7735ac3.tar.bz2 slixmpp-2dda6b80d46e2d07175348777db69f58b7735ac3.tar.xz slixmpp-2dda6b80d46e2d07175348777db69f58b7735ac3.zip | |
Partially fix poezio/poezio#3452. Prevent `groupchat_subject` from triggered sent when body or thread are in the message.
0045 says:
> The subject is changed by sending a message of type "groupchat" to the
> <room@service>, where the <message/> MUST contain a <subject/> element that
> specifies the new subject but MUST NOT contain a <body/> element (or a
> <thread/> element). In accordance with the core definition of XMPP, other child
> elements are allowed (although the entity that receives them might ignore
> them).
>
> Note: A message with a <subject/> and a <body/> or a <subject/> and a <thread/>
> is a legitimate message, but it SHALL NOT be interpreted as a subject change.
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
Diffstat (limited to 'examples/user_location.py')
0 files changed, 0 insertions, 0 deletions