XMPP Council - 2023-01-26


  1. emus has left

  2. Ingolf has left

  3. Ingolf has joined

  4. neox has left

  5. moparisthebest has left

  6. moparisthebest has joined

  7. gooya has left

  8. Tobias has joined

  9. SouL has left

  10. Tobias has left

  11. Tobias has joined

  12. SouL has joined

  13. moparisthebest has left

  14. moparisthebest has joined

  15. SouL has left

  16. SouL has joined

  17. emus has joined

  18. MSavoritias (fae,ve) has joined

  19. SouL has left

  20. SouL has joined

  21. Kev has joined

  22. emus has left

  23. emus has joined

  24. neox has joined

  25. Ingolf has left

  26. Ingolf has joined

  27. pep. has left

  28. pep. has joined

  29. vaulor has left

  30. vaulor has joined

  31. SouL has left

  32. SouL has joined

  33. gooya has joined

  34. pep.

    Melvo has a point re /me in CS.

  35. daniel isn’t a huge fan either

  36. larma

    agree it should probably be rather advanced client only

  37. pep.

    It shouldn't make it to CSs at all IMO

  38. daniel

    I’m actually not sure if slack or element support it?

  39. larma

    you could argue the same about avatars

  40. daniel

    but i'm inclined to get rid of it

  41. larma

    Slack does

  42. larma

    element too

  43. pep. is cruft straight from the past or our tech circles

  44. pep.

    fail.

  45. pep.

    /me

  46. larma

    Or precisely, Matrix does natively (on wire /me messages are different to non-/me messages)

  47. pep.

    "//me foo" sends /me in poezio..

  48. pep.

    larma, fwiw I think they should also be on XMPP

  49. pep.

    "/me " is yet another terrible body hack

  50. larma

    agree

  51. Kev

    Terrible, yes. It's a wonder that the network has been able to survive under the weight of it for so many years.

  52. pep.

    Kev, it really is! :)

  53. larma

    Kev, body hacks typically don't hurt except if you want to send something that a body hack would transform

  54. Kev

    It's inelegant, we might not design it this way these days, but it's not onerous in the grand scheme.

  55. Zash

    Did someone say '393

  56. pep.

    It's like saying philantropist billionaires are great, except when they actually get you to accept the fact that billionaires should be a thing. /me is a well-accepted body hack and it contributes to making it ok to do body hacks.

  57. pep.

    It's like saying philantropist billionaires are great, except that they actually get you to accept the fact that billionaires should be a thing. /me is a well-accepted body hack and it contributes to making it ok to do body hacks.

  58. Kev

    I thought that. The /me command and extreme wealth inequality are almost directly equivalent things.

  59. MSavoritias (fae,ve)

    whats the replacement?

  60. Kev

    Communism?

  61. MSavoritias (fae,ve)

    XD i meant /me

  62. MSavoritias (fae,ve)

    i didnt know it was such a hack

  63. pep.

    MSavoritias (fae,ve), not doing it, or doing something better, that is a specific tag in <message>

  64. daniel

    we would charge a $0.02 fee for every /me command send

  65. larma

    - Message sending "/me tests" `{ "type": "m.room.message", "content": { "msgtype": "m.text", "body": "/me tests" } }` - Message sent when typing "/me tests" in client supporting it in Matrix: `{ "type": "m.room.message", "content": { "msgtype": "m.emote", "body": "tests" } }`

  66. daniel

    a sort of tax if you will

  67. Zash

    and then that tax will go towards authoring a replacement XEP?

  68. Zash

    (and maybe the XSF Dinner)

  69. Kev

    Of all the problems that are there to be solved in XMPP - both future features and cleanup of existing inelegancies, I struggle to believe that '/me' is really worth our time. It feels like the sort of issue where although there's bigger decisions to be made, people will weigh in on this one because it's easier to grasp. Someone should come up with a term for such a thing...

  70. pep.

    Removing it from CSs should be no biggie though..

  71. pep.

    That doesn't mean clients should remove it as a feature

  72. Kev

    Except that it's a feature that client authors need to implement to not have their users get displayed weird messages.

  73. Kev

    This isn't some niche XMPP-only thing. It's common across IM ecosystems.

  74. pep.

    Because nerds use it

  75. daniel

    because slack and discord have it

  76. daniel

    apparentaly

  77. pep.

    Who uses that in slack and discord though

  78. larma

    pep., notice though, that non-nerd-platforms like Slack, Discord, etc. today use Markdown as rich-text input because nerds built it and made some small tutorial how to use it and now everyone des

  79. pep.

    and do we have to copy everything they do

  80. larma

    pep., notice though, that non-nerd-platforms like Slack, Discord, etc. today use Markdown as rich-text input because nerds built it and made some small tutorial how to use it and now everyone does

  81. daniel

    to some degree yes

  82. daniel

    and they copied us (and IRC)

  83. pep.

    daniel, you're saying we should have removed that years ago? :P

  84. pep.

    And now we're stuck with it because devs are nerds

  85. Zash

    Except in IRC it's a client to client command, not a literal "/me blah" message.

  86. pep.

    We haven't even manage to copy IRC properly :D

  87. Zash

    Type `<action>verbs</action><body>/me verbs</body>` into a XEP and send it in!

  88. MSavoritias (fae,ve)

    if its a hack i agree on removing it

  89. MSavoritias (fae,ve)

    its not like profanity is gonna look at CS and be like we have to remove it to be "compliant"

  90. Kev

    MUC is full of hacks. Should we remove '45 on that basis?

  91. Zash

    Not until there are server-side MUC-to-MIX translation layers everywhere!

  92. pep.

    Well it's an not a hack anymore it's an institution now. Look any talk about even just removing it from CSs is frowned upon :P

  93. MSavoritias (fae,ve)

    Remove it for MIX i say

  94. larma

    Zash, and even then, it should still be in there because devs can just choose one or the other to be fully compliant with groupchats

  95. pep.

    MSavoritias (fae,ve), it's not a groupchat thing

  96. MSavoritias (fae,ve)

    then only kaidan is compliant :P

  97. pep.

    https://xmpp.org/extensions/xep-0245.html

  98. MattJ

    Are we against "/me", or are we saying XMPP shouldn't support/require clients to be able to display action messages?

  99. pep.

    MattJ, the latter for me

  100. MattJ

    Even though many other messengers do support those things, and people will say it's the one thing XMPP needs to be successful

  101. MattJ

    Feels like a step backwards :)

  102. Zash

    People *did* say that!

  103. pep.

    People say everything you want to hear

  104. Zash

    MattJ, remember when the old chat.prosody.im didn't support /me ?

  105. MattJ

    Yup

  106. larma

    I'd say it's actually an advanced feature, not a critical important feature every client has to support, because the fallback body is "good enough"

  107. Zash

    I was using it in a different project and someone complained about the lack of /me

  108. larma

    I'd say it's actually an advanced feature, not a critical important feature every client has to support, because the "fallback body" is "good enough"

  109. MattJ

    I'd definitely prefer an explicit <action> or something, and a better fallback body

  110. Zash

    MattJ, write the xep!

  111. MSavoritias (fae,ve)

    i wouldnt mind action messages but i see them in the same niche as moods and user tunes personally

  112. daniel

    > and people will say it's the one thing XMPP needs to be successful that’s 100% a thing that would happen

  113. MSavoritias (fae,ve)

    yeah actions xep would be interesting

  114. Kev

    I can't even find when I added /me to Psi, because it predates the switch to Git in early 2007.

  115. MattJ

    If we have a decent fallback body I don't care much about whether it's in advanced or CS at all

  116. Zash

    inb4 months of arguing whether it should be merged into https://xmpp.org/extensions/xep-0439.html or its own XEP

  117. MattJ

    But showing unrendered "/me" to users is a step backwards

  118. larma

    When writing the XEP, also remember to add the <non-action /> element to signal that the message starting with "/me" in the body is not meant to be an action.

  119. MattJ

    Ha

  120. Zash

    or RECOMMENED that clients insert a zero-width non-breaking space before /me

  121. larma

    <message><body>/me foo</body><action /><fallback for="action" from="0" to="3" /></message> is rendered "* name foo" <message><body>/me foo</body><non-action /></message> is rendered "/me foo" <message><body>/me foo</body></message> is rendered "* name foo" for legacy compat

  122. larma

    <message><body>/me foo</body><action type="me" /><fallback for="action" from="0" to="3" /></message> is rendered "* name foo" <message><body>/me foo</body><non-action /></message> is rendered "/me foo" <message><body>/me foo</body></message> is rendered "* name foo" for legacy compat

  123. Zash

    <message><body>\/me foo</body><xhtml2><body><p>/me foo</////>

  124. Zash

    /me tests

  125. Zash

    <action>goes off to write mod_legacy_me, then sit on it for 5 years</action>

  126. me9 has joined

  127. vaulor has left

  128. vaulor has joined

  129. Wojtek has joined

  130. Link Mauve has left

  131. paul has left

  132. Kev has left

  133. Kev has joined

  134. paul has joined

  135. Link Mauve has joined

  136. Wojtek has left

  137. Tobias has left

  138. Tobias has joined

  139. Tobias has left

  140. Tobias has joined

  141. Tobias has left

  142. Tobias has joined

  143. Tobias has left

  144. Tobias has joined

  145. stpeter has joined

  146. Tobias has left

  147. Tobias has joined

  148. Tobias has left

  149. Tobias has joined

  150. Tobias has left

  151. Tobias has joined

  152. Wojtek has joined

  153. gooya has left

  154. gooya has joined

  155. SouL has left

  156. Wojtek has left

  157. stpeter has left

  158. SouL has joined

  159. vaulor has left

  160. vaulor has joined

  161. stpeter has joined

  162. MSavoritias (fae,ve) has left

  163. stpeter has left

  164. me9 has left

  165. stpeter has joined

  166. Tobias has left

  167. stpeter has left

  168. vanitasvitae_ has left

  169. vanitasvitae_ has joined

  170. gooya has left

  171. gooya has joined

  172. Tobias has joined

  173. Kev has left

  174. Tobias has left

  175. daniel has left

  176. daniel has joined