XSF Discussion - 2018-05-03


  1. moparisthebest

    are there other ways of connecting to xmpp servers besides rfc-style starttls, bosh, websocket, and xep-0368 style direct TLS ?

  2. moparisthebest

    https://github.com/xsf/xeps/pull/627 https://burtrum.org/hacx/

  3. jonasw

    can XEP-0114 components send presence probes?

  4. mrdoctorwho

    jonasw, yes

  5. jonasw

    mrdoctorwho, cool :)

  6. Maranda

    moparisthebest, I suppose this would count as bosh as well https://xmpp.org/extensions/xep-0252.html

  7. Maranda has script syntax for JSON

  8. Maranda

    unused useless whatever

  9. Maranda

    5223 would be the defacto standard for _xmpps-client or is that still considered legacy?

  10. lovetox

    i dont think so

  11. lovetox

    was it not that back in time people thought nobody is going to use it anymore in the future

  12. lovetox

    and now it seems it comes back

  13. lovetox

    oh you mean the port?

  14. Maranda

    I mean the port yes, since there's a srv record for it one wonders if there's a registered standard port, or if we're gonna reuse legacy ssl port out of assumption lovetox

  15. lovetox

    Gajim uses 5223 if there is no srv record

  16. moparisthebest

    There is no standard port in xep368

  17. debacle

    I hope this "marketing question" is right here: Why does https://xmpp.org/ bring the slogan "The most secure messaging standard" in focus? There are many things to say about XMPP, and it's not bad on security, but still: Is this the most relevant single thing marketing should focus on?

  18. MattJ

    debacle, have a suggestion for an alternative?

  19. jonasw

    (speaking of marketing, shouldn’t there be a board meeting soon-ish?)

  20. MattJ

    In 40 minutes

  21. debacle

    MattJ, I don't have an alternative, but would probably highlight universality of XMPP (IM, IoT, group communication/social, VoIP), in contrast to a specific use case. Marketing people would probably object to blurring the focus in that way :~)

  22. Holger

    And open federation.

  23. debacle

    But "most secure messaging standard" doesn't sound really compelling to me.

  24. debacle

    Even if it is (were) true.

  25. Holger

    No idea how to pour this into a marketing phrase but would do we pay our marketing department for!

  26. MattJ

    XMPP is a protocol standard, not an open federation

  27. MattJ

    See how it's complicated? :)

  28. jonasw

    remind me, which marketing department again?

  29. Holger

    An especially secure standard?

  30. Ge0rG

    Who are we even marketing XMPP to?

  31. MattJ

    debacle just became our marketing department

  32. jonasw

    boohahaha

  33. MattJ

    as being the only person to bring this up since the site was created

  34. Holger

    I was thinking exactly the same though :-)

  35. Holger

    (But I won't join the department.)

  36. jonasw

    as if you had a choice

  37. Holger

    :-)

  38. Holger

    The subtitle is better-fitting though, I think. "Battle-tested. Independent. Privacy-focused."

  39. pep.

    agreed.

  40. pep.

    Also I second Ge0rG's question, "Who are we even marketing XMPP to?"

  41. jonasw

    raise the subtitle to main title?

  42. Seve/SouL wishes XMPP beig THE messaging standard :)

  43. moparisthebest

    How about "XMPP, screw walled gardens"

  44. jonasw

    hah

  45. MattJ

    moparisthebest, again - WhatsApp was XMPP based, Facebook managed an XMPP walled garden for some time, and so on...

  46. moparisthebest

    yea the who really matters, a business wants something different than privacy focused individual looking to replace LATEST_APP

  47. MattJ

    xmpp.org is for developers, IMHO

  48. jonasw

    I tend to agree

  49. pep.

    MattJ, that's what I would think. What do the statistics say?

  50. MattJ

    I think by the time an end user reaches xmpp.org, we've lost them :)

  51. moparisthebest

    "XMPP, screw walled gardens, unless you want to build a walled garden with XMPP, but then you should be ashamed because you are a bad, bad person"

  52. moparisthebest

    got a bit unweildy there

  53. jonasw

    :D

  54. jonasw

    MattJ, buuuut... what page would an end-user reach instead? :)

  55. pep.

    I vote for moparisthebest as marketing

  56. MattJ

    jonasw, doesn't currently exist

  57. pep.

    clients.html?

  58. Holger

    jonasw: The app store page.

  59. jonasw

    :<

  60. Ge0rG

    "XMPP, come to us and get lost!"

  61. Kev

    Nothing fundamentally wrong with building unfederated or not publicly federated systems with XMPP.

  62. Holger

    Ge0rG: lol, very nice.

  63. Zash

    XMPP - The Standard

  64. Kev

    "XMPP. Standards are good, and we have many to choose from"

  65. Seve/SouL

    Zash, exactly

  66. Ge0rG

    I think we need something user-friendly at jabber.org

  67. pep.

    Ge0rG, what are you waiting for

  68. pep.

    I don't think xmpp.org should worry about this though

  69. jonasw

    +w on jabber.org probably

  70. Ge0rG

    pep.: I'm waiting for some more volunteers to start together the Jabber Software Foundation.

  71. Zash

    Ge0rG: If you want it done, you better do it yourself.

  72. Ge0rG

    Zash: I tend to agree, except for the bus factor

  73. jonasw

    starting a "foundation" all by oneself is a bit weird unless you have a few M$currency...

  74. pep.

    I say if you want traction you'd better build a service rather than a front to redirect to tons of different clients

  75. jonasw

    Ge0rG, ssss the bus-factor among the XSF members!

  76. jonasw

    pep., oddly enough, Ge0rG already offers a service :)

  77. pep.

    jonasw, I know

  78. jonasw

    so maybe he’s at the next step?

  79. Ge0rG

    I'm offering a service, a client and consulting.

  80. pep. hands out badges to Ge0rG

  81. moparisthebest

    proposed jabber.org slogan: "Jabber, use the name XMPP instead unless you have a team of lawyer's to rival Cisco"

  82. Ge0rG

    That trademark was the single most community-hurting thing in Jabber™ history.

  83. pep.

    You mean apart from lack of money and manpower

  84. Ge0rG

    pep.: no.

  85. Ge0rG

    pep.: money and manpower are optional if you have some dedication and no trademark trouble

  86. jonasw

    manpower is never optional.

  87. jonasw

    but dedication usually implies manpower

  88. pep.

    money can buy manpower

  89. Ge0rG

    money can buy trademarks.

  90. pep.

    we need money!

  91. Seve/SouL

    Just call it Zimpy, the chat

  92. pep.

    money and marketing!

  93. jonasw

    the long-term plan would be to (a) have good clients, (b) rebrand everything to FancyNewName once the clients are ready

  94. pep.

    Here, I just saved us

  95. Ge0rG

    jonasw: said the author of Jabber™Cat

  96. MattJ

    Heh

  97. pep.

    :D

  98. jonasw

    Ge0rG, the "Cat" is the important part, not the "Jabber"

  99. Ge0rG

    jonasw: I suggest you rename it to SchrödingersCat then.

  100. jonasw

    unwieldy and un-google-able

  101. Ge0rG

    ChatCat

  102. jonasw

    trademarked

  103. Ge0rG

    CatChat?

  104. jonasw

    (I fear we’re now going through the same iterations I went through before settling on Jabber™Cat)

  105. jonasw

    (note that JabberCat wasn’t my first choice)

  106. Ge0rG

    > GitHub - skylerto/chat-cat: A chat application written in Node.js. There must be some kind of Rule 34 for Node.js

  107. jonasw

    lol

  108. Ge0rG

    I'm still fed up with my "mbsync must have some way to do imap idle" research results

  109. moparisthebest

    I have an idea, and I understand it might be controversial, but why don't we come up with a neat 4 letter acronym? What about XMPP ? :P

  110. jonasw

    moparisthebest, do you know of any sucessful general-population application which uses a four-letter acronym?

  111. pep.

    ping

  112. pep.

    ah it's not

  113. Ge0rG

    moparisthebest: we still haven't recovered from the last time we attempted that rebranding

  114. pep.

    hmm

  115. moparisthebest

    jonasw, IMAP, HTTP ?

  116. Ge0rG

    But yeah, Ex-MP-Pee is awesome.

  117. jonasw

    moparisthebest, those are protocols, not applications

  118. jonasw

    the applications are "E-mail" and "The web" on one layer of abstraction, or "Outlook"/"Gmail", "Firefox"/"Chrome"/"Internet" on another

  119. moparisthebest

    well I mean no application is named XMPP is it?

  120. jonasw

    this isn’t about naming the protocol

  121. jonasw

    it’s about naming the IM network

  122. jonasw

    or ecosystem

  123. jonasw

    or how you wanna call it

  124. MattJ

    "Let me send you an SMTP with the document when I get to the office"

  125. jonasw

    exactly

  126. Ge0rG

    MattJ: can't you send me an IMAP instead?

  127. MattJ

    Ge0rG, sorry, I only JMAP

  128. MattJ

    https://tools.ietf.org/id/draft-kundrat-imap-submit-00.html

  129. MattJ

    I knew someone had to have done it

  130. Ge0rG

    but "submit" is not a PC word

  131. moparisthebest

    I just feel like it's about 20 years late for a rebranding

  132. moparisthebest

    but oh well

  133. Ge0rG

    moparisthebest: To the Time Machine!

  134. MattJ

    Ge0rG, maybe why http://trojita.flaska.net/draft-imap-sendmail-00.html :)

  135. Ge0rG

    moparisthebest: I think there is much irony in how the JSF rebranded itself into something that doesn't do ecosystem maintenance any more, a long time ago, while burning the original name with trademark complexity

  136. jonasw

    moparisthebest, WhatsApp took XMPP, rebranded it to WhatsApp and was quite succesful at it

  137. jonasw

    I don’t see why a dedicated community of XMPP developers couldn’t do the same, but with federation.

  138. MattJ

    +1 to this

  139. pep.

    yeah

  140. moparisthebest

    I don't think it was the name, I think it was the money

  141. MattJ

    Except

  142. Zash

    Ge0rG: Well, Jabber Inc was involved somehow, then got bought by Cisco..

  143. Ge0rG

    jonasw: because there is a lack of a dedicated developer community, SV startup funding and the trademark name is burned.

  144. MattJ

    "dedicated community of XMPP developers" would totally fail :)

  145. jonasw

    moparisthebest, it wouldn’t have succeeded with a crappy name like XMPP.

  146. MattJ

    Because we're terrible at everything except making protocols and writing code (and some might argue we're not too good at those things either ;) )

  147. pep.

    aren't we a dedicated community of developers already?

  148. pep.

    maybe not that dedicated

  149. jonasw

    pep., yeah, that’s the issue

  150. Ge0rG

    MattJ: the one thing we excel at is bike shedding. If life gives you lemons, make lemonade - so what should we do?

  151. Ge0rG

    Maybe go into politics?

  152. pep.

    jonasw, please free me from $dayjob

  153. jonasw

    actually, I am not really allowed in this discussion as per the "no discussions unless an XMPP related commit in the last 24 hours". and I haven’t been allowed for weeks now.

  154. jonasw

    Ge0rG, :D

  155. jonasw

    (I /wish/ I was allowed, but among the masterthesis, a bunch of private stuff going on and the job, there isn’t much time left.)

  156. pep.

    jonasw, I don't think that's an issue specific to XMPP anyway

  157. jonasw

    it’s an issue specific to FLOSS

  158. pep.

    yes

  159. jonasw

    and right now there aren’t any serious non-FLOSS federating IM products

  160. moparisthebest

    I still think it's all about money

  161. moparisthebest

    you can push any crap product given enough money

  162. Zash

    Marketing budget!

  163. moparisthebest

    on the other hand, companies can't make money pushing an xmpp client, because it's not a walled garden

  164. MattJ

    Indeed it is

  165. moparisthebest

    pushing a federated xmpp client*

  166. jonasw

    I bet one of the first things a professional marketing person would say is "folks, you need a rebrand" ;-)

  167. Holger

    You can fail pushing a product with money but you can hardly succeed without.

  168. moparisthebest

    client-wise Conversations seems by far the most successful, but it's a big nothing compared to whatsapp for example

  169. Ge0rG

    jonasw: that's how they make money, right?

  170. pep.

    Holger, hah

  171. moparisthebest

    jonasw, their first thing would be 'you need to hire me, a professional marketing person'

  172. moparisthebest

    then since you'd expect them to do *something*, they'd probably pick something useless like that

  173. jonasw

    I think the name and design of a thing matters more than you’d think, but I’m afraid we have to agree to disagree here.

  174. moparisthebest

    to be fair I understand that means nothing at all to me and more than nothing to other people :)

  175. moparisthebest

    I've been using linux on the desktop since 2006 if that tells you something about my tastes

  176. Guus

    It's time for the weekly board meeting. Ralph sent his apologies. Who's here?

  177. Guus

    MattJ, Martin, Nyco?

  178. MattJ

    Hey

  179. Guus

    ... this does not bode well.

  180. nyco

    Hello

  181. nyco

    test

  182. nyco

    we have the quorum

  183. Guus

    yey

  184. MattJ

    :)

  185. Guus bangs a gavel

  186. Guus

    0. Role Call and Agenda

  187. Guus

    we've established that we're here

  188. Guus

    The agenda will be taken from https://trello.com/b/Dn6IQOu0/board-meetings as usual.

  189. Guus

    Does anyone want to add anything?

  190. MattJ

    Nothing here

  191. Guus

    1. Minute taker

  192. Guus

    Volunteers kindly line up in rows of 5

  193. MattJ

    *Rows of 0.5

  194. MattJ

    I'll do it

  195. Guus

    thank you

  196. Guus

    2. Topics for discussion

  197. Guus

    (none)

  198. Guus

    sorry, for _decision_ that is.

  199. Guus

    3. Reviewing the commitment list

  200. Guus

    3.1 The membership survey on priorities

  201. Guus

    Mattj, how is that coming along?

  202. MattJ

    It's fine... sorry, I should have sent it out but haven't yet

  203. MattJ

    I'll aim to do it later today

  204. MattJ

    Just need to draft a short email and send the link to members@

  205. Guus

    excellent

  206. Guus

    3.2 The online shop for selling swag

  207. Guus

    Nyco, I think you were going to do some further investigation, right?

  208. Andrew Nenakhov

    jonasw, > I don’t see why a dedicated community of XMPP developers couldn’t do the same, but with federation. Because too many XEPs are written by theoreticians who don't produce working implementations.

  209. nyco

    sorry, I did not dedicate time for this

  210. Guus

    (Andrew, would you mind waiting for 20 minutes with other discussions while we have our short meeting please?)

  211. nyco

    aaah, if we had threads...

  212. Guus

    nyco, can you do it before the next meeting?

  213. Guus

    threads?

  214. nyco

    difficult, but I can find time to draft something, don't expect elaborate study

  215. nyco

    is this acceptable?

  216. Guus

    iirc people were primarily interested in the price structure and a brief comparison with alternatives

  217. Guus

    I personally don't expect an elaborate study.

  218. nyco

    that's it

  219. nyco

    ok

  220. MattJ

    wfm

  221. Guus

    thanks

  222. Guus

    3.3 Collect info on the role/responsibilities of the XO

  223. Guus

    That one is assigned to Martin - I'm assuming no-one looked into this?

  224. MattJ

    I don't think so, no

  225. Guus

    4. Items for discussion

  226. Guus

    4.1 Fundraising/Financials

  227. Guus

    I've not done much more on that. The treasurer did send out an email earlier today that he's trying to follow up on this later this month.

  228. Guus

    'this' being an inventory of the state of our sponsors

  229. Guus

    or at least, that's how I interpreted his message.

  230. Guus

    I am happy for us to leave it at that, for now - but maybe someone wants to discuss something related?

  231. MattJ

    That's fine by me

  232. nyco

    not for me

  233. Guus

    nyco, it's not fine for you, or you don't want to discuss something related?

  234. Guus

    given no response, I'm assuming the latter.

  235. Andrew Nenakhov

    Guus, sorry.

  236. nyco

    ah 😉 I do not want to discuss this, sorry

  237. Guus

    ok 🙂

  238. Guus

    no worries Andrew

  239. Guus

    4.2: Search for XO.

  240. Guus

    let's first get clear what the roles/responsibilities for that officer are.

  241. MattJ

    Right

  242. Guus

    to bad Peter is not here, he might be able to shed some light on that.

  243. Guus

    I'll try to ping him

  244. MattJ

    He already said some time back he did almost nothing in that role

  245. Guus

    I wonder if there was something that he _should_ have been doing 🙂

  246. MattJ

    Our discussion led us to - maybe that position should be more active

  247. Guus

    or _could_

  248. MattJ

    which we'd need to define

  249. MattJ

    Finding somebody willing to do next to nothing shouldn't be too hard :)

  250. nyco

    it's the responsibility that might frighten

  251. nyco

    it's the little non-nothing to do

  252. MattJ

    also any ambiguity in responsibilities

  253. MattJ

    Also... 100% of the current Board is based in the EU I believe. That begs the question, must the ED be in the US?

  254. Guus

    ED will probably outlive the yearly board

  255. MattJ

    I'm guessing not, but it seems a bit strange to have a US org run almost entirely from Europe :)

  256. nyco

    United States of Europe 😉

  257. Guus

    That's more related to the location where we're incorporated (<- unsure of the exact english term for that), than the location of the ED, right?

  258. nyco

    USE

  259. Guus

    USEMINUSUK soon

  260. MattJ

    Guus, changing where the XSF is incorporated is a bit hard compared to anything else :)

  261. MattJ

    I don't currently have any reason to believe that a non-US ED is a problem

  262. MattJ

    Just curious though

  263. Guus

    I'm wondering why you bring that up in the first place

  264. Guus

    I've never given the nationality of any officer any thought at all.

  265. Guus

    which makes my curious as why you did, just now 🙂

  266. MattJ

    I see it being a problem with e.g. bank account access, for example

  267. MattJ

    I know you said we can put Alex on a plane, sure

  268. Guus

    That's more relevant to the role of Treasurer than ED, I think?

  269. MattJ

    But it seems a bit strange having a US organisation with nobody responsible for it actually located in the US

  270. Guus

    true, but officers change. I wonder that if we act on that now, we migth end up with a similar problem anyways in a year or so.

  271. MattJ

    I'm not proposing any action. Just it was a question that came to mind in the context of the ED search

  272. Guus

    ok

  273. Guus

    let's leave it at that for now then 🙂

  274. Guus

    5. AOBs

  275. Guus

    anyone?

  276. MattJ

    None here

  277. nyco

    none

  278. Guus

    6. Time of next

  279. Guus

    +1w is Ascension day (and Ralph already mentioned he'd not be able to make it)

  280. Guus

    shall we do +2w?

  281. MattJ

    I also may not be able to make next week

  282. MattJ

    So yes, let's skip

  283. nyco

    ok +2wx

  284. Guus

    ok

  285. Guus bangs gavel

  286. Guus

    thank you!

  287. nyco

    thx

  288. MattJ

    Minutes sent

  289. Guus

    Thank you