19 Jan
2025
19 Jan
'25
5:55 a.m.
Hello,
Just to clarify, this is absolutely not a blocker for me (and I don't
have any sort of veto rights as you know ^^). But a nice to have.
Indeed, for MUCs. I shouldn't have mentioned it, I believe it's part of
another (broader) discussion. :)
-- nicoco
* Change to "/me retracted a message"
(instead of "this")
* Make the <body> empty instead
I think both are OK, I agree that "this" is problematic. I am slightly
concerned that an empty body won't work in some (all?) clients; I think
Cheogram uses a white space for this reason (singpolyma can you confirm?).
Given that the <retract> is used as a fallback,
shouldn't that be
indicated inside the fallback element?
I think you meant <replace>, which makes sense, but that's not allowed
by XEP-0428, which only allows <body> and <subject> as sub-elements of
<fallback>. I don't think it's worth making XEP-0428 more complex. Maybe
XEP-0424 could mention that if a client supports <retract>, other
sibling elements of a <message> should be dismissed? I am not confident
about this being a good idea (?).
I will be
slightly more annoying to implement if we switch to using
stanza-id instead of origin-id (since XEP-0308 requires message@id
which is == origin-id most of the time).
You mean for MUCs? For 1:1 the message id is used.