XSF Discussion - 2022-01-03


  1. mjk has left

  2. վարյա has joined

  3. wladmis has joined

  4. adiaholic has joined

  5. Mikaela has left

  6. tykayn has left

  7. adiaholic has left

  8. lskdjf has left

  9. raghavgururajan has joined

  10. kurisumakise has left

  11. nuron has left

  12. wladmis has left

  13. nuron has joined

  14. sonny has left

  15. sonny has joined

  16. debacle has left

  17. norkki has left

  18. norkki has joined

  19. karoshi has left

  20. kurisumakise has joined

  21. վարյա has left

  22. վարյա has joined

  23. sonny has left

  24. norkki has left

  25. norkki has joined

  26. karoshi has joined

  27. kurisumakise has left

  28. arne has left

  29. kurisumakise has joined

  30. adiaholic has joined

  31. arne has joined

  32. restive_monk has joined

  33. stp has left

  34. adiaholic has left

  35. adiaholic has joined

  36. karoshi has left

  37. վարյա has left

  38. emus has left

  39. adiaholic has left

  40. adiaholic has joined

  41. floretta has left

  42. marc0s has left

  43. marc0s has joined

  44. floretta has joined

  45. restive_monk has left

  46. djorz has left

  47. restive_monk has joined

  48. chronosx88 has left

  49. kurisumakise

    >This is about stopping XML libraries from _emitting_ anything that's outside our subset, no? Rather than the parsing being a problem. Yeah, those guys love doing things beyond what you want from them. I remember being shocked to find out that even though python has *four* xml libraries built in, every single one of them is vulnerable, and vulnerabilities differ between them. So Gajim for example can't use one of those. It even had to reconfigure expat somewhat IIRC. Now how often do you hear of a vulnerability in say json or bencode? Let alone those responsibilities being kept in a mainstream PL like they're part of functionality. <morning-rant> It's almost like xml just like java somehow inherently leads to overengineering. I recently learned that people have built several PL around xml alone, like xquery or xslt. What the actual hell? And more concretely take xmpp. Why come up with the *unique* format? They couldn't just use length prefixes even with that same xml for example, no they had to come up with a unique complicated xml-esque format you have to invent your own way of parsing. I mean I really want to believe they did have some different philosophy in mind. Maybe they intended for it to be parsed directly with SAX somehow? But that'd be no less complicated would it. Or take starttls. Why does it exist at all? Or srv ssl records. They couldn't just pick a standard ssl port like every other protocol does, of course, that's to simple for the xml mind. Or the mess that <message> generally is. When you receive it you have to work out if you're actually supposed to display it! I wonder what info at all that tag ends up conveying really. And then they come up with "message profiles", oh gosh... The XEP that especially shows is the "aesgcm" one. Where the guy pretty much says "screw this it's too complicated to add even a single xml tag" and he comes up with an adhoc markup format lmao. Other XEPs indicative of problems with XML are the various message text markup ones. XML is a freaking MARKUP language itslef yet people are so appalled by it they choose not to use it even in an XML based protocol. They either come up with their adhoc format, or that especially laughable XEP with " <span start="9" end="15"><emphasis/></span>". Like what the hell guys, what a perverted way with a markup language? This CANNOT be fully justified: either xml is problematic or the authors of the xep are (personally I think the former is the case) </morning-rant> >No, both sides are a problem. I remember an old (non XMPP, but similar issues) project where we ran into the <!proc exec cat /etc/passwd> or whatever it was issue. Turns out librarise out of the box were happy to do that, had no way to turn off all proc instances, and you had to know to turn it off. Exactly what I'm talking about. It's insane. Let alone it just doesn't belong in a *markup* language. Not that a markup language belongs as a data serialization language in the first place

  50. John has left

  51. adiaholic has left

  52. restive_monk has left

  53. Alex has left

  54. Sam

    Starttls exist for good reason, though I don't think it's useful these days. Back in the day though TLS and port numbers were expensive, so it was nice to be able to negotiate TLS over the same port you used for plain. SRV SSL records solve a real problem that other protocols that just pick a single port have too: sometimes even though there's a standard it's not on that port and you need service discovery.

  55. Sam

    Although I agree that starttls should just go away today and with basically everything about how XML has made things terribly complicated. The question is whether the tradeoff is worth it; eg. would it be *more* complicated to re-invent namespaces or some way of extending things in JSON where that's not just built in, for example.

  56. Sam

    I don't know what "message profiles" are though and have never really had any trouble figuring out if a message should be displayed, so I dunno about that one.

  57. jcbrand has left

  58. wurstsalat has left

  59. adiaholic has joined

  60. kurisumakise has left

  61. kurisumakise has joined

  62. restive_monk has joined

  63. kurisumakise

    > Although I agree that starttls should just go away today and with basically everything about how XML has made things terribly complicated. The question is whether the tradeoff is worth it; eg. would it be *more* complicated to re-invent namespaces or some way of extending things in JSON where that's not just built in, for example. That is implying that namespaces are a necessary thing in the first place and not a pointless complication.

  64. Steve Kille has left

  65. Steve Kille has joined

  66. Sam

    Yes, that is what I was implying, though I admit that I go back and forth on that. There may be better ways of extensibility.

  67. kurisumakise has left

  68. վարյա has joined

  69. kurisu has joined

  70. wgreenhouse has left

  71. jgart has joined

  72. stp has joined

  73. BASSGOD has left

  74. wgreenhouse has joined

  75. wgreenhouse has left

  76. adiaholic has left

  77. serge90 has left

  78. kurisu has left

  79. kurisu has joined

  80. adiaholic has joined

  81. serge90 has joined

  82. adiaholic has left

  83. վարյա has left

  84. adiaholic has joined

  85. neshtaxmpp has left

  86. neshtaxmpp has joined

  87. moparisthebest

    kurisumakise: json parsing is equally full of vulnerabilities, I mean the most popular way to parse it in JavaScript is just to eval it

  88. kurisu has left

  89. moparisthebest

    Turns out parsing untrusted input is hard

  90. wgreenhouse has joined

  91. kurisu has joined

  92. wgreenhouse has left

  93. chronosx88 has joined

  94. msavoritias has joined

  95. վարյա has joined

  96. kurisu

    Comparing "not braindead eval'ing input" to "discarding a good number of parsers because in them the vulns cannot be fixed, picking that one parser and *configuring* it so that it's not vulnerable, also you have to build the object model on top of that yourself or come up with some hack" isn't exactly fair is it

  97. arcxi has left

  98. arcxi has joined

  99. u70jfzo5eyeb468b9o has left

  100. u70jfzo5eyeb468b9o has joined

  101. BASSGOD has joined

  102. marc0s has left

  103. marc0s has joined

  104. alacer has left

  105. alacer has joined

  106. alacer has left

  107. վարյա has left

  108. wgreenhouse has joined

  109. վարյա has joined

  110. moparisthebest

    kurisu: what about "those who don't learn from history are doomed to repeat it" https://www.moparisthebest.com/images/jsonschema.jpg

  111. druthid has left

  112. druthid has joined

  113. wgreenhouse has left

  114. restive_monk has left

  115. wgreenhouse has joined

  116. jgart has left

  117. Seve has joined

  118. wgreenhouse has left

  119. atomicwatch has joined

  120. raghavgururajan has left

  121. restive_monk has joined

  122. wgreenhouse has joined

  123. floretta has left

  124. floretta has joined

  125. wgreenhouse has left

  126. andy has joined

  127. adiaholic has left

  128. adiaholic has joined

  129. atomicwatch has left

  130. pasdesushi has joined

  131. jcbrand has joined

  132. kurisu

    How many clients/servers actually end up verify xml schemas? Are those even available for most xeps? Also I can't see how they're useful anyway. Perhaps if you're coding in a low level or extremely verbose language like java, xml schemas can be more expressive than the language itself, but otherwise all verification can easily be done in the main programming language you are using along with processing.

  133. վարյա has left

  134. kurisu

    How many clients/servers actually end up verifying xml schemas? Are those even available for most xeps? Also I can't see how they're useful anyway. Perhaps if you're coding in a low level or extremely verbose language like java, xml schemas can be more expressive than the language itself, but otherwise all verification can easily be done in the main programming language you are using along with processing.

  135. adiaholic has left

  136. restive_monk has left

  137. restive_monk has joined

  138. adiaholic has joined

  139. վարյա has joined

  140. Tobias has joined

  141. harry837374884 has left

  142. harry837374884 has joined

  143. COM8 has joined

  144. COM8 has left

  145. COM8 has joined

  146. COM8 has left

  147. adiaholic has left

  148. adiaholic has joined

  149. adiaholic has left

  150. emus has joined

  151. adiaholic has joined

  152. wgreenhouse has joined

  153. adiaholic has left

  154. wgreenhouse has left

  155. վարյա has left

  156. վարյա has joined

  157. adiaholic has joined

  158. Yagiza has joined

  159. neshtaxmpp has left

  160. neshtaxmpp has joined

  161. adiaholic has left

  162. pasdesushi has left

  163. inky has left

  164. Alex has joined

  165. adiaholic has joined

  166. Alex has left

  167. wgreenhouse has joined

  168. Alex has joined

  169. Menel has joined

  170. wgreenhouse has left

  171. adiaholic has left

  172. adiaholic has joined

  173. Rodhicks has joined

  174. Rodhicks has left

  175. sonny has joined

  176. floretta has left

  177. floretta has joined

  178. kurisu has left

  179. sonny has left

  180. sonny has joined

  181. serge90 has left

  182. serge90 has joined

  183. kurisu has joined

  184. restive_monk has left

  185. վարյա has left

  186. վարյա has joined

  187. kyemxden has left

  188. kyemxden has joined

  189. adiaholic has left

  190. pasdesushi has joined

  191. alacer has joined

  192. alacer has left

  193. alacer has joined

  194. me4you has left

  195. restive_monk has joined

  196. adiaholic has joined

  197. kurisu has left

  198. millesimus has joined

  199. u70jfzo5eyeb468b9o has left

  200. Paganini has left

  201. u70jfzo5eyeb468b9o has joined

  202. me4you has joined

  203. sonny has left

  204. sonny has joined

  205. eab has left

  206. eab has joined

  207. tykayn has joined

  208. adiaholic has left

  209. jjrh has left

  210. jjrh has joined

  211. jjrh has left

  212. jjrh has joined

  213. adiaholic has joined

  214. lskdjf has joined

  215. kurisu has joined

  216. adiaholic has left

  217. COM8 has joined

  218. COM8 has left

  219. millesimus has left

  220. adiaholic has joined

  221. floretta has left

  222. Vaulor has left

  223. sonny has left

  224. sonny has joined

  225. lorddavidiii has left

  226. adiaholic has left

  227. Titi has joined

  228. Link Mauve

    kurisu, schemas are not just here for validation, they also tremendously help with understanding how the thing works. In xmpp-parsers I wrote the parsers often just from the schemas, and sometimes fixed the schemas alongside (when they didn’t match the text or the examples).

  229. Link Mauve

    And yes, schemas are available for most XEPs.

  230. Link Mauve

    I personally don’t mind XML, I don’t even see it most of the time, the parsers are doing the parsing for me, I only go down to the XML form when the parser throws an error.

  231. Link Mauve

    And usually it’s the fault of the sending entity.

  232. mjk has joined

  233. mjk has left

  234. mjk has joined

  235. adiaholic has joined

  236. millesimus has joined

  237. adiaholic has left

  238. moparisthebest has left

  239. kurisu has left

  240. kurisu has joined

  241. adiaholic has joined

  242. wgreenhouse has joined

  243. millesimus has left

  244. ti_gj06 has joined

  245. millesimus has joined

  246. kurisu has left

  247. wgreenhouse has left

  248. intosi has joined

  249. moparisthebest has joined

  250. Steve Kille has left

  251. Steve Kille has joined

  252. floretta has joined

  253. adiaholic has left

  254. adiaholic has joined

  255. COM8 has joined

  256. Wojtek has joined

  257. COM8 has left

  258. millesimus has left

  259. restive_monk has left

  260. kurisu has joined

  261. flow

    kurisu, you got my attention, do you have a pointer to a vuln in an xml parser that can be fixed?

  262. adiaholic has left

  263. wgreenhouse has joined

  264. Wojtek has left

  265. huhn has joined

  266. Nekit has left

  267. mjk has left

  268. mjk has joined

  269. wurstsalat has joined

  270. homebeach has left

  271. Matthew has left

  272. Rixon 👁🗨 has left

  273. uhoreg has left

  274. Half-Shot has left

  275. Half-Shot has joined

  276. Matthew has joined

  277. Rixon 👁🗨 has joined

  278. uhoreg has joined

  279. homebeach has joined

  280. Wojtek has joined

  281. emus has left

  282. wgreenhouse has left

  283. Wojtek has left

  284. Steve Kille has left

  285. Wojtek has joined

  286. wgreenhouse has joined

  287. eevvoor has left

  288. bung has joined

  289. adiaholic has joined

  290. bung has left

  291. kurisu has left

  292. wgreenhouse has left

  293. mjk

    > all verification can easily be done in the main programming language you are using along with processing You mean _languages_? In how many languages xmpp is implemented, again? If only there was a single language to describe formats and protocols...

  294. Nekit has joined

  295. karoshi has joined

  296. kurisu has joined

  297. alacer has left

  298. alacer has joined

  299. adiaholic has left

  300. goffi has joined

  301. eevvoor has joined

  302. mjk has left

  303. mjk has joined

  304. lorddavidiii has joined

  305. adiaholic has joined

  306. emus has joined

  307. harry837374884 has left

  308. harry837374884 has joined

  309. adiaholic has left

  310. ti_gj06 has left

  311. floretta has left

  312. jl4 has joined

  313. Steve Kille has joined

  314. eevvoor has left

  315. adiaholic has joined

  316. վարյա has left

  317. Wojtek has left

  318. Rixon 👁🗨 has left

  319. homebeach has left

  320. uhoreg has left

  321. Matthew has left

  322. Half-Shot has left

  323. Half-Shot has joined

  324. Matthew has joined

  325. Rixon 👁🗨 has joined

  326. uhoreg has joined

  327. homebeach has joined

  328. kurisu

    Link Mauve, >chemas are not just here for validation, they also tremendously help with understanding how the thing works. In xmpp-parsers I wrote the parsers often just from the schemas, is that the "crate parsing common XMPP elements into Rust structures."? Thing is with a more or less sane format like json you don't need to create any structures, you can just work with json "directly", it readily maps nicely into you PL's structures if it's high level enough. A package like that just wouldn't need to exist if xmpp used a sane format. > sometimes fixed the schemas alongside lmao they don't even get those right. See how needlessly compilcated this is? >I personally don’t mind XML, I don’t even see it most of the time, the parsers are doing the parsing for me, I only go down to the XML form when the parser throws an error. you literally just described how you had to write a parser flow, indulge: https://docs.python.org/3/library/xml.html#xml-vulnerabilities Also if there are any gajim devs here please confirm or deny this: some time ago I remember digging thru nbxmpp source and seeing they actually had to change expat's option so that it wouldn't retrieve DTDs. Not a vuln but just shows you how overcomplicated xml as a goddamn serialization format is if using a standard configuration would deanonymize you - if it can retrieve dtds it means expat carries networking code, which I'm pretty certain would not magically pick up your proxy options. Also just try and imagine how much code is in that parser if it can retrieve stuff from the internet. This is called bloat, and bloat leads to vulns. Also I think Sam here even mentioned an arbitrary code exectuion vuln he stubmled upon in some code he was working with. Now I'm not even sure if the devs of that xml lib used even considered this a vuln not a feature. mjk, what do you even mean by this poor attempt at satire? Precisely my point, in every language you have to reinvent the parser to some degree because it's xml and moreover nonstandard xml. Are you refering to schemas being a single language for validation as a convenience? Well, no one uses that. In most clients it isn't even possible because they reinvent DOM, because xmpp is nonstandard xml. So to validate schemas most would have to reinventing an xml schema parser and validator which would take so, so much more lines of code then just validating the xml in you language. Even then if some client manage through some hacks to use a standard xml library with a validator included, how many of those do you think choose to go for xml schema validation and not native language validation? Apparently next to none at all, given that Link Mauve here had to fix the schemas As always, the xml/java/bloat mindset makes an issue out of a non-issue (validation) and thinks it's come up with a tool to solve it, and the tool ends up orders of magnitude harder to create, and probably even harder to use, than the original approach.

  329. kurisu

    Link Mauve, >chemas are not just here for validation, they also tremendously help with understanding how the thing works. In xmpp-parsers I wrote the parsers often just from the schemas, is that the "crate parsing common XMPP elements into Rust structures."? Thing is with a more or less sane format like json you don't need to create any structures, you can just work with json "directly", it readily maps nicely into you PL's structures if it's high level enough. A package like that just wouldn't need to exist if xmpp used a sane format. > sometimes fixed the schemas alongside lmao they don't even get those right. See how needlessly compilcated this is? >I personally don’t mind XML, I don’t even see it most of the time, the parsers are doing the parsing for me, I only go down to the XML form when the parser throws an error. you literally just described how you had to write a parser flow, indulge: https://docs.python.org/3/library/xml.html#xml-vulnerabilities Also if there are any gajim devs here please confirm or deny this: some time ago I remember digging thru nbxmpp source and seeing they actually had to change expat's option so that it wouldn't retrieve DTDs. Not a vuln but just shows you how overcomplicated xml as a goddamn serialization format is if using a standard configuration would deanonymize you - if it can retrieve dtds it means expat carries networking code, which I'm pretty certain would not magically pick up your proxy options. Also just try and imagine how much code is in that parser if it can retrieve stuff from the internet. This is called bloat, and bloat leads to vulns. Also I think Sam here even mentioned an arbitrary code exectuion vuln he stubmled upon in some code he was working with. Now I'm not even sure if the devs of that xml lib used even considered this a vuln not a feature. mjk, what do you even mean by this poor attempt at satire? Precisely my point, in every language you have to reinvent the parser to some degree because it's xml and moreover nonstandard xml. Are you refering to schemas being a single language for validation as a convenience? Well, no one uses that. In most clients it isn't even possible because they reinvent DOM, because xmpp is nonstandard xml. So to validate schemas most would have to reinventing an xml schema parser and validator which would take so, so much more lines of code then just validating the xml in you language. Even then if some client manage through some hacks to use a standard xml library with a validator included, how many of those do you think choose to go for xml schema validation and not native language validation? Apparently next to none at all, given that Link Mauve here had to fix the schemas As always, the xml/java/bloat mindset makes an issue out of a non-issue (validation) and thinks it's come up with a tool to solve it, and the tool ends up orders of magnitude harder to create, and probably even harder to use, than the original approach. Not even speaking of flexibility

  330. eevvoor has joined

  331. floretta has joined

  332. flow

    that table seems to say that xml parsers in python are maybe vuln to attacks that are based on features that we dont' use in XMPP and only if an outdated expat version is used

  333. MattJ

    kurisu, in >20 years of XMPP you're not the first to complain about it using XML. You won't be the last. What are you hoping to achieve with this discussion, exactly?

  334. mjk

    > Are you refering to schemas being a single language for validation as a convenience? Yes. > Well, no one uses that. In most clients it isn't even possible because they reinvent DOM, because xmpp is nonstandard xml. I thought your argument was against xml schemas in general, I only used xmpp as an illustration of an xml format with wide cross-language implementation

  335. flow

    and disabling those features is trivial (at least for java), see https://github.com/igniterealtime/Smack/blob/5f75d141ff6d0494f0e548d549be25c04440fe24/smack-xmlparser-stax/src/main/java/org/jivesoftware/smack/xml/stax/StaxXmlPullParserFactory.java#L36-L40

  336. Mikaela has joined

  337. emus has left

  338. sonny has left

  339. sonny has joined

  340. sonny has left

  341. sonny has joined

  342. Link Mauve

    kurisu, no, JSON doesn’t “map nicely” to XMPP elements in any programming language, it is way too inexpressive for that.

  343. emus has joined

  344. kyemxden has left

  345. kyemxden has joined

  346. Link Mauve

    kurisu, no, I used a ready-made XML parser, and parsed that in domain-specific structs.

  347. Link Mauve

    Structs which are compile- and run-time checked for consistency, and which reject invalid states.

  348. mjk has left

  349. mjk has joined

  350. moparisthebest has left

  351. flow

    note that I'd also like if libraries would come with a secure default, I think at least some XML lib does, but I also believe there is a reason they don't (whether or not I agree with that reason is a different topic)

  352. Link Mauve

    This avoids having to carry DOM around btw, the structs being specific to XMPP are much more concise in memory.

  353. flow

    note that I'd also like if libraries would come with a secure default, I think at least some XML lib do, but I also believe there is a reason they don't (whether or not I agree with that reason is a different topic)

  354. flow

    yeah, smack does something similar

  355. moparisthebest has joined

  356. Link Mauve

    kurisu, also, you mention validators but in the wild it’s usually preferable to ignore unknown elements and extensions than to outright reject them.

  357. Link Mauve

    Unless you have specific needs.

  358. marc0s has left

  359. marc0s has joined

  360. flow

    right, usually validation means, validating known elements, but ignoring unknown ones. only if you have specific needs, typically in form of increasing security by avoiding information leakage, you want to reject or strip unknowns

  361. mjk

    Link Mauve: do I understand correctly that there are, effectively, xml-schema→programming-language compilers thst emit validation (and data conversion) code?

  362. marc0s has left

  363. mjk

    Link Mauve: do I understand correctly that there are, effectively, xml-schema→programming-language compilers that emit validation (and data conversion) code?

  364. marc0s has joined

  365. Link Mauve

    mjk, there probably are, although I never used one.

  366. Nekit has left

  367. mjk

    Ah

  368. Link Mauve

    I wrote xmpp-parsers to do this kind of validation, but using more domain-specific types than XML Schemas allow.

  369. mjk

    I see

  370. Wojtek has joined

  371. mjk

    So, you were the compiler :)

  372. Holger

    Sounds very similar to what ejabberd does.

  373. Link Mauve

    XML Schema lists what is allowed where, with some typing, but they don’t encode enough for me to generate the parsers and serialisers just from that.

  374. flow

    mjk, not sure about the data conversino part, but there are XML parsers that you can hand a schema which will cause them to report schema violations

  375. Link Mauve

    Yes, zinid and I had the same idea at roughly the same time. :)

  376. marc0s has left

  377. L29Ah has left

  378. marc0s has joined

  379. L29Ah has joined

  380. flow

    mjk, not sure about the data conversation part, but there are XML parsers that you can hand a schema which will cause them to report schema violations

  381. flow

    mjk, not sure about the data conversion part, but there are XML parsers that you can hand a schema which will cause them to report schema violations

  382. adiaholic has left

  383. kurisu

    MattJ: I also notice that in 20 years xmpp hasn't had many good clients developed for it. Even the major ones still are buggy. As much as I like the idea of a federated messenger, I'm starting to think there's some flaw inherent to the protocol that prevented it from taking off. I thought of trying to implement a client myself in my spare time. Well, it turns out the very serialization format is quite a stumbling block. So I thought maybe I'm just misunderstanding something, maybe e.g. I wasn't supposed to try and build a dom but e.g. work with sax events directly? More of curiousity at this point, as stated I'm just wondering what the original authors intended Link Mauve, >no, JSON doesn’t “map nicely” to XMPP elements in any programming language, it is way too inexpressive for that. You're being dishonest. XMPP is written in xml and you can't express xml more effeciently in json, true. However, the data conveyed by xmpp doesn't map nicely into xml in the first place. Take the list of mechanisms in stream:features. Not to mention how the xml format has no notion of a list. What does your library do with stream:features/mechanisms/mechanism/text()? Create whatever a list is called in rust? Well guess what, in a sane format like json it would already be a freaking list. Xml isn't to blame for not having a notion of a list, it's but a markup language afterall, not a data serialization one. It is however notable that even as a markup language it fails: xmpp doesn't use xml for markup like it was intended, it has to come up with an adhoc format in one xep and a laughable hack in another. So yes, unfortunately, because of the usage of xml you can't easily create a json version of xmpp. Because xml has its own object model of tree and nodes and attrs and whatnot on top of which actual structures like "a list of strings" have to be hacked on. This is in comparison to e.g. the torrent dht protocol: you could easily convert it to json or almost any other sane format because the initial format is sane. Because they don't use a markup language for data serialization. Because there are lists, dicts, strings ints and so on. Same goes for FCP, freenet's adhoc protocol. I've been developing something for freenet you see, and had to use said protocol, which didn't have a library for it in my language of choice. Well guess what it's been a freaking breeze to create my own parser. Funny how an adhoc,"afterthought" data serialization format is more pleasant to work with than xml >This avoids having to carry DOM around btw, the structs being specific to XMPP are much more concise in memory. Speaking of memory concise when speaking of xml.. ironic. >also, you mention validators but in the wild it’s usually preferable to ignore unknown elements and extensions than to outright reject them. and?

  384. jonas’

    kurisu, given that things like whatsapp are based on XMPP, it's certainly not a flaw inherent in the protocol preventing it to be used for something useful.

  385. jonas’

    it's just that nobody has made a business plan which supports the federated use case, so no moneys.

  386. kurisu

    jonas': whatsapp has unlimited budget and thus manpower. With enough thrust even a pig will fly.

  387. Ge0rG

    jonas’: well, that _is_ a flaw in the protocol, as viewed from the perspective of lock-in startups ;)

  388. mjk

    > there are XML parsers that you can hand a schema which will cause them to report schema violations That much I know. :) I was thinking more in the direction of compiling a single xml schema to byte- or machine code to produce a very efficient specialized validator/parser

  389. jonas’

    Ge0rG, federation is not mandated by the protocol

  390. Ge0rG

    jonas’: but client interop is

  391. flow

    I also think that relatively young clients like Conversations and Dino demonstrate that it is possible to implement XMPP from scratch

  392. Link Mauve

    kurisu, have a look at ActivityPub, I had the misfortune of digging into it, it’s JSON-LD all the way down.

  393. Link Mauve

    I’ll take XMPP’s XML any day over that abomination.

  394. Link Mauve

    You might like it better, maybe.

  395. Link Mauve

    It does pretty much the same as XMPP, provides authentication, message passing, pubsub, etc.

  396. edhelas is discovering JSON-LD https://www.w3.org/2018/json-ld-wg/

  397. Link Mauve

    Fun fact: there are no integers in JSON. ^^

  398. Link Mauve

    Only numbers, which are double floats.

  399. eevvoor has left

  400. marc0s has left

  401. marc0s has joined

  402. mjk

    That makes it a natural fit for a Prosody module!.. Wait, Lua has integers now

  403. John has joined

  404. marc0s has left

  405. marc0s has joined

  406. sonny has left

  407. restive_monk has joined

  408. sonny has joined

  409. me4you has left

  410. me4you has joined

  411. mathieui

    I don't know why we are having this discussion, apart from ranting it will solve nothing and enlighten exactly nobody. The points being made are laughable to me for the most part (the lack of modern clients is that the "legacy" clients were good enough, until they weren't, and mobile-first with awful OSes and lack of proper networking were a big hurdle, that has nothing to do with XML, we had a good markup solution using XML elements 20 years ago already but I won't go back to this debate). The one I will acknowledge is that it is slightly harder to bootstrap a client from nothing, and that is mostly because it requires quite a bit of RFC diving and domain knowledge. But comparing XMPP to FCP or the torrent DHT protocol is disingenuous at best, considering the specialised and narrow target of what they are set to achieve.

  412. Vaulor has joined

  413. edhelas

    +1

  414. mathieui

    I have never used XML outside of XMPP, except for configuring openbox or writing web stuff, but I have seen complex data types and schemas in JSON and YAML and it certainly is not an pleasant sight.

  415. L29Ah has left

  416. debacle has joined

  417. L29Ah has joined

  418. mathieui

    (I'm not saying I don't like rants or ranting, but maybe there are other rooms that can better accommodate it than this room where people expect productive discussion, because no, XMPP is not switching to bencode tomorrow)

  419. flow

    I am surely biased, but my impression is that the provided arguments against XMPP/XML are exaggerating the situation while additionaly describing it not precisely nor technically sound

  420. Holger

    And I don't buy the implication that there're obvious/simple alternatives. I.e. just avoid XML, reinvent everything from scratch and suddenly an extensible messaging spec becomes a simple, straightforward problem to solve, validation now is a non-issue and whatnot.

  421. Holger

    What I do buy is that JSON over HTTP does a much better job at on-boarding devs, being able to show a simple `curl` example for sending a message is a huge win.

  422. Daniel

    seemingly atomic operations are a plus too

  423. mjk

    Seemingly atomic or seemingly a plus? :)

  424. Daniel

    seemingly atomic

  425. adiaholic has joined

  426. Daniel

    because any complex http+json protocol will have some kind of discovery / feature negotiation

  427. wgreenhouse has joined

  428. mjk

    Yeah

  429. xecks has left

  430. xecks has joined

  431. wgreenhouse has left

  432. inky has joined

  433. millesimus has joined

  434. dwd

    I still say that if we described XMPP has having a "JSX-like wire protocol" we'd be fine.

  435. floretta has left

  436. kyemxden has left

  437. kyemxden has joined

  438. adiaholic has left

  439. dwd

    Anyway, the reality is that XMPP's biggest problems are that it's a connection-orientated protocol that connects clients. There's ways around both, but they require some effort to shift to a protocol that connects users with multiple clients. XML isn't really a problem, exce4pt that people perceive it to be one and get very hung up over it when they start.

  440. intosi has left

  441. intosi has joined

  442. dwd

    I think the XML problem is much less problematic than people think it is, but only because XMPP really doesn't use XML as much as it uses some serialization and namespacing from XML. And that's very hard to explain, when people see XML and assume we're built on SOAP.

  443. adiaholic has joined

  444. dwd

    The "connection-orientated" problem is another conceptual problem, but also has technical problems. Mobile phones and suchlike simply cannot hold a connection open - a flaw in their design, but one we need to deal with. I've tried addressing this with XEP-0198 and persisting sessions beyond TCP connections, and I think that works, especially given the increasing need to persist a lot of information about clients in use. But that's met with resistance and I'm out of energy.

  445. dwd

    Similarly, the clients versus users problem; we have a series of half-solutions in that space too, but again, no energy.

  446. dwd

    And, of course, we're dealing with Matrix, which has a nice set of shiny clients, and a marketing/sales team happy to distort the truth as much as they can, which is stealing away a lot of market share.

  447. adiaholic has left

  448. Daniel

    addressing both persistent connections AND clients v users is so overwhelming that it sometimes feels like we might as well start over

  449. lorddavidiii has left

  450. wgreenhouse has joined

  451. Rixon 👁🗨 has left

  452. homebeach has left

  453. uhoreg has left

  454. Matthew has left

  455. Half-Shot has left

  456. Half-Shot has joined

  457. Matthew has joined

  458. Rixon 👁🗨 has joined

  459. uhoreg has joined

  460. homebeach has joined

  461. lorddavidiii has joined

  462. lorddavidiii has left

  463. lorddavidiii has joined

  464. Wojtek has left

  465. lorddavidiii has left

  466. dwd

    Oh, note I didn't say "persistent connections", I said "connection-orientated". They're somewhat different.

  467. intosi has left

  468. kurisu has left

  469. lorddavidiii has joined

  470. neshtaxmpp has left

  471. neshtaxmpp has joined

  472. lorddavidiii has left

  473. dwd

    And clients v users feels achingly close to solved, some days. In fairness, it's easier to go in this direction than the other - a lot of effort on IMAP went on going from user to multiple clients, and it was *hard*.

  474. lorddavidiii has joined

  475. kurisu has joined

  476. lorddavidiii has left

  477. intosi has joined

  478. lorddavidiii has joined

  479. lorddavidiii has left

  480. lorddavidiii has joined

  481. lorddavidiii has left

  482. rafasaurus has left

  483. rafasaurus has joined

  484. lorddavidiii has joined

  485. lorddavidiii has left

  486. intosi has left

  487. lorddavidiii has joined

  488. COM8 has joined

  489. COM8 has left

  490. lorddavidiii has left

  491. floretta has joined

  492. intosi has joined

  493. lorddavidiii has joined

  494. lorddavidiii has left

  495. lorddavidiii has joined

  496. lorddavidiii has left

  497. dwd

    The other thing we could do - and I gave it some thought a while back - would be to define a server-side client and a standardized traditional HTTP API (whether graph or RESTish).

  498. lorddavidiii has joined

  499. lorddavidiii has left

  500. dwd

    That's somewhat akin to what Lloyd Watkin did a few years back, mind, but perhaps taking things a bit further.

  501. ti_gj06 has joined

  502. lorddavidiii has joined

  503. lorddavidiii has left

  504. lorddavidiii has joined

  505. lorddavidiii has left

  506. adiaholic has joined

  507. lorddavidiii has joined

  508. lorddavidiii has left

  509. lorddavidiii has joined

  510. lorddavidiii has left

  511. lorddavidiii has joined

  512. lorddavidiii has left

  513. intosi has left

  514. djorz has joined

  515. intosi has joined

  516. lorddavidiii has joined

  517. nyco has left

  518. lorddavidiii has left

  519. Link Mauve

    dwd, mod_rest in Prosody is already kind of like that I think.

  520. Link Mauve

    Minus the standardisation.

  521. lorddavidiii has joined

  522. lorddavidiii has left

  523. papatutuwawa has joined

  524. papatutuwawa has left

  525. papatutuwawa has joined

  526. lorddavidiii has joined

  527. lorddavidiii has left

  528. lorddavidiii has joined

  529. dan.caseley has left

  530. dan.caseley has joined

  531. adiaholic has left

  532. lorddavidiii has left

  533. Wojtek has joined

  534. lorddavidiii has joined

  535. lorddavidiii has left

  536. lorddavidiii has joined

  537. Titi has left

  538. tykayn has left

  539. pasdesushi has left

  540. lorddavidiii has left

  541. nyco has joined

  542. lorddavidiii has joined

  543. lorddavidiii has left

  544. tykayn has joined

  545. Titi has joined

  546. lorddavidiii has joined

  547. lorddavidiii has left

  548. lorddavidiii has joined

  549. jonas’

    huh

  550. lorddavidiii has left

  551. jonas’

    so

  552. jonas’

    there is that idea of tracking devices

  553. jonas’

    if we were to track devices and had device-specific tokens which are good for, say, a day or so.

  554. jonas’

    and which can be renewed via a proper connection with SASL

  555. jonas’

    and those token would, while valid, represent a session with smacks and push and whatnot and could be used with a mod_rest-ish interface

  556. pasdesushi has joined

  557. jonas’

    that would be like 95% of what's needed to resolve the connection-oriented stuff, right?

  558. jonas’

    and it doesn't seem that complex

  559. lorddavidiii has joined

  560. ti_gj06 has left

  561. jonas’

    I mean, tracking devices and per-device auth is a bit of work, but there are people interested in solving that anyway (I think Snikket is, even if only for proper multi-device onboarding and management)

  562. lorddavidiii has left

  563. lorddavidiii has joined

  564. lorddavidiii has left

  565. lorddavidiii has joined

  566. lorddavidiii has left

  567. floretta has left

  568. lorddavidiii has joined

  569. lorddavidiii has left

  570. lorddavidiii has joined

  571. lorddavidiii has left

  572. lorddavidiii has joined

  573. lorddavidiii has left

  574. chronosx88 has left

  575. chronosx88 has joined

  576. lorddavidiii has joined

  577. lorddavidiii has left

  578. Wojtek has left

  579. lorddavidiii has joined

  580. lorddavidiii has left

  581. lorddavidiii has joined

  582. lorddavidiii has left

  583. MattJ

    I definitely wouldn't say "if only for" - I think the server having no knowledge of a user's clients is one of the big things holding us back right now

  584. MattJ

    We do, sort of, have this knowledge already (XEP-0198, push registrations) but it's incomplete and fragmented

  585. intosi has left

  586. floretta has joined

  587. intosi has joined

  588. lorddavidiii has joined

  589. lorddavidiii has left

  590. bung has joined

  591. lorddavidiii has joined

  592. lorddavidiii has left

  593. lorddavidiii has joined

  594. restive_monk has left

  595. lorddavidiii has left

  596. lorddavidiii has joined

  597. lorddavidiii has left

  598. lorddavidiii has joined

  599. lorddavidiii has left

  600. lorddavidiii has joined

  601. lorddavidiii has left

  602. restive_monk has joined

  603. lorddavidiii has joined

  604. lorddavidiii has left

  605. lorddavidiii has joined

  606. lorddavidiii has left

  607. John

    CSS of the wiki pages does not look right on my phone using Chrome https://wiki.xmpp.org/web/Main_Page

  608. lorddavidiii has joined

  609. Wojtek has joined

  610. lorddavidiii has left

  611. lorddavidiii has joined

  612. lorddavidiii has left

  613. lorddavidiii has joined

  614. lorddavidiii has left

  615. intosi has left

  616. andrey.g has joined

  617. lorddavidiii has joined

  618. lorddavidiii has left

  619. intosi has joined

  620. lorddavidiii has joined

  621. lorddavidiii has left

  622. lorddavidiii has joined

  623. jl4 has left

  624. kurisu has left

  625. kurisu has joined

  626. adiaholic has joined

  627. intosi has left

  628. atomicwatch has joined

  629. intosi has joined

  630. lorddavidiii has left

  631. Wojtek has left

  632. lorddavidiii has joined

  633. lorddavidiii has left

  634. lorddavidiii has joined

  635. lorddavidiii has left

  636. marc0s has left

  637. marc0s has joined

  638. marc0s has left

  639. marc0s has joined

  640. kurisu has left

  641. intosi has left

  642. kurisu has joined

  643. Wojtek has joined

  644. intosi has joined

  645. dan.caseley has left

  646. x51 has joined

  647. nyco has left

  648. dan.caseley has joined

  649. nyco has joined

  650. John has left

  651. lorddavidiii has joined

  652. mjk has left

  653. mjk has joined

  654. nyco has left

  655. lorddavidiii has left

  656. lorddavidiii has joined

  657. lorddavidiii has left

  658. lorddavidiii has joined

  659. lorddavidiii has left

  660. papatutuwawa has left

  661. lorddavidiii has joined

  662. lorddavidiii has left

  663. adiaholic has left

  664. adiaholic has joined

  665. adiaholic has left

  666. neshtaxmpp has left

  667. neshtaxmpp has joined

  668. adiaholic has joined

  669. nyco has joined

  670. kurisu has left

  671. restive_monk has left

  672. kurisu has joined

  673. adiaholic has left

  674. lorddavidiii has joined

  675. lorddavidiii has left

  676. adiaholic has joined

  677. lorddavidiii has joined

  678. lorddavidiii has left

  679. John has joined

  680. lorddavidiii has joined

  681. kyemxden has left

  682. kyemxden has joined

  683. lorddavidiii has left

  684. lorddavidiii has joined

  685. lorddavidiii has left

  686. lorddavidiii has joined

  687. lorddavidiii has left

  688. restive_monk has joined

  689. andrey.g has left

  690. lorddavidiii has joined

  691. lorddavidiii has left

  692. lorddavidiii has joined

  693. lorddavidiii has left

  694. andrey.g has joined

  695. lorddavidiii has joined

  696. lorddavidiii has left

  697. lorddavidiii has joined

  698. lorddavidiii has left

  699. Vaulor has left

  700. COM8 has joined

  701. lorddavidiii has joined

  702. lorddavidiii has left

  703. COM8 has left

  704. COM8 has joined

  705. COM8 has left

  706. andrey.g has left

  707. adiaholic has left

  708. adiaholic has joined

  709. lorddavidiii has joined

  710. lorddavidiii has left

  711. lorddavidiii has joined

  712. lorddavidiii has left

  713. restive_monk has left

  714. lorddavidiii has joined

  715. lorddavidiii has left

  716. lorddavidiii has joined

  717. lorddavidiii has left

  718. lorddavidiii has joined

  719. lorddavidiii has left

  720. lorddavidiii has joined

  721. lorddavidiii has left

  722. lorddavidiii has joined

  723. lorddavidiii has left

  724. lorddavidiii has joined

  725. lorddavidiii has left

  726. Vaulor has joined

  727. lorddavidiii has joined

  728. lorddavidiii has left

  729. lorddavidiii has joined

  730. lorddavidiii has left

  731. kurisu

    dwd: > And, of course, we're dealing with Matrix, which has a nice set of shiny clients, and a marketing/sales team happy to distort the truth as much as they can, which is stealing away a lot of market share. Sales team? How do they make money?

  732. Sam

    kurisu: it's created by a VC funded company that sells consulting services and maintains the only usable clients

  733. lorddavidiii has joined

  734. Zash

    and hosting

  735. lorddavidiii has left

  736. lorddavidiii has joined

  737. lorddavidiii has left

  738. kurisu

    Sam: someone pays for matrix related consulting? What sort of consulting I wonder

  739. kurisu

    Anything similar seem happening with xmpp?

  740. andy has left

  741. lorddavidiii has joined

  742. lorddavidiii has left

  743. lorddavidiii has joined

  744. lorddavidiii has left

  745. Daniel

    > Anything similar seem happening with xmpp? That's how a good amount of the people working within the XSF make a living

  746. lorddavidiii has joined

  747. Daniel

    See https://xmpp.work/all-listings/ for example

  748. lorddavidiii has left

  749. lorddavidiii has joined

  750. neshtaxmpp has left

  751. neshtaxmpp has joined

  752. eab has left

  753. floretta has left

  754. Mikaela has left

  755. floretta has joined

  756. restive_monk has joined

  757. emus

    > Daniel escribió: > See https://xmpp.work/all-listings/ for example Btw reminder to everyone here to place make their entries as I plan to advertise sooner or later

  758. wgreenhouse has left

  759. jl4 has joined

  760. papatutuwawa has joined

  761. MattJ

    emus, Process One are missing, you may want to reach out to them directly

  762. emus

    yes ok thanks!

  763. emus

    any contact recommendations?

  764. arne has left

  765. arne has joined

  766. jl4 has left

  767. jl4 has joined

  768. pjn has left

  769. COM8 has joined

  770. COM8 has left

  771. pjn has joined

  772. reimar has joined

  773. jonas’

    emus: you could try the ejabberd muc

  774. arne has left

  775. Wojtek has left

  776. emus

    jonas’: oh surez totally forgot

  777. jl4 has left

  778. jl4 has joined

  779. arne has joined

  780. wgreenhouse has joined

  781. arne has left

  782. homebeach has left

  783. Rixon 👁🗨 has left

  784. uhoreg has left

  785. Matthew has left

  786. Half-Shot has left

  787. Half-Shot has joined

  788. Matthew has joined

  789. Rixon 👁🗨 has joined

  790. uhoreg has joined

  791. homebeach has joined

  792. arne has joined

  793. arne has left

  794. arne has joined

  795. kurisu has left

  796. kurisu has joined

  797. intosi has left

  798. intosi has joined

  799. Wojtek has joined

  800. Wojtek has left

  801. harry837374884 has left

  802. dwd

    kurisu, Lots of consulting, but also Element have a bunch of pay-for addons. Most of what Matrix is being used for is bridging, as far as I can see. But their Teams and WhatsApp bridges are not open source, but per-seat licensing.

  803. dwd

    Sam, You're wrong, of course. Matrix is maintained by a foundation which is entirely seperate from Element, and just happens to have the same staff, infrastructure, and accounts.

  804. Sam

    Heh, oh yes, silly me, how could I ever forget

  805. dwd

    In any case, I've been told by people that XMPP can't do picture messaging, for example. They've been told this by Matrix/Element sales staff. Of course, the Matrix bridge is curated carefully to prevent anything nice from working, so it appears this way, but...

  806. intosi has left

  807. intosi has joined

  808. rafasaurus has left

  809. moparisthebest

    Also matrix invented the concept of bridging, nothing else had this decades before

  810. rafasaurus has joined

  811. adiaholic has left

  812. wladmis has joined

  813. kurisu has left

  814. adiaholic has joined

  815. Wojtek has joined

  816. Ge0rG

    I feel severely insulted as the developer of the matrix client with the longest code history.

  817. adiaholic has left

  818. Shackleton has joined

  819. adiaholic has joined

  820. marc0s has left

  821. marc0s has joined

  822. nyco has left

  823. goffi has left

  824. intosi has left

  825. mjk has left

  826. neshtaxmpp has left

  827. Shackleton has left

  828. mjk has joined

  829. Paganini has joined

  830. me9 has joined

  831. neshtaxmpp has joined

  832. rocco has joined

  833. intosi has joined

  834. Wojtek has left

  835. neshtaxmpp has left

  836. neshtaxmpp has joined

  837. marc0s has left

  838. marc0s has joined

  839. Wojtek has joined

  840. John

    dwd: I'm in a MUC has bridge with Matrix and Discord, I can download files but can't open them. Is that intended?

  841. wladmis has left

  842. nyco has joined

  843. adiaholic has left

  844. neshtaxmpp has left

  845. neshtaxmpp has joined

  846. adiaholic has joined

  847. neshtaxmpp has left

  848. neshtaxmpp has joined

  849. intosi has left

  850. alex11 has left

  851. intosi has joined

  852. Mikaela has joined

  853. rocco has left

  854. wgreenhouse

    John: bridged by a bot, or using bifröst?

  855. harry837374884 has joined

  856. andy has joined

  857. wladmis has joined

  858. pjn has left

  859. rion has left

  860. neshtaxmpp has left

  861. neshtaxmpp has joined

  862. adiaholic has left

  863. adiaholic has joined

  864. marc0s has left

  865. marc0s has joined

  866. pjn has joined

  867. Wojtek has left

  868. Wojtek has joined

  869. wladmis has left

  870. intosi has left

  871. wladmis has joined

  872. goffi has joined

  873. John

    wgreenhouse: I'm not sure, I think bot, I can see the Matrix users as participants in the MUC, like in other transports

  874. intosi has joined

  875. jl4 has left

  876. Menel

    If you can download, and not open, its a problem of your OS isn't it?

  877. adiaholic has left

  878. papatutuwawa has left

  879. John

    Menel: I tried to download using Conversations. You can try https://matrix.andrzejszczepaniak.co.uk/_matrix/media/v1/download/t2bot.io/15c36c5778f007732c5b98139069f93a6a8e91f9

  880. adiaholic has joined

  881. Menel

    Fine opening in my webbrowser

  882. harry837374884 has left

  883. harry837374884 has joined

  884. Menel

    Conversations is delegating it to my webbrowser and is opening fine

  885. John

    Worked on my browser too

  886. adiaholic has left

  887. Neustradamus has joined

  888. wgreenhouse

    John: that doesn't show as a button, or "oob" stanza per xep-0067

  889. wgreenhouse

    which is the req. for conversations to opwn

  890. wgreenhouse

    which is the req. for conversations to open

  891. restive_monk has left

  892. John

    wgreenhouse: it shows as a button, maybe OOB

  893. intosi has left

  894. wgreenhouse

    if it shows as a button but Conversations won't open it, hook Conversations up to adb and maybe report a bug

  895. wgreenhouse

    sounds like the bridge is trying to oob but something goes wrong

  896. adiaholic has joined

  897. wgreenhouse

    ordinary bifrost rooms do have working picture attachments

  898. wgreenhouse

    when they work at all

  899. John

    I will update Conversations to make sure first

  900. Ge0rG

    Maranda has been doing some work on the bridge lately

  901. andy has left

  902. Daniel has left

  903. arcxi has left

  904. floretta has left

  905. floretta has joined

  906. intosi has joined

  907. adiaholic has left

  908. adiaholic has joined

  909. sonny has left

  910. sonny has joined

  911. adiaholic has left

  912. Daniel has joined

  913. rocco has joined

  914. huhn has left

  915. Maranda

    https://aria-net.org/_matrix/media/v1/download/aria-net.org/dDNSPVQaDKXIhSHgQKvIckvD

  916. Maranda[x] has joined

  917. Maranda

    🤔🤔

  918. adiaholic has joined

  919. John

    Maranda: I see the link as a plain text, no download button

  920. Maranda

    That depends on mime / size and C related configuration iirc

  921. intosi has left

  922. stpeter has joined

  923. stpeter has left

  924. Maranda

    I don't recall issues with the oob element in the stanza itself, but if that's the case just give me a poke and I'll fix what runs on aria-net.org at least

  925. wladmis has left

  926. wladmis has joined

  927. Zash

    No OOB there.

  928. Zash

    Presumably because of the module that stops you from posting pictures here.

  929. intosi has joined

  930. Maranda

    https://aria-net.org/_matrix/media/v1/download/aria-net.org/eTSToHRtaxBpIxLPcApGfbgl

  931. Maranda

    Indeed

  932. papatutuwawa has joined

  933. jl4 has joined

  934. rocco has left

  935. qy has left

  936. qy has joined

  937. Rixon 👁🗨 has left

  938. uhoreg has left

  939. homebeach has left

  940. Matthew has left

  941. Half-Shot has left

  942. Half-Shot has joined

  943. Matthew has joined

  944. Rixon 👁🗨 has joined

  945. uhoreg has joined

  946. homebeach has joined

  947. adiaholic has left

  948. Ge0rG

    That's a Premium member feature

  949. adiaholic has joined

  950. arcxi has joined

  951. adiaholic has left

  952. adiaholic has joined

  953. jl4 has left

  954. Wojtek has left

  955. Wojtek has joined

  956. restive_monk has joined

  957. papatutuwawa has left

  958. intosi has left

  959. adiaholic has left

  960. msavoritias

    Ge0rG: to be able to sent pictures? It is the bridge you are paying?

  961. ben has left

  962. Ge0rG

    msavoritias: posting pictures in this room is only allowed to members since The Incident. The "premium" part was just a bit of irony about membership being paid in most places (but not here)

  963. intosi has joined

  964. msavoritias

    Ah. Totally missed the joke on my part :p I just assumed it to be a matrix closed feature out of habit

  965. me9 has left

  966. huhn has joined

  967. harry837374884 has left

  968. restive_monk has left

  969. raghavgururajan has joined

  970. Wojtek has left

  971. intosi has left

  972. Wojtek has joined

  973. inky has left

  974. wladmis has left

  975. wladmis has joined

  976. adiaholic has joined

  977. wladmis has left

  978. intosi has joined

  979. jl4 has joined

  980. floretta has left

  981. John has left

  982. eab has joined

  983. inky has joined

  984. eab has left

  985. eab has joined

  986. jl4 has left

  987. jl4 has joined

  988. floretta has joined

  989. intosi has left

  990. adiaholic has left

  991. adiaholic has joined

  992. intosi has joined

  993. Yagiza has left

  994. Wojtek has left

  995. kyemxden has left

  996. kyemxden has joined

  997. kyemxden has left

  998. kyemxden has joined

  999. huhn has left

  1000. Mikaela has left

  1001. marc0s has left

  1002. marc0s has joined

  1003. stpeter has joined

  1004. stpeter has left

  1005. intosi has left

  1006. papatutuwawa has joined

  1007. adiaholic has left

  1008. jl4 has left

  1009. adiaholic has joined

  1010. sonny has left

  1011. sonny has joined

  1012. intosi has joined

  1013. jl4 has joined

  1014. BASSGOD has left

  1015. marc0s has left

  1016. marc0s has joined

  1017. BASSGOD has joined

  1018. adiaholic has left

  1019. me9 has joined

  1020. msavoritias has left

  1021. adiaholic has joined

  1022. jl4 has left

  1023. adiaholic has left

  1024. John has joined

  1025. John has left

  1026. John has joined

  1027. paul has left

  1028. intosi has left

  1029. Nekit has joined

  1030. intosi has joined

  1031. Titi has left

  1032. kyemxden has left

  1033. kyemxden has joined

  1034. rafasaurus has left

  1035. rafasaurus has joined

  1036. x51 has left

  1037. jl4 has joined

  1038. jl4 has left

  1039. intosi has left

  1040. kyemxden has left

  1041. kyemxden has joined

  1042. stpeter has joined

  1043. stpeter has left

  1044. millesimus has left

  1045. adiaholic has joined

  1046. paul has joined

  1047. stpeter has joined

  1048. stpeter has left

  1049. adiaholic has left

  1050. reimar has left

  1051. intosi has joined

  1052. adiaholic has joined

  1053. John has left

  1054. John has joined

  1055. papatutuwawa has left

  1056. adiaholic has left

  1057. stpeter has joined

  1058. stpeter has left

  1059. Tobias has left

  1060. jjrh has left

  1061. jjrh has joined

  1062. Maranda[x] has left

  1063. Matthew has left

  1064. Rixon 👁🗨 has left

  1065. uhoreg has left

  1066. homebeach has left

  1067. Half-Shot has left

  1068. Half-Shot has joined

  1069. Matthew has joined

  1070. Rixon 👁🗨 has joined

  1071. uhoreg has joined

  1072. homebeach has joined

  1073. Maranda[x] has joined

  1074. adiaholic has joined

  1075. floretta has left

  1076. adiaholic has left

  1077. adiaholic has joined

  1078. lorddavidiii has left

  1079. adiaholic has left

  1080. Menel has left

  1081. Seve has left

  1082. pasdesushi has left

  1083. intosi has left

  1084. adiaholic has joined

  1085. intosi has joined

  1086. adiaholic has left

  1087. jjrh has left

  1088. jjrh has joined

  1089. BASSGOD has left

  1090. BASSGOD has joined

  1091. adiaholic has joined

  1092. adiaholic has left

  1093. floretta has joined

  1094. intosi has left

  1095. arcxi has left

  1096. jcbrand has left

  1097. marc0s has left

  1098. marc0s has joined

  1099. marc0s has left

  1100. marc0s has joined

  1101. Syndace has left

  1102. kurisu has joined

  1103. Syndace has joined

  1104. emus has left

  1105. bung has left

  1106. John has left

  1107. John has joined

  1108. kurisu

    moparisthebest: > Also matrix invented the concept of bridging, nothing else had this decades before Matrix bridges are well integrated into clients. Now to use xmpp bridges to just irc I had to actually ask about working instances on biboumi chat (b/c you can't just google them, let alone connect automatically), then also find out which ones work lmao. I think we should give credit where credit's due

  1109. mathieui

    kurisu: I fail to see the links between your three statements

  1110. kurisu

    Try being honest with yourself and you will

  1111. mathieui

    I haven't dabbled in matrix clients in a while so I will ignore the first, the second is more about having a SPOF with a humongous IRC bridge on matrix.org, as far as I understand it?

  1112. mjk

    Aren't matrix bridges practically centralized? In which case there's nothig to discover

  1113. mathieui

    (I am not saying it does not work, or that the matrix IRC bridging is not a success, although I find it to be a bit abrasive from the IRC side, but I fail to see how it is relevant)

  1114. Alex has left

  1115. kyemxden has left

  1116. John has left

  1117. John has joined

  1118. moparisthebest

    kurisu: are you saying the matrix clients have the IRC gateways hardcoded? Doesn't sound very federated to me

  1119. floretta has left

  1120. moparisthebest

    kurisu: https://www.moparisthebest.com/images/xmpp-vs-matrix.jpg

  1121. intosi has joined

  1122. jl4 has joined

  1123. druthid has left

  1124. floretta has joined

  1125. druthid has joined

  1126. marc0s has left

  1127. marc0s has joined

  1128. goffi has left

  1129. stp has left

  1130. kyemxden has joined

  1131. mjk has left

  1132. atomicwatch has left

  1133. kurisu

    moparisthebest: > kurisu: are you saying the matrix clients have the IRC gateways hardcoded? Doesn't sound very federated to me I don't know, I only know that it just werks And no, builtin gateways don't harm federation. At the end of the day Conversations by default offers its server, is that a problem now? moparisthebest: > kurisu: https://www.moparisthebest.com/images/xmpp-vs-matrix.jpg I wish that honesty were the case irl.

  1134. John has left

  1135. John has joined

  1136. lovetox has left

  1137. intosi has left

  1138. adiaholic has joined