Difference between revisions of "XEP-Remarks/XEP-xxxx: Message Reactions"
Jump to navigation
Jump to search
(→Cons) |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{remarks}} | |||
== XEP-xxxx: Message Reactions == | == XEP-xxxx: Message Reactions == | ||
| Line 15: | Line 16: | ||
* Legacy Client unusable because of reaction spam in MUCs, real messages with content are buried under reactions | * Legacy Client unusable because of reaction spam in MUCs, real messages with content are buried under reactions | ||
* People might refrain from using reactions, as they notice how they spam others legacy client, which could effectively harm adoption of the feature | |||
Latest revision as of 20:47, 17 April 2020
|
This is a page for information about XEP-Remarks/XEP-xxxx: Message Reactions, including errata, comments, questions, and implementation experience. |
XEP-xxxx: Message Reactions
Fallback Body
Summary of the advantages (pros) and disadvantages of adding a fallback body to the reaction.
Pros
- Users of legacy clients still see the reaction, because to them the message will appear as "standard" message.
- the legacy body causes the message to become "important" (in the sense of Carbons and MAM) without a hint (this is also a con).
Cons
- Legacy Client unusable because of reaction spam in MUCs, real messages with content are buried under reactions
- People might refrain from using reactions, as they notice how they spam others legacy client, which could effectively harm adoption of the feature