Georg Lukas

I've tested the behavior by sending a message from Siskin to [email protected], which will automatically send an error response to the message, referencing the original message id. However, Siskin didn't...

I haven't yet seen message errors with a body element in the wild, and I'm pretty sure that would be considered as non-standard by most. Have a look at [RFC6120...

Yes, I am aware of the sad situation with message errors that do not contain a body. I've actually just [started a thread](https://mail.jabber.org/pipermail/standards/2019-August/036332.html) about this problem, in the hope to...

P.S: the `createroom` plugin has a `subdomain` option that is also based on the connection domain, making it impossible to use chat.yax.im from anon.yax.im.

@linkmauve suggested: > Should we have a new CSS class for examples with a red background, to be certain no one will blindly copy this example?

This was [discussed and rejected by Council on 2019-11-13](https://mail.jabber.org/pipermail/standards/2019-November/036630.html). I'm preparing a second attempt with less strict wording and more rationale.

Just a small note that this all-in-one commit will make #434 fail, at least because the other PR also removes the element. P.S: the title of this PR is sufficiently...

Looks like back in 2017, council [informally decided](https://logs.xmpp.org/council/2017-03-08#2017-03-08-70a456d72a6dc76f) that the clarification doesn't need a namespace bump.

Please let me clarify. The **clarification** about the state of Carbons post-resumption does not need a bump. The replacement of `private` with `no-copy` does need a bump indeed, but it...

Yeah, using a different variable for the hero image would solve the problem for me. It would probably also make sense to remove the /images/ prefix while you are at...