XSF Discussion - 2021-05-20


  1. qrpnxz

    alright, took me about 300 lines to make the domainpart parser. Not too bad lol

  2. flow

    for just the parser, that sounds like to much LOC

  3. flow

    for something that prepares, validates and enforces the domainpart, it is way to less (assuming no external libraries)

  4. qrpnxz

    definitely leaned on many libraries for it, and it's just the parser (which by definition validates btw), so the preperation part. I didn't do enforcement, because I actually don't know what the spec means by that. I think I just do that when I'm going to do comparison, or if I'm going to store or forwards the information.

  5. qrpnxz

    definitely leaned on many libraries for it, and it's just the parser (which by definition validates btw) I didn't do enforcement, because I actually don't know what the spec means by that. I think I just do that when I'm going to do comparison, or if I'm going to store or forwards the information.

  6. qrpnxz

    definitely leaned on many libraries for it, and it's just the parser (which by definition validates btw). I didn't do enforcement, because I actually don't know what the spec means by that. I think I just do that when I'm going to do comparison, or if I'm going to store or forwards the information.

  7. flow

    depends on your use case, servers to a lot of jid comparision and "is child of" checking. so it appears sensible to store the enforced variant of the JID representation

  8. Zash

    What /does/ enforcement mean?

  9. flow

    IIRC lowercasing the localpart for example

  10. Zash

    So convert everything to the normalized form and reject invalid values?

  11. flow

    I'd assume rejecting happens in the validation step

  12. Zash

    We occationally have users who REALLY want their UserName case to be preserved. :)

  13. flow

    I'm sure you do

  14. flow

    hmm it appears in PRECIS, validatation and enforcement are in the same step "enforcement"

  15. flow

    qrpnxz, I am sure you checked the RFC's errata for additional information regarding domainpart validation, right? :)

  16. qrpnxz

    i have not finished reading the spec even :) Thanks for heads up tho

  17. qrpnxz

    enforcement seems to be about taking an almost valid jid and doing some transformations on it so that it's actually conformant

  18. qrpnxz

    enforcement seems to be about taking an almost valid jid (say from user input) and doing some transformations on it so that it's actually conformant

  19. qrpnxz

    yeah i'm pretty sure about this see RFC 5895

  20. flow

    qrpnxz, what about ipv6 addresses in the domainpart? maybe there are code points that IDNA disallows that are valid in an IPv6 address?

  21. qrpnxz

    IDNA is not relevant to IP addresses, only if you detect that it must be a domain name do you start worrying about that

  22. qrpnxz

    flow,

  23. flow

    right, but you should not allow arbitrary strings if it is not a DNS name

  24. flow

    and, how do you detect that is must be a DNS name?

  25. qrpnxz

    if it starts with a number it has to be ipv4, if it starts with a '[' it better be ipv6, otherwise i start trying to parse a domain name

  26. flow

    DNS labels can start with digits, so that's not sound

  27. qrpnxz

    LDH cannot start with digits

  28. qrpnxz

    U-labels maaaaybe. And maybe when i find time to care i change the code to try domain name even when it starts with a digit. That would not be hard.

  29. qrpnxz

    yeah no it can't lol

  30. qrpnxz

    it gets caught in the bidi rule

  31. Zash

    > LDH cannot start with digits source?

  32. qrpnxz

    sure one sec

  33. qrpnxz

    https://datatracker.ietf.org/doc/html/rfc1034#section-3.5

  34. qrpnxz

    they also cannot start or end with hyphen

  35. Zash

    https://datatracker.ietf.org/doc/html/rfc5890 didn't say so, only the hypen bit

  36. Kev

    I thought that was relaxed in a later RFC.

  37. qrpnxz

    yeah 5890 defers to 1034 on a lot of details

  38. Kev

    (Starting with a number, not the hyphen)

  39. Kev

    But I don’t have this swapped in.

  40. Kev

    1123 maybe? I don’t have time to read it to check.

  41. Kev

    Blah. I got sucked in

  42. Kev

    2.1 Host Names and Numbers The syntax of a legal Internet host name was specified in RFC-952 [DNS:4]. One aspect of host name syntax is hereby changed: the restriction on the first character is relaxed to allow either a letter or a digit. Host software MUST support this more liberal syntax.

  43. qrpnxz

    hmm, nice find. Problem is that it breaks the bidi rule

  44. qrpnxz

    Kev, which are you quoting from

  45. Kev

    1123

  46. qrpnxz

    wait, but this is for host names, is that really the same as a domain name?

  47. Kev

    Down this path madness lies. Don’t say you haven’t been warned :D

  48. qrpnxz

    also, a host here can be an ip or a domain name, so ofc a host name should be able to start with a number, but this is not necessarily the case for a domain name

  49. qrpnxz

    yeah i'm certain this is what that's for

  50. flow

    it's confusing, isn't it? rfc5890 even explicitly says that LDH label rules are modified by rfc1123

  51. Kev

    > yeah i'm certain this is what that's for Honestly, if you’re still at the point of being certain about anything you’ve not spent long enough looking at name stuffs :D

  52. flow

    I tend to lean towards rfc1123 § 2.1 talking about "DNS labels" when "host name syntax"

  53. flow

    the problem is, besides what Kev mentioned, terminology

  54. qrpnxz

    Kev, correction: I'm certain this is how i'm going to interpret it xD.

  55. flow

    "domain name", "host name", are not well defined terms

  56. flow

    "DNS name", "DNS label" are

  57. Kev

    Actually, domain name and host name both *are* well defined, I think. The former in 1034 and the latter in 1123. It’s just that … yeah.

  58. qrpnxz

    even the JID standard just tells you about RFC5890 in an informational note. The actual requirement is that it be a FQDN, which the standard also admits as not well defined lol

  59. Kev

    It’s defined what format they have, but not what the *are* :)

  60. Kev

    It’s defined what format they have, but not what they *are* :)

  61. flow

    Kev, not sure if this is the case for "domain name", rfc1034 even admits "The terms "domain" or "domain name" are used in many contexts beyond the DNS described here."

  62. Kev

    Fair.

  63. flow

    where "DNS name" is unambiguous

  64. Kev

    But frequently unhelpful!

  65. flow

    of course, you could argue that it is well defined to be not well defined

  66. qrpnxz

    xd

  67. flow

    qrpnxz, would you mind elaborating on the bidi rule thingy you mentioned?

  68. qrpnxz

    yeah so for full unicode labels there's all kinds of rules for what code points are allowed, and one of them has to do with the directionality of the text (left-to-right, right-to-left). A label is only valid if it passes this test. Link: https://datatracker.ietf.org/doc/html/rfc5893#section-2

  69. flow

    and having a digit at first position causes issues with the bidi rule because?

  70. flow

    (note that I may have misunderstood you)

  71. qrpnxz

    well it violates condition one, for starters

  72. flow

    right

  73. flow

    so you can't have a U-label starting with a digit

  74. flow

    but you can have a A-label

  75. flow

    so 1soccer.us would be fine as DNS name and as XMPP domainpart

  76. flow

    but 1fußball.de would not be fine as DNS name (but I believe it would be fine as XMPP domainpart)

  77. flow

    then again, a XMPP domainpart that does not may well to a DNS name is mostly useless

  78. flow

    then again, a XMPP domainpart that does not map well to a DNS name is mostly useless

  79. qrpnxz

    A-labels start with xn-- remember :)

  80. flow

    no

  81. qrpnxz

    yes

  82. flow

    no

  83. qrpnxz

    this is just fact sorry

  84. qrpnxz

    quote "This means, by definition, that every A-label will begin with the IDNA ACE prefix, "xn--""

  85. flow

    got me, was confusing A with LDH labels

  86. qrpnxz

    and LDH cannot start with number for sure

  87. flow

    and that's because?

  88. qrpnxz

    https://datatracker.ietf.org/doc/html/rfc1034#section-3.5

  89. qrpnxz

    because that's how it's defined

  90. flow

    but everything is an LDH label, so that relaxation from rfc1123 would apply there too

  91. flow

    but everything is a LDH label, so that relaxation from rfc1123 would apply there too

  92. qrpnxz

    i'm really certain that that quote from 1123 is for host names, which it says were previously defined in rfc 952 (totally different document)

  93. flow

    but why would rfc5890 then refer to rfc1123?

  94. flow

    also rfc1123 talks about DNS' "trailing dot"

  95. flow

    but yes, I can definelty see your point too

  96. flow

    but yes, I can definetly see your point too

  97. Kev

    https://datatracker.ietf.org/doc/html/rfc3696#section-2 add any light here? :)

  98. flow

    moar rfcs!!!!

  99. qrpnxz

    i refered to 1123 because you brought it up lol

  100. qrpnxz

    but 5890 refers to 1034 on what a valid LDH label is

  101. flow

    Kev, I think it does, and I am pretty sure I've read all that ages ago

  102. flow

    the second paragaph only mentions the hypen rule, nothing about disallowing a digit in the first position

  103. qrpnxz

    my god everything is mislinked but i found something one sec

  104. qrpnxz

    "a segment of a host domain name is now allowed to begin with a digit and could legally be entirely numeric (see Section 6.1.2.4). However, a valid host name can never have the dotted-decimal form #.#.#.#, since at least the highest-level component label will be alphabetic" this is from 1123, twas hidden later on in the text. (Section 6.1.2.4 is totally completely unrelated btw) So the answer here seems to be then to only apply the bidi rule if there are any RTL characters. (I'll have to check if there was a correction of the rule.)

  105. qrpnxz

    "a segment of a host domain name is now allowed to begin with a digit and could legally be entirely numeric (see Section 6.1.2.4). However, a valid host name can never have the dotted-decimal form #.#.#.#, since at least the highest-level component label will be alphabetic" this is from 1123 section 2.1, twas hidden later on in the text. (Section 6.1.2.4 is totally completely unrelated btw) So the answer here seems to be then to only apply the bidi rule if there are any RTL characters. (I'll have to check if there was a correction of the rule.)

  106. qrpnxz

    this i think is better evidence that it also applies to domain names in general

  107. Kev

    > Honestly, if you’re still at the point of being certain about anything you’ve not spent long enough looking at name stuffs :D I’ll just leave this here :)

  108. qrpnxz

    real world proof of number domain name https://37signals.com/

  109. qrpnxz

    will get back to you guys on the bidi thing

  110. Kev

    Oh, I could have come up with exxamples if asked :)

  111. qrpnxz

    bruh lmao

  112. Kev

    123-reg is the most obvious one I think.

  113. qrpnxz

    you bastard, anyway, i guess for bidi it's like i said, only applies if there's an RTL somewhere in the whole domain name

  114. Kev

    I thought I started off by saying it was allowed ;)

  115. qrpnxz

    i mean idk why i didn't even try, clearly there's 4chan and 2ch

  116. qrpnxz

    hahaha

  117. flow

    qrpnxz, that bidi thing only applies to U-labels, no?

  118. flow

    so you could have a plain old LDH label with a digit at first position, but not a U-label

  119. qrpnxz

    domain names with RTL characters, it says

  120. qrpnxz

    a U-label could have it if no other part of the domain had an RTL char

  121. flow

    isn't that all something scoped within the context of IDNA / U-labels?

  122. qrpnxz

    necessarily the label with the RTL char would be a U-label if that's what you are talking about, but the bidi std says that the rule applies to all labels in a domain with any RTL chars

  123. flow

    that's now what I remember, expect or have read, but then again, it's big area

  124. qrpnxz

    sorry, to be more accurate, that contains a char with bidi class of R, AL, or AN

  125. flow

    IIRC the bidi rules only applies to U-labels

  126. flow

    and I'd argue that todays DNS is not all U-labels (but could be wrong)

  127. qrpnxz

    it says "The following rule, consisting of six conditions, applies to labels in Bidi domain names." Which are domains with at least one RTL label. Which are labels that contains at least one char with bidi class R, AL, or AN

  128. flow

    it being?

  129. flow

    anyhow, isn't foobar in foobar.com an example of a non RTL label?

  130. flow

    (hmm what is bidi class AL…)

  131. qrpnxz

    AL is arabic letters, AN is arabic numbers

  132. qrpnxz

    R is most letters is non-arabic RTL scripts

  133. qrpnxz

    foobar.com is not a bidi domain name

  134. flow

    that's what I am saying

  135. qrpnxz

    neither foobar nor com are RTL labels

  136. flow

    so the bidi rule does not apply here

  137. qrpnxz

    correct

  138. flow

    which means I can have 9foobar.com

  139. qrpnxz

    correct

  140. flow

    ahh, now I understand what you said: not only does the bidi rule not apply if it isn't a U-label, but I can have a U-label without codepoints that would require the bidi rule

  141. qrpnxz

    yes :)

  142. qrpnxz

    9fóobar.com is also fair game

  143. flow

    <qrpnxz>  it gets caught in the bidi rule made me believe that you thought that the bidi rule would disallow a digit in the first place in very U-label

  144. qrpnxz

    like i said, it applies if it's a bidi domain, which means it has at least one RTL label, which has at least one type R AL or AN char

  145. qrpnxz

    which 9fóobar.com does not have

  146. flow

    <qrpnxz>  it gets caught in the bidi rule made me believe that you thought that the bidi rule would disallow a digit in the first place in every U-label

  147. qrpnxz

    turns out no

  148. eevvoor

    https://ru.wikipedia.org/wiki/XMPP_Standards_Foundation

  149. eevvoor

    Amazing, such a long russian wikipedia article about the xsf.

  150. eevvoor

    😲️

  151. Ge0rG

    Jabber is big in Russia

  152. edhelas

    That's why we have millions of $ of funding from the Kremlin to add security issues in the protocol

  153. eevvoor

    🤦‍♂️️

  154. croax

    Unlucky they sent it to the wrong BTC address.

  155. eevvoor

    Perhaps we should change policy to accept rubels also.

  156. dwd

    It's a little out of date. It says Кевин Смит is still on Council.

  157. eevvoor

    It is amazing that they care about the names.

  158. eevvoor

    Who the hell finds it interesting to have a membership list on wikipedia?

  159. Kev

    dwd: And I always will be in spirit :)

  160. rion

    Kremlin didn't come to me yet =) but FSB (ФСБ/FSS) did.

  161. Ge0rG

    The German Federal Cartel Office is doing an investigation of chat services, and they would like to inquire the operators of "Jabber", in German, via snail mail. Can Board empower somebody to respond on behalf of the XSF? I'd volunteer, unless Daniel wants to step in.

  162. Ge0rG

    https://www.bundeskartellamt.de/SharedDocs/Meldung/DE/Pressemitteilungen/2020/12_11_2020_SU_Messenger_Dienste.html

  163. flow

    Is board the right entity given that board does not represent a chat service?

  164. flow

    That said, the XSF should try to be present in this discussion

  165. flow

    but clarify that there is a difference between "chat service" and "chat protocol". Maybe on the example of email

  166. flow

    "distributed open-standard chat procol" that is

  167. Ge0rG

    flow: I'd take care of that

  168. flow

    I'd expect nothing less :)

  169. flow

    so some XSF representative *and* another represenstative from a XMPP-based "chat service" would be ideal

  170. flow

    hence why not appoint Ge0rG, and send daniel?

  171. flow

    (given that he wants to)

  172. jonas’

    what do you mean by that?

  173. eevvoor

    why not write it and share it here?

  174. eevvoor

    before "submission"

  175. flow

    eevvoor, I don't think anyone would mind that. but first board has to decide/delegate

  176. Daniel

    flow: a few people in the xmpp verse have been requested to participate on their own behalf

  177. Daniel

    Meaning there is probably already some diversity in it

  178. flow

    Daniel, ahh, ok, that sound good then

  179. flow

    Daniel, ahh, ok, that sounds good then

  180. Ge0rG

    I know of inquiries to Jitsi and BBB

  181. eevvoor

    weird

  182. Daniel

    I wouldn't make too much of a big deal out of it. Just have Ge0rG do it if he wants to

  183. qrpnxz

    argh i accidentally cleared this chat as i was reading the juicy part

  184. jonas’

    qrpnxz, https://logs.xmpp.org/xsf/2021-05-20

  185. qrpnxz

    wow life saver

  186. dwd

    We've a Board meeting this evening, so we can rubber-stamp Georg if that works?

  187. qrpnxz

    > and another represenstative from a XMPP-based "chat service" would be ideal how about a random self-hoster xDDDDD

  188. Ge0rG

    dwd: that would be great, but please be gentle with the rubber-stamp

  189. jonas’

    yeah, a silicone stamp is more body-friendly

  190. qrpnxz

    do you know why the "German Federal Cartel Office" is doing a chat service investigation?

  191. Ge0rG

    does the ink contain lead?

  192. qrpnxz

    Investigation of what?

  193. dwd

    Branding? Tatooing?

  194. Ge0rG

    qrpnxz: I've linked their press release above, maybe some google translate might help

  195. dwd

    Ge0rG, Is tha "Cartel Office" the equivalent of the Monopolies and Mergers authority?

  196. qrpnxz

    Ge0rG, actually there's an en version https://www.bundeskartellamt.de/SharedDocs/Meldung/EN/Pressemitteilungen/2020/12_11_2020_SU_Messenger_Services.html;jsessionid=29F37418ED730DE76B91478F56EDD02E.2_cid387?nn=3591568

  197. qrpnxz

    Ge0rG, actually there's an en version https://www.bundeskartellamt.de/SharedDocs/Meldung/EN/Pressemitteilungen/2020/12_11_2020_SU_Messenger_Services.html

  198. Ge0rG

    qrpnxz: it's probably rooted in the monopolies of Facebook and such, and they want to see how to ensure interop. This has been going on for a year or two now

  199. Ge0rG

    qrpnxz: cool

  200. qrpnxz

    looks like they are investigating user data protections

  201. qrpnxz

    > Furthermore, in most cases it is not possible for users to communicate with each other by using different messenger services. GO XMPP

  202. Ge0rG

    dwd: I can't possibly answer that without knowing what the latter is about, and it looks like the M&M was replaced at least twice since.

  203. jonas’

    the name *does* sound like it could match the kartellamt tho

  204. qrpnxz

    btw, wikipedia: " Federal Cartel Office (German: Bundeskartellamt) is Germany's national competition regulator." So "Monopolies Authority" sounds about right.

  205. moparisthebest

    Mexico's Federal Cartel Office is quite different

  206. qrpnxz

    i think it's https://www.cofece.mx

  207. edhelas

    covfefe

  208. arc

    It is about that time again

  209. MattJ

    That comes quick

  210. arc

    Yeah weekly meetings do that

  211. ralphm bangs gavel

  212. ralphm

    0. Welcome

  213. ralphm

    Hi!

  214. ralphm

    Who do we have today?

  215. dwd waves

  216. MattJ

    o/

  217. ralphm

    Any point for our agenda?

  218. arc

    Here

  219. dwd

    Yes, the Ge0rG / German Cartel thing mentioned earlier today.

  220. Ge0rG

    dwd wanted to rubber-stamp me.

  221. ralphm

    Missed that, but ok.

  222. ralphm

    1. Minute taker

  223. arc

    I took meeting minutes last 2 weeks

  224. ralphm

    Yes. I think that's dwd now

  225. dwd

    OK

  226. ralphm

    2. "rubber-stamping Ge0rG"

  227. dwd

    Ge0rG, Want to explain?

  228. Ge0rG

    Sure!

  229. Ge0rG

    The Federal Cartel Office of Germany (Bundeskartellamt) is inquiring different IM providers about interoperability and similar topics.

  230. Ge0rG

    They have also approached the person behind freie-messenger.de about a contact for "Jabber" in the context of chat and video calls.

  231. Ge0rG

    I suppose that they mean XMPP and not the Cisco product, and I think somebody from the XSF should step in to participate in their questionnaire.

  232. Ge0rG

    I would step up to do so on behalf of the XSF

  233. Ge0rG

    They require an address in Germany and some hopefully small time effort.

  234. dwd

    So, I think this is a fine idea, and if Ge0rG is happy to do it that's great. I think Board should be sanctioning "speaking on behalf of the XSF", but in this case I feel it's a formality.

  235. Ge0rG

    So I would like to get rubber-stamped by the XSF Board as the Official Ambassador Of XMPP For The German Government.

  236. ralphm

    heh

  237. MattJ

    Sounds good to me

  238. ralphm

    I think we've previously used the word liason, but in general I'd be happy to have Ge0rG be the in-between.

  239. dwd

    I think it should be "The XMPP Ambassador to the Federal German Republic", technically, but whatever.

  240. dwd

    (For the avoidance of doubt, I am joking).

  241. ralphm

    Or rather "The XSF Ambassador...", as I've read people be sensitive about this even yesterday.

  242. Ge0rG

    dwd: I was just going to ask for a diplomatic passport.

  243. ralphm

    I take dwd's thinking as a motion.

  244. ralphm

    +1

  245. dwd

    +1

  246. ralphm dreads how this ends up in the minutes.

  247. MattJ

    h+1

  248. ralphm

    arc?

  249. Ge0rG

    dwd: technically it would be the "Federal Republic of Germany".

  250. arc

    +1

  251. Ge0rG

    Thank you very much, I'm honored to represent the XSF in #Neuland.

  252. arc

    Ok so who's making him the officially xmpp loferl socken?

  253. ralphm

    Motion carries. Congrats!

  254. Ge0rG

    For the minutes, you can link the slowly loading page at https://www.bundeskartellamt.de/SharedDocs/Meldung/EN/Pressemitteilungen/2020/12_11_2020_SU_Messenger_Services.html

  255. ralphm

    arc: I believe you just volunteered

  256. arc

    Yay!

  257. ralphm

    3. Open Collective

  258. ralphm

    From what I've seen Peter was dedicating an hour on this earlier this month. I haven't seen an update, yet.

  259. ralphm

    Sam pinged earlier today.

  260. ralphm

    4. AOB

  261. ralphm

    ?

  262. arc

    Not this week

  263. ralphm

    arc: but you have one for next week?

  264. ralphm

    I'll wait in anticipation.

  265. arc

    Maybe. We'll have to see

  266. ralphm

    5. Data of Next

  267. ralphm

    +1W

  268. ralphm

    6. Close

  269. ralphm

    Thanks all!

  270. ralphm bangs gavel

  271. arc

    Ge0rG: medium shoe and calf size? 😏

  272. ralphm

    Is that the new ASL?

  273. arc

    For the Loferl Socken!

  274. MattJ

    Thanks all

  275. ralphm

    arc: sure

  276. Ge0rG

    As long as I'm not supposed to wear a Dirndl.

  277. dwd

    Just a hoodie.

  278. ralphm

    _just_ a hoodie?

  279. arc

    No it would be great to get you in a photo wearing xmpp socks and the leather pants

  280. dwd

    arc, Now you remind me I need to work on that CoC...

  281. arc

    But seriously just yesterday I was talking to a friend about loferl socken to be worn under rugby socks because they look super warm, and as long as they are less than 5mm thick they would not violate any rules.

  282. arc

    I have known a few people that have worn foam shin pads under their socks. But yeah anyways I was downloading knit patterns to make them

  283. dwd

    Minutes send.

  284. dwd

    Minutes sent.

  285. ralphm

    Isn't the warmth simply because their 100% wool and roughly knit?

  286. ralphm

    Isn't the warmth simply because they're 100% wool and roughly knit?

  287. arc

    And they are literally anything around the calves. Rugby socks are typically knee-high but also typically thin so they are not all that warm

  288. arc

    I have played in the snow. So I can testify that they are not that warm. As can all of the bonfires with players huddled around them

  289. dwd

    I seem to recall that was just considered character building.

  290. ralphm

    So basically you need some kind of Merino over-the-calf socks

  291. arc

    In my experience is not very. When we were playing in Manchester England it was pissing rain at around 2c out, and windy, and I had a miserable weekend

  292. dwd

    Or, you know, just not play rugby when it's cold.

  293. arc

    ralphm: that's what Loferl Socken is

  294. ralphm

    arc: note that Merino

  295. arc

    That's a brand, isn't it?

  296. dwd

    Also, Manchester, 2°C and heavy rain - so July or August? The rest of the year it's windy, too...

  297. Ge0rG

    arc: let me know when you have my XMPP branded Loferl ready, and I will arrange for a photo in leather pants.

  298. ralphm

    It is a breed of sheep with certain wool quality, and you now often see it used as a type-of-wool. Often thin but warm.

  299. ralphm

    Might make it easier to search

  300. ralphm

    dwd: if people wouldn't play rugby when it's cold, how did it ever take off in England?

  301. dwd

    ralphm, I spent much of my childhood asking the same question.

  302. mathieui

    dwd, those are fast minutes!

  303. ralphm

    haha

  304. dwd

    ralphm, Usually while being forced into playing Rugby.

  305. Kev

    <Arc> the XSF is too European. <also Arc> I demand our liason wears loferl socken.

  306. Kev

    :D

  307. ralphm

    *boom*

  308. Ge0rG

    Is xmpp.org especially slow tonight?

  309. moparisthebest

    seems fine to me

  310. moparisthebest

    https://xmpp.org/software/libraries.html has "project name: txmpp, languages: linux" ? it's neither a library nor is it written in a programming language named linux...

  311. mathieui

    moparisthebest, we went through this already, I think someone needs to put the work in adding a new page for "tools" or whatever

  312. mathieui

    (which txmpp is)

  313. moparisthebest

    it looks like a sendxmpp that relies on libstrophe from the link

  314. moparisthebest

    looks like it's already on this "tools" page https://wiki.xmpp.org/web/User:MDosch/Sendxmpp_incarnations

  315. jubalh

    this one seems more like the library: https://github.com/rpavlik/txmpp

  316. moparisthebest

    interesting, seems abandoned though

  317. Ge0rG

    The language would be "Unix shell"

  318. moparisthebest

    the one on libraries.html is actually written in C

  319. moparisthebest

    "Linux" makes no sense regardless

  320. moparisthebest

    what in the world https://github.com/rpavlik/txmpp/blob/master/src/Equifax_Secure_Global_eBusiness_CA-1.h

  321. roro

    Applogies for the random message. I was told that I should ask this here to get a precise answer. I am looking for fundamental differences between XMPP and MATRIX. I'm sure quite a bit has been written already. If you have an exhaustive link to point me, that would be great.

  322. roro

    If you just have some bullets for me...I'll take it 🙂

  323. moparisthebest

    there are a lot of major differences, I can list a couple: 1. XMPP is an established standard with RFCs that has passed the test of time, Matrix is a... VC funded project? 2. XMPP is a message passing protocol, Matrix is some... eventually consistent graph thing? This is why matrix servers take insane amounts of resources

  324. Zash

    eventually consistent globally replicated JSON graph database

  325. roro

    > eventually consistent globally replicated JSON graph database Don't know if it's just me, sounds complicated.

  326. moparisthebest

    roro, also XMPP is XML over TLS, Matrix is JSON over HTTPS, that's more on the level of implementation detail that doesn't matter though

  327. emus

    dwd, ralphm arc I also offered Ge0rG help if I can do something. And I also followed the process so far. And some other members here too.

  328. emus

    > jubalh escribió: > this one seems more like the library: https://github.com/rpavlik/txmpp We allocated this to Libaries/Tools on the website I thinl

  329. emus

    https://xmpp.org/software/libraries.html