XSF Communications Team - 2020-07-13


  1. emus has left
  2. erszcz has joined
  3. erszcz has left
  4. erszcz has joined
  5. erszcz has left
  6. erszcz has joined
  7. Licaon_Kter has left
  8. Licaon_Kter has joined
  9. erszcz has left
  10. Licaon_Kter has left
  11. erszcz has joined
  12. erszcz has left
  13. erszcz has joined
  14. erszcz has left
  15. erszcz has joined
  16. erszcz has left
  17. erszcz has joined
  18. erszcz has left
  19. erszcz has joined
  20. erszcz has left
  21. erszcz has joined
  22. erszcz has left
  23. erszcz has joined
  24. erszcz has left
  25. erszcz has joined
  26. erszcz has left
  27. erszcz has joined
  28. erszcz has left
  29. erszcz has joined
  30. erszcz has left
  31. erszcz has joined
  32. erszcz has left
  33. erszcz has joined
  34. erszcz has left
  35. erszcz has joined
  36. erszcz has left
  37. erszcz has joined
  38. erszcz has left
  39. erszcz has joined
  40. erszcz has left
  41. erszcz has joined
  42. erszcz has left
  43. erszcz has joined
  44. erszcz has left
  45. SouL has joined
  46. emus has joined
  47. Nÿco has left
  48. Nÿco has joined
  49. erszcz has joined
  50. Licaon_Kter has joined
  51. debacle has joined
  52. wurstsalat has left
  53. wurstsalat has joined
  54. debacle has left
  55. SouL has left
  56. SouL has joined
  57. emus has left
  58. emus has joined
  59. debacle has joined
  60. wurstsalat has left
  61. wurstsalat has joined
  62. wurstsalat has left
  63. wurstsalat has joined
  64. la|r|ma has left
  65. la|r|ma has joined
  66. Wojtek has joined
  67. alacer has left
  68. alacer has joined
  69. ralphm has left
  70. intosi has left
  71. Nÿco has left
  72. Nÿco has joined
  73. debacle has left
  74. intosi has joined
  75. ralphm has joined
  76. SouL has left
  77. SouL has joined
  78. jcbrand has left
  79. emus peetah, wurstsalat: All merged! Thank you guys!
  80. raspbeguy has left
  81. debacle has joined
  82. erszcz has left
  83. peetah how about using the @xmpp@fosstodon.org or another dedicated account to explain XEPs as simply as possible ?
  84. pep. peetah, you'd pick a random XEP and try and explain it?
  85. pep. Or would you do that for every XEP that gets changed
  86. peetah it would need to be short, simple, user centric, explaining what problem it solves, what constraint it brings and when possible how it is better than other protocols
  87. pep. peetah, the issue with that is not all XEPs can be explained easily
  88. peetah I guess every XEP from 001 to the ned
  89. peetah that would be the challenge
  90. pep. They're more technical things in there, and there's lots of XEP that depend on others that are more technical :P
  91. peetah ok so we could decide here which one would be the most valuable and draft it here before sending on microblogging platform
  92. peetah ok so we could decide here which would be the most valuable and draft them here before sending on microblogging platform
  93. pep. You can probably summarize PubSub as "Publish Subscribe" and explain the concept, but then explaining why there's a change in there from "this" to "that" that changes the meaning of 90% of the thing (as an example) and also all dependant XEPs :x
  94. peetah the idea is to make users more aware of the modularity of their tool, and give them arguments to promote it
  95. pep. I don't think it's important to end users tbh :/
  96. pep. It's important to devs for sure
  97. peetah I'm not talking about explaining the changes, but what each of them are
  98. pep. I don't understand
  99. peetah people often complain about the number and complexity of XEPs, why this one is implemented in a server, this one in a client, how they impact them directly and why they should care when choosing their client or server
  100. peetah the idea is to make all this XEP environment easier to grab
  101. pep. "people"?
  102. pep. We're actually trying to figure out here what kind of people we're targetting :P
  103. peetah user writing comments on the various platform where the newsletter is published
  104. peetah that is why I was suggesting a separate microblogging account, so taht it is separated from the newsletter
  105. peetah that is why I was suggesting a different microblogging account, so that it is separated from the newsletter
  106. peetah if it becomes a reality , we would talk about it in the newsletter but it would live on its own
  107. pep. Right but are these users really a group of people that need to be exposed to XEPs
  108. peetah not all of them, bu some are willing to understand the modularity of XMPP to make informed choices
  109. peetah not all of them, but some are willing to understand the modularity of XMPP to make informed choices
  110. peetah and reading the full specifications of a XEP is not very tempting
  111. peetah the microblogging format could be the start of a discussion with those users around a XEP to catch what should be explained and what should be left to experts/developers
  112. peetah this whole discussion could then be summarized in the wiki
  113. peetah the result of this whole discussion could then be summarized in the wiki
  114. pep. Tbh I'd also like to have vulgarization material even for developers
  115. peetah it's 23h34, I'm just thinking out loud
  116. peetah it's 23h24, I'm just thinking out loud
  117. pep. Maybe that can help more technical non-technical users also :)
  118. Licaon_Kter Not a bad idea, but do start with those under 0423 ;)
  119. pep. Yeah sure, the order is not exactly the most important thing just now :)
  120. peetah no but it can have its importance if we think of the learning curve
  121. pep. I'll repeat though, for end-users -- like a big chunk of people on linuxfr -- I don't think this is something they need
  122. pep. They might be interested in what features they client have, not what a (doesn't have to be the only one) protocol that client is using can do
  123. pep. They might be interested in what features their client have, not what a (doesn't have to be the only one) protocol that client is using can do
  124. peetah I would need that :)
  125. emus peetah, I recently had similar ideas in mind. I like it basically. How this should be done can be discussed. But I basically like it
  126. pep. emus, a series of blog post or sth? :p
  127. emus Videos 😀
  128. emus I also still have my podcast idea in mind
  129. peetah again what I would like to be able to do on my own is to explain why XMPP is better than such and such other protocols/tools
  130. peetah and to do so, I need short and strong arguments, relying on a good knowledge of the XEPs
  131. pep. Tbh I don't think the strengh of XMPP is in any individual XEP
  132. pep. It's in the fact that XEPs are a thing
  133. pep. (That it's possible to extend the protocol)
  134. peetah can you do what X and Y is doing ? yes there's a XEP for that and it's doing it more efficiently !
  135. peetah but not implemented everywhere...
  136. pep. Because there are lots of XEPs that are actually useless, there are some that are even harmful, then there's those that have nice goals but the spec is sub-par, and there are those that most implementations are using that still have lots of things that needs fixing but won't be changed exactly because everybody is using them
  137. pep. Because there are lots of XEPs that are actually useless, there are some that are even harmful, then there's those that have nice goals but the spec is sub-par, and there are those that most implementations are using that still have lots of things that need fixing but won't be changed exactly because everybody is using them
  138. pep. peetah, yeah I think that's slightly misguided
  139. emus I like the basic approach he has. Maybe XEPs are not he best way to directly advertise XMPP. But maybe peetah can create a few example what he would like to advertise and we look what we can do with it. In general, it is good to make clear why XMPP is the best 🙂 😀
  140. Licaon_Kter Eg. PEP XEPs....it's OMEMO but also Movim stuff...but also whatever Salut-a-toi adds up
  141. emus I dont understand
  142. pep. Yeah I also don't understand. Is that the list of XEPs you'd like to see explained
  143. peetah I'm not sure it is the best since I don't have the basic bricks to explain how it works: there are only complex specifications that even repulse those already involved
  144. peetah I would like to create those basic bricks that would allow any one to have a global understanding of this ecosystem
  145. emus And I join your intention. I am just not sure whats a good way. Mapping of or generaliszing the important XEPs could be helpful too? even for tech-newcomers
  146. peetah I believe a simplification effort is required in order to redirect interested end-users to something more accessible than the XEPs specifications: what, why, current limits and possibly how it compares to their equivalents in other tools
  147. emus Yep! Why XMPP? <reasons>
  148. SouL has left
  149. debacle has left
  150. alacer has left
  151. alacer has joined
  152. Licaon_Kter has left
  153. emus has left
  154. emus has joined
  155. kikuchiyo has left
  156. kikuchiyo has joined