XSF Discussion - 2019-03-06


  1. zinid

    can someone point me where in the RFCs it's said that a client must ignore 'to' of incoming stanzas?

  2. zinid

    I might be blind, cannot find it

  3. zinid

    ah, found

  4. flow

    zinid, where?

  5. flow

    I only had https://tools.ietf.org/html/rfc6120#section-8.1.1.1 in mind

  6. zinid

    yes, it is

  7. zinid

    there is no need for the client to check the 'to' address of incoming stanzas. However, if the client does check the 'to' address then it is suggested to check at most the bare JID portion (not the full JID), since the 'to' address might be the user's bare JID, the client's current full JID, or even a full JID with a different resourcepart

  8. flow

    that is not really "most ignore", isn't it? ;)

  9. zinid

    sorry for not being exactly precise in this bureacratic chatroom!

  10. Ge0rG

    I'm currently challenged by "check whether the user has finished entering a JID yet". The current naive version just lets the server hammer DNS and s2s...

  11. Ge0rG

    https://op-co.de/tmp/yaxim-jid-search.mp4

  12. waqas

    Ge0rG: I don't think I've ever had say an email client attempt that… why check for valid JIDs that way?

  13. Ge0rG

    waqas: I hope for better usability. First I was going to filter based on the public suffix list, but then I realized it's huge, complicated and messy, and it doesn't support local deployments

  14. waqas

    "it doesn't support local deployments" — wat? browsers do embed it, and tend to work locally...

  15. Ge0rG

    waqas: I mean it won't accept "mycoolxmpp.local"

  16. waqas

    If you want local stuff, well "helloworld" is a valid local hostname

  17. Ge0rG

    Also I'd have to either embed an immediately outdated list or load it at runtime periodically.

  18. Ge0rG

    waqas: that's exactly my point

  19. waqas

    I'm struggling to see the usability goal. What are you trying to solve for?

  20. waqas

    People mistyping hostname?

  21. Ge0rG

    Giving people a way to explore xmpp? Dunno

  22. waqas

    I wonder if there's a use-case for a directory of all publicly accessible XMPP servers

  23. Ge0rG

    It would be a good thing for auto completion.

  24. zinid

    > Giving people a way to explore xmpp? That's not needed

  25. Ge0rG

    > Giving people a way to explore MQTT?

  26. Wiktor

    For me the demo looked good 👍 I'd use that.

  27. jonas’

    Ge0rG, maybe add an explicit search button and prepare to integrate it with Jabber Search

  28. Ge0rG

    jonas’: it'a already integrated, you just need to open the lower group

  29. Ge0rG

    I'm still not sure about "have all ways to add JIDs in one dialog" vs "omg what is all this shit"

  30. jonas’

    Jabber Search is not muclumbus

  31. Ge0rG

    Wait. What's Jabber Search then?

  32. jonas’

    XEP something

  33. Ge0rG

    something something.

  34. jonas’

    I don’t know it off the top of my head, you’ll find it in the XEP list, I’m at work

  35. Ge0rG

    https://op-co.de/tmp/smack-typesystem.png

  36. Ge0rG

    *sigh*

  37. zinid

    Ge0rG, you asked: http://upload.zinid.ru/xep-eax-csr.html

  38. Kev

    Is slixmpp now the only maintained fork of sleek?

  39. pep.

    Kev, are there any others?

  40. Kev

    That's what I was asking.

  41. pep.

    No you're asking if slixmpp is the only one :p

  42. pep.

    I know only of slixmpp

  43. pep.

    Link Mauve, ^

  44. Link Mauve

    That’s the only one I know of.

  45. Link Mauve

    And I’d really like to merge both projects, the only thing SleekXMPP has got for it is its python2 support, and that is getting EoL’d quick.

  46. Link Mauve

    SleekXMPP still seems pretty popular, so if we could just reuse the name and the website and rename the next slixmpp version that, it’d be perfect.

  47. flow

    Ge0rG, https://github.com/Flowdalic/android-xmpp-iot-demo/blob/master/app/src/main/java/com/clayster/xmppiotdemo/JidTextWatcher.java#L61 is what I did a while ago

  48. flow

    regarding user provided jid string verification

  49. Ge0rG

    flow: yeah, but I also need it to work on domain JIDs, and this is somewhat harder ;)

  50. Ge0rG

    flow: did you see last night's yaxim video?

  51. flow

    Ge0rG, no

  52. Ge0rG

    flow: what I'm essentially looking for is "does the whole string / what comes after an @ qualify as a domain part"

  53. Ge0rG

    https://op-co.de/tmp/yaxim-jid-search.mp4

  54. Ge0rG

    flow: ^

  55. Wiktor

    Ge0rG: can't you just cheat somehow? I dont know... Fire dns srv queries on the client?... :)

  56. Ge0rG

    Wiktor: my ISP is already serving ServFail to SRV requests... with a 3s delay.

  57. Ge0rG

    Sending a disco#info is actually the least work for me.

  58. Wiktor

    Dns over HTTPS! For every problem I've got two solutions a.k.a "next problems"

  59. Wiktor

    for faster access better grab a local client index of all jabber domains, as TLS certs are now logged in Certificate Transparency logs the list is there... but it would take a lot of space... so use bloom filters, see, easy! ;-)

  60. Wiktor

    no, I just got a better, CaaS - Completion as a Service, you send a query and it autocompletes the domain part, then you can start offering it to others for a small fee... it's an unmet need right there :)

  61. flow

    Ge0rG, the "what comes after the @ qualify as domain part" check is what the code I linked does

  62. flow

    plus, does the string before the @ qualify as localpart

  63. Ge0rG

    flow: it only checks whether what's between @ and / is non-empty.

  64. flow

    Ge0rG, I don't think so

  65. Ge0rG

    Wiktor: https://foaas.com/greed/cloud/Ge0rG 😁

  66. Wiktor

    Wow, great... 👍

  67. Ge0rG

    flow: it calls JidUtil.isValidEntityBareJid() which splits and calls XmppStringUtils.parseDomain() which just splits, and then checks the length.

  68. Ge0rG

    flow: unless you added magic in smack 4.4

  69. Ge0rG

    or rather, jxmpp 0.6.4

  70. flow

    Ge0rG, hmm, no?

  71. flow

    you possibly missed that line: https://github.com/igniterealtime/jxmpp/blob/0.6/jxmpp-jid/src/main/java/org/jxmpp/jid/util/JidUtil.java#L140

  72. Ge0rG

    flow: ah, right, it goes down into Domainpart.from() which also ensures domainprep.

  73. Ge0rG

    but I'm not sure how much that actually adds.

  74. Ge0rG

    flow: or, in other words, does it add any value over attempting to JidCreate.from(string)?

  75. Ge0rG is also interested in feedback on the search UX

  76. zinid

    btw, great twitter (uh!) thread what people thinking about XMPP: https://twitter.com/bascule/status/1102693889842921472 😀

  77. flow

    Ge0rG, it does. It ensures that there is a "valid" localpart and domainpart, and no resourcepart, and provides better feedback about what is missing for the string to become a valid JID

  78. Ge0rG

    flow: but I'm hiding the error anyway, at least in the last version ;)

  79. Ge0rG

    https://twitter.com/DLitz/status/1102961301616156676 🤣🤣🤣

  80. zinid

    Ge0rG, wut?

  81. zinid

    I actually replied to this

  82. dwd

    Has anyone got a server-side implementation of MIX-PAM (XEP-0405) anywhere?

  83. Ge0rG

    zinid: yeah, saw that a bit later. Master trolling at work.

  84. zinid

    dwd, I have

  85. zinid

    dwd, part of ejabberd 19.02 actually

  86. Ge0rG

    Damn android single tasking. If I open Twitter links from yaxim, then use yaxim, the Twitter client forgets what I was looking at.

  87. zinid

    Ge0rG, yeah, that's annoying AF

  88. zinid

    Ge0rG, and btw I didn't mean to troll, but whatever

  89. Ge0rG

    zinid: not speaking of you! 😀

  90. zinid

    oh, really, I'm impressed

  91. zinid

    yeah, that dude just goes full strawman hoping from subject to subject

  92. zinid

    and gains a ton of likes because, well, XMPP is godawful

  93. dwd

    zinid, Oh, really? That's awesome. I'll check it out.

  94. zinid

    dwd, I can create you an account at my server, I'm running mix pam there

  95. dwd

    zinid, Is it a module? And is it available (open source, downloadable, whatever)?

  96. zinid

    dwd, yes, it's a module (actually two) and is a part of ejabberd distribution

  97. Ge0rG

    While that thread is actually rather sad, it's showing Twitter at its best. You can try to convince them, or try to insult them, but it's not going to change anything.

  98. dwd

    zinid, Do you have any clients or MIX servers that use it?

  99. dwd

    Oh, wow. Found a client library that supports MIX, and claims to have a GUI client. (Which is an example only - I've not attempted to see if it has a MIX UI yet).

  100. pep.

    dwd, slixmpp has OMEMO, Jingle, and MAM support (I think?), poezio has none of that :P

  101. zinid

    dwd: no I don't, Daniel has some experimental branch of Conversations though, we tested our implementations

  102. dwd

    zinid, https://github.com/qxmpp-project/qxmpp might work, I have no clue.

  103. dwd

    pep., Yeah, the MAM is handy, and the '60, but no MIX. I might have to fix that.

  104. zinid

    Ge0rG: true, they have already set up their minds, and I am not sure this is actually attributed to Twitter

  105. pep.

    Heh, qxmpp, is that what the telepathy people starting to use?

  106. pep.

    for telepathy-nonsense?

  107. zinid

    Ge0rG: this is just blatant IT hype and groupthinking

  108. Ge0rG

    zinid: twitter is known for this kind of toxicity. It's also a good place for short, "state-less" rants making it impossible to have a proper debate based on merit

  109. Ge0rG

    it's like XMPP! 😁

  110. zinid

    Ge0rG: well you can debate at other more appropriate place, but you can do nothing when you're told that XML is shit (which is I agree BTW)

  111. zinid

    and every xmpp discussion ends up there

  112. Ge0rG

    zinid: I agree with that too, and I'd love to see them solving extensibility on top of JSON :>

  113. Ge0rG

    But they can't.

  114. zinid

    Ge0rG: you can do that in asn.1 😁

  115. zinid

    oids ftw!

  116. Ge0rG

    Anyway, with Matrix we do have the anti-design to XMPP. Monolithic spec instead of modular, JSON instead of XML, persistent message database instead of a stream of ephemeral events. Let's wait five years and see what sticks.

  117. dwd

    Extensibility is easy in JSON. Permissionless extensibility is somewhat harder.

  118. jonas’

    zinid, mmm, OIDs, which you can only allocate with a bureaucratic process which doesn’t even work?

  119. zinid

    yeah, sticks where?

  120. zinid

    jonas’: why doesn't it work? last time we registered oids in iana

  121. zinid

    in 2004 😂

  122. dwd

    But my usual argument about XMPP and XML is that we don't use XML like SOAP - instead, it's very terse XML and pragmatically-driven, so while it's still XML, it's vastly nicer than what they may have experienced before.

  123. Andrew Nenakhov

    > persistent message database instead of a stream of ephemeral events. That one is actually good

  124. dwd

    Sorta - you can record a stream, but you can't make a persistent database ephemeral.

  125. zinid

    dwd: yeah, but I'd love to see those arguments spelled at public, not in this chat where everyone is already converted 😁

  126. dwd

    zinid, For sure.

  127. dwd

    zinid, Also, the "Nobody uses XMPP" thing, except for half the games industry, military, government, and so on.

  128. zinid

    also, though xml is not, let's say, ideal, it's not as fatal as opponent trying to draw it

  129. zinid

    also, though xml is not, let's say, ideal, it's not as fatal as opponents trying to draw it

  130. zinid

    it's just not ideal, indeed

  131. Ge0rG

    Indeed. There are larger problems in XMPP. Maybe we should tell them about the mess that is MUC, Carbons and message routing (which are just my favorite pet problems)

  132. Andrew Nenakhov

    But but it's confusing! 😂

  133. zinid

    > That one is actually good Andrew Nenakhov: agreed

  134. Seve

    pep., qxmpp is what Kaidan is using if I recall correctly, lnj?

  135. zinid

    Ge0rG: we can say that of course, but they won't even understand those problem may exist, because designing protocols is easy

  136. zinid

    you just need to stick to json and http!

  137. zinid

    > That one is actually good although seems like the design is awful, looking at how their servers behaves

  138. Ge0rG

    zinid: implement matrix protocol in ejabberd! 😁😁

  139. zinid

    and you probably cannot make such type of replication terribly efficient, so matrix will be always slower than xmpp by design

  140. zinid

    Ge0rG: we considered that a few years ago and I had the discussion about it a few *days* ago with the boss

  141. zinid

    the conclusion is "this will require too much effort, let's wait if matrix demonstrate some real progress except hype"

  142. zinid

    5 years have passed and where is the progress?

  143. Zash

    What's 'this'?

  144. zinid

    Zash: implementing matrix in ejabberd

  145. zinid

    note that after 5 years of evolving of xmpp we had several servers and clients and rfcs

  146. Zash

    Implementing the c2s protocol is probably doable, then we can steal all their clients. ;)

  147. Zash

    The s2s protocol .. yeah, no.

  148. zinid

    Zash: doable of course, but requires full time commitment and we are currently limited in human resources at p1

  149. pep.

    s/ at p1//

  150. zinid

    mqtt and sip were much easier to implement

  151. zinid

    also, the only attractive part of the protocol is replication, everything else is terrible, they reiterate the mistakes of xmpp

  152. zinid

    and I personally rather disappointed in federation and looking at P2P

  153. Zash

    Doesn't MQTT provide way less functionality than what XMPP-Core does?

  154. Zash

    It seems weird to me to compare MQTT to XMPP

  155. zinid

    Zash: sure, mqtt is very dumb

  156. zinid

    Zash: you cannot compare them

  157. zinid

    I don't understand why people do that all the time

  158. Andrew Nenakhov

    I personally don't think that full p2p will have great UX

  159. zinid

    Andrew Nenakhov: not full

  160. zinid

    I could say here wait for me to complete my xor proposal, but seems like nobody reads them 😂

  161. zinid

    Zash: did you read the matrix s2s spec BTW? Is it finalized?

  162. Zash

    zinid: Not really and not really.

  163. zinid

    ok, let's wait 5 more years

  164. zinid

    > Also, the "Nobody uses XMPP" thing, except for half the games industry, military, government, and so on. dwd: oh, just saw it. yeah, virtually every second our customer is gamedev, hehe. xmpp is quite strong there.

  165. zinid

    and again, also the reason I consider MIX: group chats in gamedev is hell, thousands of participants

  166. Andrew Nenakhov

    Our Groupchats should probably handle that well and quite easy to implement

  167. zinid

    Andrew Nenakhov: 😉

  168. Ge0rG

    zinid: it would be really great to have testimonials from them about XMPP

  169. Ge0rG

    zinid: or maybe at least contact people to interview, cc winfried

  170. zinid

    Ge0rG: hum, let me explain how their development is done: they hire some developers (usually from India) and assign them to work with us. their project managers are almost clueless and their bosses are totally clueless. so the question is whom to ask? that developer from India?

  171. zinid

    chat infrastructure is actually a huge pain for gamedev they offload the work because that's not their area of competence

  172. Ge0rG

    zinid: good point. Is there some kind of in-house senior tech project manager?

  173. zinid

    so it's just like to ask you to promote that cool Japan engine in your murican car.

  174. zinid

    Ge0rG: I don't contact them, so I am also not the right person to ask, sorry

  175. zinid

    and thanks gods I don't 😁

  176. Ge0rG

    Haha!

  177. lnj

    > pep., qxmpp is what Kaidan is using if I recall correctly, lnj? Yes, that's right and I'm working on the MIX implementation in QXmpp. It's not completely finished though and most of the pull requests haven't been merged yet.

  178. jonas’

    zinid, I assigned XEP-0415 to XOR and XEP-0416 to EAX

  179. jonas’

    push is done, waiting for the build to happen, so ETA 1h or so

  180. zinid

    jonas’, thanks a lot

  181. zinid

    https://rosenzweig.io/blog/the-federation-fallacy.html

  182. pep.

    zinid, #old, I linked that yesterday :p

  183. Andrew Nenakhov

    It was here a couple of days ago

  184. zinid

    argh

  185. zinid

    sorry guys, I'm too slow

  186. pep.

    https://lwn.net/Articles/781205/ comments

  187. zinid

    oh, good start: they attacked the author's graphs!

  188. Zash

    Don't read the comments

  189. zinid

    is it Dirac, power-law or loglog distribution? hum... so many questions

  190. Andrew Nenakhov

    That funny article failed to address the most famous federated protocol: email

  191. pep.

    No it did

  192. pep.

    You probably missed some points

  193. Ge0rG

    stop throwing links! I need to work still.

  194. Zash

    The part about how gmail has 100% of the market and self-hosting is impossible?

  195. zinid

    Ge0rG, I just copied it! You should have read it already

  196. Andrew Nenakhov

    pep., It didn't provide any graphs for email, I mean

  197. pep.

    Zash, I'm not saying I agree with all she's saying

  198. Ge0rG

    zinid: it's right behind your CA proto-XEP, but it will move up if you keep talking about it

  199. zinid

    Ge0rG, I shut up, carry on

  200. zinid

    nah, just joking, I cannot shut up

  201. Andrew Nenakhov

    Just claim that 'most people have email on Gmail', but what about outlook, Yahoo, mail.ru, hundreds of them noticeable big servers

  202. zinid

    Andrew Nenakhov, still power-law distribution

  203. Andrew Nenakhov

    Yes, but: not sharp and with plenty other choices.

  204. zinid

    I already have brought an article somewhere from 2001 where the same thesis about federation was spelled

  205. pep.

    zinid, I'm interested if you can find it again, but don't bother if it's too much of a hassle

  206. moparisthebest

    they are all basically the same "federation doesn't solve all problems" ok, agreed, also the sky is blue and water is wet, why the long blog post?

  207. Andrew Nenakhov

    Funny thing is, what do they offer as an alternative?

  208. Zash

    Wikipedia

  209. Zash

    ?

  210. Andrew Nenakhov

    Centralized services, 'because federations are centralized anyway'?

  211. Ge0rG

    Facebook!

  212. zinid

    pep., http://shirky.com/writings/powerlaw_weblog.html

  213. zinid

    pep., from 2003, sorry!

  214. zinid

    > In systems where many people are free to choose between many options, a small subset of the whole will get a disproportionate amount of traffic (or attention, or income), even if no members of the system actively work towards such an outcome. The very act of choosing, spread widely enough and freely enough, creates a power law distribution

  215. pep.

    thanks

  216. zinid

    so predicted 20 years ago

  217. zinid

    Andrew Nenakhov, centralization is a bad solution obviously

  218. zinid

    it has the same drawbacks plus others

  219. Zash

    That reminds me to search for ...

  220. Zash

    and find http://urbanpolicy.berkeley.edu/pdf/AQWJEG0804PB.pdf

  221. zinid

    btw, today I noticed that my xmpp domain was suspended (I forgot to pay for it). It's becoming quite annoying to self-host even if you have the needed qualification.

  222. Link Mauve

    That has happened so many times to me. >_<

  223. zinid

    The DNS Mafia!

  224. Ge0rG

    zinid: it always was an extortion business, but with the buy your own TLD for $$$ business, it became unbearable.

  225. Ge0rG

    We need an alternative DNS root!

  226. Ge0rG

    I propose the XSF.

  227. zinid

    right after the CA!

  228. zinid

    after me please

  229. Ge0rG

    Also DNS-over-XMPP!

  230. zinid

    we wanted to buy process.one and guess what? It's $8000 per year. Tell me about CA mafia now 😛

  231. zinid

    oh, it's still free, no surprise

  232. moparisthebest

    Ge0rG, why not cloudflare does it literally every other possible way https://developers.cloudflare.com/1.1.1.1/fun-stuff/

  233. moparisthebest

    it would avoid the TLS setup cost, should be pretty performant actually

  234. Ge0rG

    moparisthebest: that list is missing XMPP.

  235. pep.

    Ge0rG, add that to the missing integrations page :p

  236. Ge0rG

    I wonder if SamWhited knows somebody who can be convinced to make it happen

  237. moparisthebest

    it should be pretty easy to make a component to do that, hmmmm

  238. moparisthebest

    great I needed another useless project

  239. pep.

    If you want I have a whole list I can share with you

  240. zinid

    the list of useless things?

  241. pep.

    If you can do some of these for me

  242. moparisthebest

    I already have a whole list of my own thanks

  243. pep.

    zinid, useless and not useless. Often the line is pretty thin :P

  244. moparisthebest

    if I create a xmpp component to answer DNS queries, and add support to a DNS proxy to use it, will anyone in here use it ? :P

  245. Zash

    moparisthebest: Aware of any DNS client libraries that let you easily feed them data without it coming from the network?

  246. Zash

    If so, give me BASE64'd DNSSEC-signed blobs plz!

  247. Zash

    But then, what problem are you solving?

  248. moparisthebest

    I was not aware of one so I wrote one https://github.com/moparisthebest/jDnsProxy it would be easy to, using that, write a xmpp component to answer them, and a resolver to ask said xmpp component :)

  249. moparisthebest

    same problem DNS-over-HTTPS and DNS-over-TLS is solving I guess?

  250. moparisthebest

    maybe faster though, if the S2S stream is already established

  251. Ge0rG

    Please make a bot that runs `dig $message_content` and responds with the stdout+stderr content.

  252. Zash

    :D

  253. Ge0rG

    I promise not to do evil. Not too much at least.

  254. jonas’

    17:24:55 Vlatin Pudimir> !dig SRV _xmpp-server._tcp.muc.xmpp.org 17:24:56 foorl> _xmpp-server._tcp.muc.xmpp.org (SRV): 1 1 9269 xmpp.xmpp.org.

  255. Zash

    moparisthebest: It won't help clients do initial connections tho, where we have actual problems still.

  256. Ge0rG

    jonas’: now all we need to do is to host that bot as a component on 1.1.1.1

  257. Zash

    I'm sure Ge0rG can tell us (or already did?) how many fail at SRV lookups

  258. Ge0rG

    can you have SRV records for IP addresses?

  259. moparisthebest

    Zash, it will if the resolvers are set up to use it, like my router is

  260. Zash

    Routers that don't support SRV lookups but they'll support DNS-over-XMPP?

  261. Ge0rG

    Wow, my ISP fixed their resolver. It's not servfailing after 3s any more.

  262. moparisthebest

    but wire-format-wise it'd just be like DOH, base64'd raw TCP request bytes

  263. moparisthebest

    Zash, yea honestly endpoints will end up using DOH etc first before all the routers get fixed, android phones already do DNS-over-TLS to google by default now

  264. moparisthebest

    firefox also can or does

  265. Wiktor

    Dns over xmpp sounds like a perfect April 1st XEP folks

  266. jonas’

    better than jackbeer?

  267. moparisthebest

    how about this, if I can write the code to get a working POC in the next, 2 weeks max, will someone else commit to writing the XEP :D Wiktor ? :)

  268. zinid

    moparisthebest, the XEP for April 1st you mean?

  269. moparisthebest

    yea

  270. zinid

    not sure if trolling

  271. zinid

    ah

  272. Ge0rG

    moparisthebest: are you going to map all DNS payloads to XML elements?

  273. moparisthebest

    hell no, down that path only lies tears

  274. Ge0rG

    tears of joy!

  275. moparisthebest

    it'll be just like DOH, base64 raw DNS packet bytes

  276. Ge0rG

    😂

  277. Wiktor

    moparisthebest: 👍

  278. moparisthebest

    call it DOX ?

  279. Ge0rG

    moparisthebest: that's not XMPP style.

  280. Wiktor

    Then we get cloud flare in the loop

  281. moparisthebest

    it's not HTTP style either yet here we are

  282. Ge0rG

    moparisthebest: if you do that, you can as well just run jonas’' SRV bot.

  283. Wiktor

    They'd like the April joke I bet haha

  284. moparisthebest

    Ge0rG, no it'd be actually useful, because you'd have a UDP/TCP DNS port locally you can query, put in resolv.conf or whatever, except it's just connected to an XMPP server to resolve names

  285. moparisthebest

    for, some definition of useful :P

  286. Wiktor

    wait a minute, Ge0rG was complaining about his ISP failing DNS queries... if only he had DNS-over-XMPP!

  287. moparisthebest

    he soon will!

  288. uhoreg

    There's already DNS over HTTPS and HTTP over XMPP, so if you chain them together, then you can easily get DNS over XMPP

  289. moparisthebest

    so... what's the latest/greatest java xmpp library for clients nowadays...

  290. Ge0rG

    uhoreg: that sounds like there is no need for an own XEP

  291. Ge0rG

    moparisthebest: sed

  292. zinid

    oh, I finally finished reading that "federation sucks" article

  293. zinid

    great ending: > To see the future of liberty for the many, look not to the obscurity of XMPP, for arcane technical voodoo can never be wielded by those who need it most. To see the free future, look to Wikipedia.

  294. flow

    re council@: I think it is a terrible idea if we start to omit namespace bumps on experimental XEPs. That will only lead to confusion and a bad reputation wrt. XMPP's interoperability

  295. zinid

    flow, so, after the publication of my XEPs I now need to bump the namespaces after every second PR? nowaaaay

  296. zinid

    however, not that I'm against that much

  297. flow

    zinid, that I why I am in favor of an "incubating" state of XEPs, where they got an stable identifier and a clearly visibile notice that there may be no namespace bumps on backwards incompatible changes

  298. zinid

    flow, if you incubate too much how they will become visible?

  299. Ge0rG

    flow: that's called "Experimental"

  300. flow

    Ge0rG, I hope not

  301. zinid

    whatever, I'm not against at bumping the namespace at every commit, I know sed!

  302. flow

    I see people starting to implement XEPs and then wondering why their implementation does not interoperate with another one

  303. Ge0rG

    Namespace bumping is one of the worst ways to iterate protocols.

  304. flow

    Ge0rG, I think you mean backwards incompatible changes are the worst way to iterate protocols

  305. zinid

    flow, but when you implement IETF I-D you don't wonder?

  306. Ge0rG

    Unless it is a major rewrite, protocols should come with feature tags.

  307. flow

    but sometimes they can not be avoided, but in this case you need a namespace bump

  308. flow

    at least for my definition of backwards incompatible change

  309. flow

    zinid, exactly

  310. flow

    probably because an ID has not RFC number

  311. zinid

    flow, I kinda agree that we need a concept of a "living standard" and "final"

  312. zinid

    everything in between should be burnt with fire

  313. flow

    but an experimental XEP has an XEP number

  314. zinid

    I honestly prefer numbers, it's easier to reference them

  315. flow

    it may appear as a small difference but I think it has an huge impact on how people perceive the standard

  316. flow

    zinid, as soon as the thing is out of the incubating state, give it a number

  317. zinid

    XEP-DRAFT-0123

  318. zinid

    DER-0123!

  319. flow

    or, even much better, a short name

  320. flow

    I never understood why we use numbers when humans are much better with letters

  321. Ge0rG

    flow: let's namespace-bump MUC and see what happens?

  322. flow

    I already memorized the short names of zinids new XEPs, and have a idea what is behind every name

  323. flow

    I doubt I would have been able to memorize it if they where assigned a number on submission

  324. zinid

    flow, my next xep will have a terrible name, I cannot invent it

  325. wurstsalat

    Should the upcoming sprint be announced on xmpp.org ?

  326. Zash

    Yes

  327. zinid

    summit, fosdem, sprint