XSF Discussion - 2019-03-08

  1. moparisthebest

    Wiktor, anyone else interested, code is up https://github.com/moparisthebest/jDnsProxy/blob/dox/dox.md

  2. moparisthebest

    also I have it running at dns@moparisthebest.com/listener if anyone wants to query some DNS over XMPP

  3. Link Mauve

    “20:04:36 flow> I never understood why we use numbers when humans are much better with letters”, Western* humans, just ask a random Chinese person to remember letters instead of numbers and you’ll have a bad time.

  4. Ge0rG

    Link Mauve: not even if those letters are abbreviations of the subject matter name?

  5. Link Mauve

    AIUI, even then.

  6. flow

    Link Mauve, TIL. But is that an argument that we shouldn't use short names instead of numbers?

  7. Zash

    But, we do have short names

  8. flow

    that nobody uses

  9. flow

    that makes the situation even more ironic, we have them, I hope they are supposed to be short and unique, and still we use additinally numbers

  10. Zash

    But IIRC they get assigned at Draft or something

  11. wurstsalat

    > wurstsalat: it is already? pep., I meant on the xmpp.org frontpage, with a banner?

  12. pep.

    Ah you want the fancy banner :p

  13. pep.

    If you come up with the CSS for it I assume somebody will accept it

  14. wurstsalat

    pep., still no computer access for me until end of march, sorry. next time it will be a PR ;)

  15. jonas’

    flow, the numbers can be uniquely searched for, the short names may be so short that they occur in other words

  16. jonas’

    so using the numbers is much better for searchability

  17. jonas’

    at least that’s my rationale for using them in the ML subject and in rooms

  18. flow

    jonas’, XEP-SM?

  19. jonas’

    then we can never have XEP-SMART

  20. flow


  21. jonas’

    and what about avatars

  22. jonas’

    or bookmarks

  23. flow

    I immeditaly will know what XEP-FMUC is about, can you tell me the FMUC number from the top of your head?

  24. jonas’


  25. jonas’

    no, since I never cared about FMUC

  26. flow

    jonas’, right, but it doesn't make the situation worser

  27. jonas’

    the others I use I typically know, but I’m a number person

  28. flow

    also XEP-CAPS, and XEP-CAPS2 works pretty well for me

  29. jonas’

    then you can’t search for the old caps only

  30. jonas’

    you’ll always get both

  31. flow

    I think I could live with that

  32. jonas’

    not much more frustrating than having inaccurate search results and not being able to do anything about it

  33. flow

    it would be even better if we could tag threads and messages of the ML with unique xep tags for searching, but that is a different discussion

  34. jonas’

    I agree

  35. zinid

    > Western* humans, just ask a random Chinese person to remember letters instead of numbers and you’ll have a bad time who cares, there is already a ton of language discrimination 🙂 It's even more sharp when your native alphabet is not latin

  36. zinid

    this stringprep crap for example, not every language has a problem with character cases, and this shit is built into the protocol, permanently consuming resources at the servers

  37. Ge0rG


  38. Ge0rG

    The obvious solution is to use XEP Emoji Shortnames.

  39. Ge0rG

    I would like to propose a minor change to XEP<FacePalm><Male><Fitzpatrick-Modifier-3><ZeroWidthJoin><Regional-Indicator-Letter-Ф>

  40. Zash

    User was banned for this crime against sanity

  41. Guus


  42. dwd

    FWIW, I think we often do refer to protocols by name, and not number. We refer to the documents by number for precision, but there's only a handful that are routinely referred to by number (198, for example). Most of the time we talk about MUC, or vCards, or whatever.

  43. Ge0rG

    does "MUC" also include all the undocumented quirks that are not part of 0045? 😁

  44. MattJ

    Ge0rG, fancy documenting those?

  45. Zash

    What undocumented quirks are there? I can think of the vCard hack and MSN

  46. Ge0rG

    MattJ: MSN is the most prominent example. I think *somebody* started a wiki page on it, but then it was widely ignored by the people who know the most about their respective implementations.

  47. Zash

    Was that among the losses in the great server crash?

  48. Zash

    Was that page among the losses in the great server crash?

  49. Ge0rG

    Zash: no

  50. Ge0rG

    At least I don't think so

  51. Zash

    I think I started writing a sentence about the vcard hack but git ate it, probably when I looked at GC 1.0 removal

  52. Zash

    Hah, https://xmpp.org/extensions/xep-0089.html

  53. Zash

    What was the conclusion of looking at an old XEP each week?

  54. dwd

    Zash, Everyone thought that someone else should definitely do that?

  55. Zash

    Let's talk about XEP-XXXX: Tragedy of the Commons

  56. dwd

    Have we changed to roman numerals?

  57. pep.

    What do people think about this: https://lab.louiz.org/poezio/poezio/issues/3462 ? poezio bug: "LMC replaces the whole stanza"

  58. Guus

    pep. given that we're already in a situation where both approaches exist, an implementation note that warns to expect both methods might be good.

  59. Kev

    Replacing the whole stanza isn't what 308 asks you to do.

  60. Kev

    Just the payloads.

  61. Ge0rG

    that's getting rather philosophical.

  62. Zash

    Stanza of Theseus

  63. zinid

    client developers problems

  64. lovetox

    does poezio save stanzas to its local storage?

  65. Alex

    If you are a XSF member and have not voted yet in our current voting period then please do so. Memberbot is online and waiting to accept your votes ;-) Thank You

  66. MattJ

    Done, thanks :)

  67. Alex


  68. Ge0rG

    The deadline is 2019-03-12 19:00 UTC!

  69. Ge0rG

    Alex: thanks for running all this process 👍

  70. jonas’

    done, thanks!

  71. Seve

    Alex, very appreciated :)

  72. Seve

    New applicants :O

  73. Syndace


  74. pep.

    lovetox, no it doesn't

  75. lovetox

    then how does it "replace" a stanza

  76. pep.

    What do you call local storage?

  77. lovetox

    are you saying it keeps the received stanzas in some cache?

  78. pep.

    yeah, there's a buffer of stanzas that get displayed or sth

  79. pep.

    (I don't exactly know the details yet)

  80. pep.

    LMC will go as many times as it's corrected in the logs in any case, I think

  81. pep.

    But not displayed

  82. pep.

    (but **poezio will not display all of them, unless you ask for it)

  83. lovetox

    yes, but you wrote it replaces a stanza, but now from what you tell it does sound like it does put every message into storage

  84. pep.

    By replacing the whole stanza we also lose the ability to see corrections _after_. You have to have that setting _before_ that happens

  85. lovetox

    so i dont see replacing going oon

  86. pep.

    lovetox, there's hot/cold storage :p

  87. Ge0rG

    what about warm storage?

  88. pep.

    lovetox, when I say "replace" in that issue, I mean that the original stanza is getting replaced by the correction, in the buffer that will get displayed

  89. pep.

    (I think that's how it works, Link Mauve/mathieui will know better)

  90. Ge0rG

    not the stanza but the displayed text

  91. pep.

    no, the stanza

  92. Ge0rG

    (I'm pretty sure that LMC doesn't apply in the xml tab)

  93. pep.

    Yeah that's a different tab..

  94. pep.

    But we keep the stanza, with the associated ids/attributes etc., and that's actually what's causing the issue here, because we don't know about the original ID anymore

  95. pep.

    So we expect other implementations to refer to the one-to-last id

  96. Ge0rG

    Oh, I should have read the issue first.

  97. pep.


  98. lovetox

    pep. but every impl refers to the last message

  99. lovetox

    not to the first

  100. lovetox

    if i remember correctly

  101. pep.

    lovetox, not every no

  102. pep.

    converse doesn't

  103. pep.

    And the XEP is not explicit about it

  104. lovetox

    then you have no base for action

  105. lovetox

    so why change anything

  106. pep.


  107. lovetox

    hm no i said anything :D

  108. pep.

    Ge0rG, I like your time machine

  109. pep.

    ah, anything.

  110. Ge0rG

    tl;dr: nobody cares.

  111. pep.

    lovetox, well, because some LMC messages won't appear as LMC

  112. pep.

    And it's still valid

  113. lovetox

    you mean you impl displaying both ways?

  114. Ge0rG

    pep.: tell converse that it's called LMC and not FMC for a reason.

  115. pep.

    Ge0rG, we could do that by being explicit in the XEP yes

  116. pep.

    Or we could fix poezio to support all cases

  117. Ge0rG

    lovetox: yaxim only stores _one_ message in the DB (yeah, I know, I know). So it can only follow a linear LMC trace and not a tree.

  118. lovetox

    Ge0rG, Gajim stores all messages but still corrects the last

  119. Ge0rG

    technically, it should suffice to store two IDs, the _first_ ID and the _last_ ID for correction purposes.

  120. Ge0rG

    but then you need to index on both.

  121. pep.

    lovetox, yeah but at least you know the id converse is referring to. poezio doesn't

  122. lovetox

    i know the id but i still dont show the correction

  123. pep.

    heh, why?

  124. lovetox

    because i only allow the last message to be corrected

  125. Ge0rG

    pep.: I suggest you write a PR outlining that always the lastest message is to be referenced.

  126. pep.


  127. lovetox

    its called last message correction :D

  128. pep.

    lovetox, It's not called "last <message> correction" though

  129. lovetox

    i dont see the difference

  130. lovetox

    ah i get it

  131. lovetox

    you mean the user decides what counts as a message

  132. Zash

    XEP-XXXX: Message Correction Like Last Message Correction, but any recent message, within reason.

  133. Zash

    There I fixed it

  134. Ge0rG

    lovetox: I also have a time machine deployment for you: https://mail.jabber.org/pipermail/standards/2018-June/035143.html ;)

  135. pep.

    Ge0rG, I want access to your time machine

  136. lovetox

    either way this convers stuff is a good clue

  137. Zash

    <feature var="any-message-correction"/>

  138. lovetox

    because i have a bug report with not working LMC

  139. lovetox

    and now i think i know why

  140. Ge0rG

    pep.: it's called mutt <esc>/~S

  141. pep.


  142. Ge0rG

    lovetox: to quote from my past self: > I think there is a compelling reason to allow correcting more than just the last message - imagine typing multiple lines in a row, and only then reading what you sent, to realize a typo / incorrectness.

  143. lovetox

    im not against it within reason

  144. pep.

    Mattermost allows Any of My Messages Correction, unless you're an admin and then it's YMC

  145. lovetox

    Any makes not much sense to me, we are chatting here, this is not a document

  146. pep.

    Tell that to users with strong OCDs

  147. lovetox

    also its too much impl work

  148. Ge0rG

    lovetox: yaxim defines "within reason" as "the last 10 stored messages from that user"

  149. lovetox

    because when people can alter your history next thing your users want it to be made aware of it

  150. pep.

    lovetox, I agree

  151. Ge0rG

    as corrections are overwriting the original message, you can do an unlimited number of corrections of the same msg.

  152. MattJ implemented an animated progress bar in a bot already ;)

  153. pep.

    or as /marquee

  154. Ge0rG

    MattJ: showcase!

  155. MattJ

    Here? In this MUC?? ;)

  156. Zash

    In this part of XMPP?

  157. Ge0rG

    MattJ: dunno. Record a screencap maybe?

  158. MattJ

    Alas, it's a private project, and I don't intend to make this public because someone worse than me will use it somewhere

  159. Ge0rG imagines poezio /upload sending the upload progress of large files

  160. Zash

    Ge0rG: Don't give them ideas!

  161. Ge0rG

    [=====> ] 23.42KB/s ETA: tomorrow

  162. Zash

    Not when /marquee is a thing already

  163. Ge0rG

    is there a way to determine the width of the recipient's terminal over XMPP?

  164. Zash

    Put it in disco#info

  165. pep.


  166. Zash

    <winch columns="80" lines="24"/>

  167. pep.

    Ge0rG, do you send something different for each participant?

  168. pep.

    Or is that a server thing?

  169. Ge0rG

    pep.: yes!

  170. pep.

    <width columns="273" lines="74"/>

  171. Zash


  172. Zash

    in PEP

  173. Ge0rG


  174. Ge0rG

    I did it.

  175. Ge0rG

    Now let's make 2D animated art.

  176. dwd

    I don't know if I'm impressed, or disappointed.

  177. Ge0rG

    can't you be both, along different aspects of it?

  178. MattJ

    Star Wars over XMPP

  179. Ge0rG

    (now somebody must make the stupid name joke)

  180. MattJ

    Wow, it's still up

  181. Maranda

    Pft Star Wars