XSF Discussion - 2019-04-28


  1. lovetox

    https://xmpp.org/extensions/xep-0300.html#recommendations

  2. lovetox

    the table says Support for version 1 of the 'urn:xmpp:hashes' namespace implies the following:

  3. lovetox

    why is there a table for version 1 in a xep that is on version 2, but no table for version 2

  4. jonas’

    lovetox, probably because it should be version 2

  5. jonas’

    (on the table)

  6. lovetox

    ok thanks

  7. jonas’

    wait

  8. jonas’

    actually, that XEP should not have that table at all

  9. jonas’

    did I forget to open a PR

  10. flow

    was the xep not split yet?

  11. jonas’

    it is half-split

  12. jonas’

    I need to make the PR for completing the split and to fix up a few issues in the recommendations XEP

  13. jonas’

    I have a commit ready there, just need to re-read and PR it

  14. pdurbin

    High praise for XMPP in this latest episode: https://librelounge.org/episodes/episode-18-the-rise-and-fall-of-instant-messengers.html ... made me nostalgic. Hi, everyone. I'm new here.

  15. Guus

    Hi, welcome

  16. jonas’

    flow, relevant: https://github.com/xsf/xeps/pull/750

  17. jonas’

    welcome, pdurbin

  18. pdurbin

    Thanks. I work at Harvard and I used to help run an Openfire server for our department. It was great.

  19. Guus

    It still is. 😇

  20. yvo

    interesting pdurbin. So are you in the Sysadmin department of Havard?

  21. pdurbin

    No. I switched jobs within Harvard a couple times. This was in 2006 or so that we had an Openfire server (yes, I'm sure it's still great 🙂). For the last six years I've been a developer for an open source project called Dataverse. I log our IRC channel and it's pretty active during the week: http://irclog.iq.harvard.edu/dataverse/2019-04-26

  22. yvo

    ah it is about metadata, I'll pm you since it is off topic here

  23. pdurbin

    Sure, please feel free to pm me. :)

  24. yvo

    received pdurbin ?

  25. pdurbin

    Hmm. Nope. Let me try initiating.

  26. yvo

    ok strange. No prob, my jid is no secret. Could you write me directly: yvo@jabber.de

  27. yvo

    ok strange. No prob, my jid is no secret. Could you write me directly: yvo@jabber.de pdurbin

  28. jonas’

    I think this room filters PMs

  29. jonas’

    but I’m not sure

  30. jonas’

    it’s either this one or jdev@

  31. yvo

    filter PMs? what's the usecase for filtering PMs? jonas’ *wondering*

  32. pdurbin

    yvo: I just tried to send you a pm. I'm using an Android client called Conversations that was mentioned in that Libre Lounge episode above. I just installed it an hour ago so maybe it's misconfigured. :)

  33. jonas’

    Conversations hates MUC-PMs

  34. jonas’

    so that might be a different reason ;)

  35. pdurbin

    But a direct PM should work right? I sent one to Guus and we've been chatting back and forth without trouble.

  36. pdurbin

    He made a great post over at https://discourse.opensourcedesign.net/t/restoring-chat-functionality-collaboration-with-xmpp-community/901

  37. pep.

    pdurbin, now reading that threads, I see "I’ve gravitated toward chat systems like Gitter where the conversation is saved.", you know that this also happens on XMPP?

  38. pep.

    pdurbin, now reading that thread, I see "I’ve gravitated toward chat systems like Gitter where the conversation is saved.", you know that this also happens on XMPP?

  39. pdurbin

    Yes, but there is a difference between conversation being saved and conversation (including decision making) being available to read without login on a website. I think the latter is healthy for open source projects. :)

  40. pep.

    Both are possible

  41. MattJ

    pdurbin, http://logs.xmpp.org/xsf/2019-04-25#2019-04-25-3565fdd047495c23 for an example of an XSF board meeting logs, for example

  42. Guus

    pdurbin: as an aside, there's some mix-up of terms going on. What you sent me earlier was a one-on-one message, which is technically different from a private message in a chatroom. The main difference is addressing: your one-on-one to me was addressed directly to me, while a PM in a room is addressed to my nickname in the room.

  43. pdurbin

    Interesting. I didn't know the difference between a one-to-one message and a PM. Thanks!

  44. Guus

    I just sent you a PM.

  45. pep.

    Lots of people wish there was no difference tbh

  46. Guus

    I also sent you some one-on-one messages, for illustration purposes.

  47. moparisthebest

    Then don't use semi anonymous mucs and there is no difference

  48. pep.

    I strongly believe there is a need for some kind of anonymity, (even just a really small layer hiding quicksy users' jids, for example), but I don't know if full/semi-anon MUCs are the answer to that. In the meantime it's the only thing we have

  49. pdurbin

    moparisthebest: is this a PM?

  50. moparisthebest

    No, you sent that to the whole channel

  51. pdurbin

    Ok. What do you call what I just did? Calling it an "@mention" doesn't feel like the right term. There's no @ sign. :)

  52. MattJ

    It is called a mention or a highlight, depending on your background

  53. pdurbin

    That makes sense. Thanks, MattJ.

  54. pdurbin

    I see "Prosody" at the bottom of https://logs.xmpp.org . Is that the software creating public HTML versions of the logs? Are plain text versions created as well?

  55. Guus

    Prosody is an XMPP server implementation, like Openfire

  56. Guus

    Prosody has a plugin that generates those HTML logs.

  57. pdurbin

    Is it a core module?

  58. Guus

    Don't think so, but unsure. Zash or MattJ will be able to answer that.

  59. MattJ

    It's not a core module

  60. pdurbin

    Is it https://modules.prosody.im/mod_http_muc_log.html ?

  61. Wiktor

    pdurbin: xmpp:prosody@conference.prosody.im?join may be of interest to you :)

  62. pdurbin

    Wiktor: thanks! I just joined. To be clear, I don't care at this point what XMPP server is used. I'm more interested in the complete solution: public logs for multi user channels. Are there any other examples out there besides https://logs.xmpp.org ?

  63. jonas’

    not that I knew

  64. Wiktor

    You could ask if ejabberd has something similar. I think their room is xmpp:ejabberd@conference.process-one.net?join

  65. pdurbin

    Thanks. Joined. I'll ask after the current chatter dies down. :)

  66. pdurbin

    I'm getting the impression that my public log use case is unusual but I was glad to discover that this and a few other channels are logged. Makes sense for meetings especially.

  67. yvo

    I find it not so unusual?

  68. jonas’

    I don’t think it’s too unusual

  69. pdurbin

    Ok. Good. :)

  70. Wiktor

    Actually I find the other way also interesting. IIRC Prosody room is not logged and doesn't have MAM enabled. This may be good to foster "no important discussions on chats, use e.g. Email"

  71. pdurbin

    But people love chat, especially Slack.

  72. Zash

    I'm opposed to keeping logs after having seen people get stressed out by feeling like they have to read all of it.

  73. Wiktor

    Not to mention having all messages preserved for eternity :)

  74. Zash

    And becase if it's important it should be written down in the docs or somewhere, not some hard-to-search chat log.

  75. Wiktor

    I actually set 6 month data retention limit in Conversations, also for my family members, no one complained for years :)

  76. Zash

    Yeah, that too. Public records change peoples behavior.

  77. Wiktor

    Zash: write the reasoning somewhere... Sometimes it's good to link to something like this (I'm serious)

  78. pdurbin

    I like preservation. :)

  79. Wiktor

    I mean "why isn't Prosody room logged"

  80. Wiktor

    I'd retain it for a while, for people that left or disconnected, but not long.

  81. Zash

    The pre-MAM built-in MUC history is still there to provide some context of whatever discussion you might be entering into when you join.

  82. Wiktor

    Ah right.

  83. Zash

    Wiktor: Writing down the reasons would be good, indeed.

  84. Zash

    Writing down all the important things that shouldn't be stored in chat logs would also be good, but it turns out that such things don't magically transcribe themselves into the proper place just because you don't keep persistent logs.

  85. Wiktor

    Zash: yes it doesn't but if you didn't write it down explicitly maybe it wasn't important? :)

  86. pep.

    I challenge this statement, I really doubt that applies to everything out there :P

  87. Zash

    What is and what should be aren't always the same.

  88. pep.

    I agree with Zash's last sentence

  89. pep.

    (well the one before that, now)

  90. Wiktor

    pep.: if it applied to anything I'd attach a formal proof ;) . It's more like a rule of thumb. Compare with how brain remembers, repeated exposure makes it easier to recall. One time events are usually ignored. :)

  91. mr.fister

    » One time events are usually ignored. not if they were very weird, unexpected or bizarre

  92. pdurbin

    I definitely agree that chat logs are no substitute for proper documentation and meeting minutes and all that. I write a ton of documentation for our project. :)

  93. yvo

    it is called "one shot learning" in psychology, a mysterious feature of humans brain.

  94. Zash

    Lots of emotions being involved seems to help. Evolutionary, it makes sense to make you remember that time when you got really scared so you can avoid whatever that was in the future.

  95. Wiktor

    Indeed. So you don't need chat logs for emotionally charged discussions too! Seems like a good optimization :)

  96. pdurbin

    I've heard the same thing, that memories are stronger if there's a strong emotion experienced. Not just fear.

  97. yvo

    Flamewars need not to be logged :D.

  98. MattJ

    Yeah, I remember the important part of all of them: I was right

  99. yvo

    Yes, I am right. And you are right MattJ since you share my opinion.

  100. pdurbin

    Heh.

  101. yvo

    Lets publish a new encryption: whenever people flamewar lets compress it to "I was right". Very small file.

  102. yvo

    All chats about demos can be compressed too.

  103. yvo

    "I am against it."

  104. pdurbin

    My philosophy is to err on the side of logging and link to the interesting parts. Quote the interesting parts. Learn. Grow.

  105. yvo

    Could be a constant in the db. RIGHT and AGAINST

  106. yvo

    err? pdurbin? I dont get your abbreviation.

  107. pdurbin

    Oh sorry: https://www.merriam-webster.com/dictionary/err%20on%20the%20side%20of

  108. pdurbin

    Lean toward.

  109. pdurbin

    Favor.

  110. pdurbin

    Sometimes I say "open source by default".

  111. pdurbin

    The reason I'm here is that this channel is logged. :)

  112. yvo

    ah thx, never met that idiom.

  113. pdurbin

    Sure.

  114. pdurbin

    I have a list of haunts that are all Gitter and logged IRC channels: http://wiki.greptilian.com/haunts . Maybe I'll add this one. It's nice here. :)

  115. pdurbin

    I forgot how nice XMPP is.

  116. yvo

    Take your chance and become also a member of the XSF ;) next chance is soon: in May,

  117. yvo

    Take your chance and become also a member of the XSF ;) next chance is soon: in May, pdurbin.

  118. flow

    Is there an easy to type character that is not valid in any JID part?

  119. pdurbin

    How much does it cost to be a member?

  120. Zash

    pdurbin: In the XSF? A few minutes of your time to type up a membership application.

  121. Zash

    flow: https://tools.ietf.org/html/rfc7622#section-3.3.1 (except @ and /) are probably the easest to type, remember and find

  122. Zash

    Hm wait are those legal in resources?

  123. pdurbin

    I can probably afford a few minutes. Thanks. :)

  124. MattJ

    Zash, @ and / are legal

  125. Zash

    MattJ: I know that, I though the other ones were't legal in resources. Turns out they are. Meh.