XSF Discussion - 2019-10-14

  1. Daniel has left
  2. andrey.g has joined
  3. Douglas Terabyte has left
  4. Douglas Terabyte has joined
  5. Daniel has joined
  6. !XSF_Martin has left
  7. !XSF_Martin has joined
  8. mimi89999 has joined
  9. zach has left
  10. zach has joined
  11. Daniel has left
  12. mukt2 has left
  13. pdurbin has joined
  14. pdurbin has left
  15. Daniel has joined
  16. zach has left
  17. zach has joined
  18. Daniel has left
  19. Daniel has joined
  20. debacle has left
  21. UsL has left
  22. UsL has joined
  23. emus has left
  24. emus has joined
  25. Daniel has left
  26. Daniel has joined
  27. matlag has left
  28. matlag has joined
  29. mukt2 has joined
  30. matlag has left
  31. Shell has left
  32. matlag has joined
  33. zach has left
  34. zach has joined
  35. neshtaxmpp has left
  36. neshtaxmpp has joined
  37. aj has left
  38. pdurbin has joined
  39. Chobbes has left
  40. Chobbes has joined
  41. lskdjf has left
  42. mukt2 has left
  43. pdurbin has left
  44. lskdjf has joined
  45. zach has left
  46. zach has joined
  47. !XSF_Martin has left
  48. mukt2 has joined
  49. !XSF_Martin has joined
  50. Daniel has left
  51. Daniel has joined
  52. mukt2 has left
  53. adiaholic has left
  54. adiaholic has joined
  55. adiaholic has left
  56. adiaholic has joined
  57. lskdjf has left
  58. andy has joined
  59. zach has left
  60. zach has joined
  61. !XSF_Martin has left
  62. !XSF_Martin has joined
  63. Yagiza has joined
  64. Maranda has joined
  65. !XSF_Martin has left
  66. Daniel has left
  67. !XSF_Martin has joined
  68. xalek has left
  69. pdurbin has joined
  70. Chobbes has left
  71. Chobbes has joined
  72. adiaholic has left
  73. Nekit has joined
  74. !XSF_Martin has left
  75. !XSF_Martin has joined
  76. pdurbin has left
  77. Daniel has joined
  78. Chobbes has left
  79. Chobbes has joined
  80. adiaholic has joined
  81. zach has left
  82. zach has joined
  83. Tobias has joined
  84. neshtaxmpp has left
  85. mukt2 has joined
  86. Daniel has left
  87. Daniel has joined
  88. mukt2 has left
  89. Zash has joined
  90. adiaholic has left
  91. Daniel has left
  92. Daniel has joined
  93. !XSF_Martin has left
  94. zach has left
  95. zach has joined
  96. karoshi has joined
  97. Mikaela has joined
  98. !XSF_Martin has joined
  99. waqas has left
  100. mimi89999 has left
  101. mimi89999 has joined
  102. zach has left
  103. zach has joined
  104. adiaholic has joined
  105. pdurbin has joined
  106. Douglas Terabyte has left
  107. Douglas Terabyte has joined
  108. neshtaxmpp has joined
  109. !XSF_Martin has left
  110. pdurbin has left
  111. !XSF_Martin has joined
  112. larma has left
  113. larma has joined
  114. LNJ has joined
  115. Daniel has left
  116. mukt2 has joined
  117. Daniel has joined
  118. zach has left
  119. zach has joined
  120. mukt2 has left
  121. Ge0rG has left
  122. !XSF_Martin has left
  123. Daniel has left
  124. Steve Kille has left
  125. Ge0rG has joined
  126. Daniel has joined
  127. !XSF_Martin has joined
  128. Steve Kille has joined
  129. Link Mauve has left
  130. zach has left
  131. zach has joined
  132. Link Mauve has joined
  133. Daniel has left
  134. Daniel has joined
  135. Dele (Mobile) has joined
  136. emus has left
  137. Link Mauve has left
  138. debacle has joined
  139. !XSF_Martin has left
  140. Link Mauve has joined
  141. Link Mauve has left
  142. eevvoor has joined
  143. Link Mauve has joined
  144. emus has joined
  145. jubalh has joined
  146. !XSF_Martin has joined
  147. zach has left
  148. zach has joined
  149. Zash has left
  150. Zash has joined
  151. j.r has left
  152. j.r has joined
  153. multixmp has joined
  154. goffi has joined
  155. goffi has left
  156. goffi has joined
  157. goffi has left
  158. goffi has joined
  159. goffi has left
  160. goffi has joined
  161. !XSF_Martin has left
  162. !XSF_Martin has joined
  163. j.r has left
  164. zach has left
  165. zach has joined
  166. multixmp has left
  167. Zash has left
  168. Zash has joined
  169. zach has left
  170. zach has joined
  171. eevvoor has left
  172. Nekit has left
  173. Nekit has joined
  174. chronosx88 has joined
  175. zach has left
  176. zach has joined
  177. jubalh has left
  178. multixmp has joined
  179. jubalh has joined
  180. multixmp has left
  181. zach has left
  182. zach has joined
  183. Daniel has left
  184. Daniel has joined
  185. adiaholic has left
  186. adiaholic has joined
  187. eevvoor has joined
  188. adiaholic has left
  189. zach has left
  190. zach has joined
  191. eevvoor has left
  192. multixmp has joined
  193. jubalh has left
  194. zach has left
  195. zach has joined
  196. eevvoor has joined
  197. multixmp has left
  198. !XSF_Martin has left
  199. andrey.g has left
  200. lskdjf has joined
  201. Daniel has left
  202. Daniel has joined
  203. Dele (Mobile) has left
  204. Dele (Mobile) has joined
  205. mukt2 has joined
  206. mukt2 has left
  207. !XSF_Martin has joined
  208. zach has left
  209. zach has joined
  210. LNJ has left
  211. LNJ has joined
  212. vanitasvitae has left
  213. multixmp has joined
  214. neshtaxmpp has left
  215. zach has left
  216. zach has joined
  217. jubalh has joined
  218. andrey.g has joined
  219. Douglas Terabyte has left
  220. multixmp has left
  221. zach has left
  222. zach has joined
  223. adiaholic has joined
  224. eevvoor has left
  225. eevvoor has joined
  226. lovetox has joined
  227. Daniel has left
  228. gav has left
  229. Daniel has joined
  230. zach has left
  231. zach has joined
  232. pdurbin has joined
  233. Daniel has left
  234. Daniel has joined
  235. eevvoor has left
  236. !XSF_Martin has left
  237. !XSF_Martin has joined
  238. zach has left
  239. zach has joined
  240. zach has left
  241. zach has joined
  242. Chobbes has left
  243. mukt2 has joined
  244. !XSF_Martin has left
  245. !XSF_Martin has joined
  246. zach has left
  247. zach has joined
  248. Mikaela has left
  249. mukt2 has left
  250. Mikaela has joined
  251. adiaholic has left
  252. adiaholic has joined
  253. zach has left
  254. zach has joined
  255. j.r has joined
  256. adiaholic has left
  257. adiaholic has joined
  258. aj has joined
  259. nyco-2 has joined
  260. APach has left
  261. nyco-2 has left
  262. adiaholic has left
  263. adiaholic has joined
  264. Shell has joined
  265. pdurbin has left
  266. zach has left
  267. zach has joined
  268. eevvoor has joined
  269. waqas has joined
  270. waqas has left
  271. adiaholic has left
  272. jubalh has left
  273. jubalh has joined
  274. Chobbes has joined
  275. vanitasvitae has joined
  276. APach has joined
  277. zach has left
  278. zach has joined
  279. adiaholic has joined
  280. adiaholic has left
  281. !XSF_Martin has left
  282. !XSF_Martin has joined
  283. zach has left
  284. zach has joined
  285. j.r has left
  286. debacle has left
  287. !XSF_Martin has left
  288. mukt2 has joined
  289. !XSF_Martin has joined
  290. zach has left
  291. zach has joined
  292. j.r has joined
  293. Shell has left
  294. Shell has joined
  295. Nekit has left
  296. jubalh has left
  297. zach has left
  298. zach has joined
  299. mukt2 has left
  300. Ge0rG flow: do you have a suggested wording for the MIX reference(s)=
  301. Ge0rG flow: before you answered my mail, I made it look like this: https://op-co.de/tmp/xep-0423.html#future
  302. adiaholic has joined
  303. !XSF_Martin has left
  304. Chobbes has left
  305. Chobbes has joined
  306. Wojtek has joined
  307. mukt2 has joined
  308. lskdjf Regarding the Compliance Suite: It lists "Private XML Storage", but what for, actually? I mean, private xml storage is no end in itself. bookmark storage previously used it, but the current version of the XEP doesn't, so what does XEP-0049 even do in there?
  309. zach has left
  310. zach has joined
  311. !XSF_Martin has joined
  312. Ge0rG lskdjf: it's still used for bookmarks by some clients, because transition and backward compatibility are hard
  313. Nekit has joined
  314. Nekit has left
  315. jonas’ also because pep bookmarks (except bookmarks2) don’t give a real benefit
  316. jonas’ and there was massive lack of server support for private and persistent pep until a year ago or so
  317. Ge0rG and the compatibility transition requirements of Bookmarks2 are abysmal
  318. Ge0rG looks at prosody 0.10 with a sad face
  319. lskdjf it's actually used by pretty much all clients ^^ perhaps make it clear that this is really just about bookmarks backwards compatibility, then? Maybe by putting it into the same row as "Advanced Group Chat"?
  320. pep. Ge0rG, you might want to reference https://xmpp.org/extensions/attic/xep-0048-1.0.html then instead?
  321. Zash Private XML storage was widely used for client settings back in the day, but I don't know if anything still does that
  322. Ge0rG "I don't know if" is not a good rationale to move it, or is it?
  323. Nekit has joined
  324. pep. Do you need stronger opinions?
  325. lskdjf Zash, you mean for storing it's own settings? that would have nothing to do with compliance, then.
  326. Zash lskdjf, storing settings on the server
  327. Ge0rG an advanced server needs to support it, no matter what a client does with it
  328. MattJ Ge0rG, maybe a nice parallel to "Future development" would be to document what stuff we are trying to deprecate also
  329. Ge0rG MattJ: indeed, but I'm not sure how to style that, also -ETIME
  330. mukt2 has left
  331. lskdjf Ge0rG, also you didn't remove vcard-temp (at least from the core client) yet. A few days ago I got the impression you were on board with doing that. Did someting change?
  332. j.r has left
  333. chronosx88 has left
  334. Ge0rG lskdjf: I have no clue on how relevant vcard-temp still is
  335. pep. vcard4 is Proposed, and has been for some months now :(
  336. j.r has joined
  337. pep. (At least it's better than most other XEPs in the CS)
  338. Kev I think vcard-temp is still very relevant.
  339. jonas’ sadly
  340. Chobbes has left
  341. MattJ vcard-temp is implemented by every server and just about every client
  342. Ge0rG Kev: is it core-relevant or advanced-relevant?
  343. Kev Core, I think.
  344. MattJ and vcard4 is implemented by one server, and possibly nothing else
  345. Ge0rG because avatars became advanced somehow. I hope nobody noticed.
  346. Kev You would struggle to implement an interoperable client/server without it.
  347. Kev And avatars need it, which are certainly core.
  348. pep. Does that mean it needs to be Client core/advanced?
  349. Kev Heh.
  350. Ge0rG Kev: as I said, User Avatars are advanced ;)
  351. alameyo has left
  352. alameyo has joined
  353. j.r has left
  354. j.r has joined
  355. chronosx88 has joined
  356. lskdjf Conversations doesn't have vcard-temp and it's (one of) the most popular clients. So not having vcard-temp can't be too bad.
  357. Chobbes has joined
  358. lskdjf > And avatars need it, which are certainly core. Kev: well clients can implement vcard avatars without displaying/parsing other vcard-temp information.
  359. lskdjf And for the record I also think avatars should stay in Core Client.
  360. Kev Only read-only.
  361. zach has left
  362. zach has joined
  363. Ge0rG I'm slowly losing track of all the things. Maybe this is due to the other things I need to work on in parallel, plus the timeline being tomorrow
  364. Ge0rG lskdjf: why are avatars more important than 0392?
  365. lskdjf "more important" is IMHO a wrong way to compare those two things. Mandating UI in the compliance suite is simply a very bad idea and not the task or competence of the council. It's not part of the protocol, it's UI/UX design. avatars on the other hand are part of the protocol and it doesn't matter how or where you display them.
  366. Ge0rG ...or if you display them at all
  367. MattJ I somewhat disagree with this analysis
  368. Ge0rG if I don't display avatars, do I need to support them at the protocol level?
  369. pdurbin has joined
  370. pep. I agree with lskdjf here fwiw
  371. Ge0rG luckily, I'm not wearing my Council hat here, but my XEP author hat ;)
  372. Kev I think Ge0rG's question is valid. Since 392 covers a fallback for avatars, it doesn't seem unreasonable to argue the case for it if you argue for avatars.
  373. pep. lskdjf, in any case, that should probably be expressed on the ML
  374. Kev I'm not sure I agree with it, but I think the argument is sane.
  375. neshtaxmpp has joined
  376. Ge0rG Kev: it's not a fallback, because you often need to display both the name and the image, but other than that, yeah.
  377. Ge0rG lskdjf: yes, please write it to the ML.
  378. Kev Ge0rG: The bit about fallback avatars is a fallback for avatars :)
  379. Ge0rG Kev: a fallback for fallback avatar fallback?
  380. Ge0rG Can we agree on moving vcard-temp into "User Avatar Compatibility" or are there other use cases for it?
  381. Kev Ge0rG: I think there's one argument that, irrespective of the optimal thing, it might be least contentious, if you want things through smoothly on a short timescale, to put comments in the future direction section, and not change too much that's likely to bikeshed.
  382. Zash Clients tend to use vcard-temp + xep-0153 for avatars?
  383. Kev I think vcard-temp is core, because of the avatar requirement.
  384. lskdjf > if I don't display avatars, do I need to support them at the protocol level? Ge0rG orcourse not. but then you're not compliant. the difference is: "User Avatars" mandates that you should _have_ a feature. Somewhere, somehow. If I have to cascade through 3 menues to get there, that's client choice. But "User Name Coloring" tells the clients _how_ to do a UI feature. That's a difference.
  385. Kev I think vcard-temp is advanced for all other use. It's not obsolete because vcard4 "isn't used".
  386. Ge0rG Kev: as I said, Avatars got demoted to Advanced by a strange mishap.
  387. Kev Using this year as an opportunity to rectify that seems sane :)
  388. Ge0rG I have no idea why heated debates always happen in the last days before the new CS XEP is getting proposed.
  389. Ge0rG We literally had a year to figure all that out.
  390. moparisthebest that's the first time people look at them :)
  391. Kev Because everything happens last-minute when dealing with busy people.
  392. Ge0rG I'm also slowly starting to feel why previous editors of the CS vanished.
  393. jonas’ indeed
  394. neshtaxmpp has left
  395. Ge0rG lskdjf: I'm not sure whether we read the same version of 0392.
  396. Ge0rG > Implementations may colorize the participants of a conversation with an individual color to make them easier to distinguish. > In such cases, the color SHOULD be generated as described in the Generating a color section.
  397. Ge0rG > Implementations SHOULD allow the user to turn off any colorization completely.
  398. Ge0rG lskdjf: also I'm curious what your actual problem with 0392 is, besides of it being out-of-scope of the XSF powers.
  399. neshtaxmpp has joined
  400. zach has left
  401. zach has joined
  402. alameyo has left
  403. alameyo has joined
  404. pdurbin has left
  405. Ge0rG lskdjf: that said, I really don't see the principal difference to avatars. I'd even argue that avatars are worse than 0392, because their transmission consumes additional network capacity
  406. larma GeOrG, I think the main issue is that quiet some XEPs on the list are on CS for the first time and many probably did not expect them to end up there given that they are still in their early days. I am currently writing a lengthy mail for the ML explaining why I think the color generation is flawed and imposes accessibility issues if used as suggested (which is rarely done, fortunately).
  407. eevvoor has left
  408. Ge0rG larma: I think the main goal of CS is to provide a useful selection of what to implement, to authors. I've done a review of the existing XEPs and considered some more for addition.
  409. Ge0rG larma: jonas’ and I will be very interested to hear about the accessibility issues of 0392, and I hope we can improve that.
  410. Shell has left
  411. larma As far as I know, there are actually very few existing clients implementing the 3.2 usecase of 0392, where lack of contrast is a significant issue (it doesn't really matter for avatars, because avatars don't matter)
  412. karoshi has left
  413. karoshi has joined
  414. Daniel Fwiw I feel some general uneasiness about trying to put in a lot of new xeps last minute
  415. Ge0rG larma: lack of contrast between the colored nickname and the background / theme of the client, or between different names?
  416. larma first, second wouldn't be an accessibility issue
  417. jonas’ larma, for background contrast, there is https://xmpp.org/extensions/xep-0392.html#impl-bgcolor
  418. jonas’ larma, for background contrast, there is https://xmpp.org/extensions/xep-0392.html#impl-bgcolor
  419. jonas’ we can adapt the factors in https://xmpp.org/extensions/xep-0392.html#algorithm-bg if they’re not good enough for accesibility
  420. jonas’ also please note that all implementations must have an OFF switch for text colorisation for accessibility reason
  421. jonas’ also please note that all implementations must have an OFF switch for text colorisation for accessibility reasons
  422. jonas’ also please note that all implementations SHOULD have an OFF switch for text colorisation for accessibility reasons
  423. waqas has joined
  424. mukt2 has joined
  425. aj has left
  426. vanitasvitae has left
  427. alameyo has left
  428. pep. Daniel, yeah.. lots of friction in a short period of time, not good.
  429. pep. We need to add some time to allow for dissipation
  430. Ge0rG if only we didn't have Council election in a month, followed by re-org, followed by Christmas.
  431. Ge0rG it will be impossible to finish this in 2019 if we don't vote on advancing before the reeleection.
  432. Ge0rG I'm not sure when I volunteered to do CS-2020, but I'm sure it was early this year.
  433. Ge0rG so everybody had enough time to propose changes.
  434. Daniel The fact that nobody suggested changes could be seen as being fine with the status quo
  435. Kev Or that no-one's particularly enthusiastic about the suites.
  436. pep. Also
  437. alameyo has joined
  438. Ge0rG Or that no-one's particularly enthusiastic about XMPP.
  439. zach has left
  440. zach has joined
  441. Kev I'm more enthusiastic about XMPP than I am about the suites.
  442. Daniel It seems to be causing some friction now. So apparently people do care about the CS
  443. Kev I didn't mention caring, I mentioned enthusiasm ;)
  444. Kev I think we'd be better off not publishing them (in their Compliance Suite form, at least), but if we have to publish them I don't think we should get them wrong.
  445. Ge0rG Kev: I think we tried very hard to have a phone conference type of thing happen to discuss alternative ways to do CS
  446. Daniel I think compliance suites are a good thing. But I'd be careful about them becoming a simple _include all_
  447. Ge0rG Sorry, I got to run now. I really hope I'm going to read your specific feedback on list, tomorrow.
  448. Steve Kille has left
  449. Steve Kille has joined
  450. zach has left
  451. zach has joined
  452. mukt2 has left
  453. alameyo has left
  454. alameyo has joined
  455. Shell has joined
  456. Nekit has left
  457. Nekit has joined
  458. andy has left
  459. Chobbes has left
  460. Chobbes has joined
  461. zach has left
  462. zach has joined
  463. j.r has left
  464. j.r has joined
  465. andy has joined
  466. Shell has left
  467. marc_ Ge0rG: you're not attending at the Munich Meet up, right?
  468. larma jonas’, yes I have read the XEP and the background color correction algorithm presented there is pretty bad
  469. jonas’ larma, suggestions welcome
  470. Zash How is it bad?
  471. jubalh has joined
  472. Ge0rG And regarding the last minute changes, I'm very sorry. I didn't factor in the time for the Last Call, also was very busy the last weeks (and still am). I really hoped to have this ready sooner
  473. moparisthebest re 392, it's not perfect, but I haven't seen perfect yet, at least it's specified, it's better than whatever dino is using for instance
  474. moparisthebest I'm in an IRC chat using biboumi with about 40 people, dino has about 4 different colors total shared across everyone, conversations uses 392 and at least has about 10 different colors instead
  475. moparisthebest (I'm a little colorblind so that's how it looks for me, I haven't actually sampled RGB colors lately)
  476. moparisthebest it's pretty hard to get it right, when jonas’ was playing with the algorithm, if he applied it to one set of usernames it'd look perfect, but then applied to another set, really bad, no idea
  477. zach has left
  478. zach has joined
  479. !XSF_Martin has left
  480. Ge0rG Daniel, pep. and me look almost identical in here. Well, that's life
  481. Chobbes has left
  482. Chobbes has joined
  483. jubalh has left
  484. pdurbin has joined
  485. zach has left
  486. zach has joined
  487. jubalh has joined
  488. Daniel has left
  489. Daniel has joined
  490. zach has left
  491. zach has joined
  492. larma Ge0rG, can you remove XEP-0223 from the list? It is Informational, there is nothing clients or servers need to do to implement it, so you are always compliant...
  493. pdurbin has left
  494. !XSF_Martin has joined
  495. eevvoor has joined
  496. Ge0rG larma: isn't it useful to know for implementing bookmarks?
  497. pep. Isn't it required by bookmarks then?
  498. eevvoor has left
  499. pep. > It is RECOMMENDED to use Publish-Subscribe (XEP-0060) [4] for data storage, specifically through the use of personal data nodes hosted at the user's virtual publish-subscribe service as described in Best Practices for Persistent Storage of Private Data via Publish-Subscribe (XEP-0223) [5] and illustrated in the following sections.
  500. eevvoor has joined
  501. Zash There's no XEP for "Full blown PubSub on your own JID", XEP-0163 specifies a minimum subset.
  502. pep. and it's again mentioned in the security considerations
  503. Zash XEP-0222 and 0223 talk about fancy things you can do with a slightly bigger subset
  504. Zash Does '163 actually specify a protocol? Should it too be Informational?
  505. Zash Or should 22[23] be Standards Track?
  506. Zash 0060 is where everything is defined anyways, but you can't implement all of that
  507. pep. You can, no? But it's probably not required for most use-cases
  508. Zash All of '60? No that's impossible. First you have to implement half of it, which is a huge task. Then you have to implement half of the remaining part, also a huge task. Then half of the remaining, still a huge task.
  509. Zash ... etc
  510. larma Well I was thinking it makes more sense to require bookmarks 2 support if we require bookmarks 2 support. It doesn't add any value (at least for client developers) to know they should implement XEP-0223, because there is nothing in XEP-0223 that can be implemented.
  511. Zash larma: You could not do '222 or 223 with Prosody prior to version 0.10.
  512. Zash So there was *something* that was implemented.
  513. pep. because #persist_items ?
  514. Zash and access models
  515. larma Zash, Yeah, for servers it might make sense, for clients it doesn't
  516. larma on the other hand bookmarks 2 is nothing a server needs to handle if they do XEP-0223
  517. Zash larma: There is still a step between the absolute baseline defined by '163 up to what 222/223 describes
  518. Zash Like, dealing with publish-options
  519. larma I agree, but still it's servers implementing 223, clients implement bookmarks 2 which relies on servers implementing the 0060 subset outlined in 0223
  520. Zash So, my point is, pointing to '223 in the compliance suite is a short-hand for pointing to specific features in 0060
  521. larma what I mean is, we want servers to implement 163/223, but if a client only has a function to fetch bookmarks 2, that's fine, it doesn't need to be able to do anything generic for 163/223
  522. Zash I think you want publish-options with access model = whitelist
  523. zach has left
  524. zach has joined
  525. debacle has joined
  526. Ge0rG larma: there is also this thing about Bookmarks 2 not requiring backward compatibility.
  527. pep. Ge0rG, yeah that should be added, and I think it is in the submitted PR
  528. pep. (that JC just reviewed btw)
  529. Ge0rG And even then, we can't demand bookmarks 2 right now, because inertia.
  530. Zash Under Futures maybe, but it seems way too early for a compliance suite spot
  531. Ge0rG It's been just a few hours since I was told not to add controversial specifications at the last minute.
  532. Ge0rG Zash: it's in Future already 😉
  533. Zash Ah
  534. Zash Can you re-post the link please?
  535. Ge0rG > https://op-co.de/tmp/xep-0423.html
  536. zach has left
  537. Zash Thanks
  538. zach has joined
  539. eevvoor has left
  540. xalek has joined
  541. Daniel has left
  542. Daniel has joined
  543. mukt2 has joined
  544. Chobbes has left
  545. Chobbes has joined
  546. Chobbes has left
  547. Chobbes has joined
  548. Chobbes has left
  549. Chobbes has joined
  550. Maranda has left
  551. Maranda has joined
  552. taylon has joined
  553. zach has left
  554. zach has joined
  555. taylon has left
  556. mukt2 has left
  557. Nekit has left
  558. Nekit has joined
  559. zach has left
  560. zach has joined
  561. eevvoor has joined
  562. rion has left
  563. rion has joined
  564. chronosx88 has left
  565. !XSF_Martin has left
  566. !XSF_Martin has joined
  567. zach has left
  568. zach has joined
  569. aliex@exploit.im has joined
  570. pdurbin has joined
  571. Shell has joined
  572. pdurbin has left
  573. waqas has left
  574. waqas has joined
  575. alameyo has left
  576. alameyo has joined
  577. waqas has left
  578. waqas has joined
  579. waqas has left
  580. !XSF_Martin has left
  581. waqas has joined
  582. !XSF_Martin has joined
  583. flow Ge0rG, FWIW, I do really like your proposed compliance suites. Even though I don't see the point in mentioning all the single MIX XEPs, as it appears to create a lot of noise for no benefit. But besides that, it comes close to the "map of the xep jungle", which provides guidance about the current state and the probable future of XMPP, that I always asked for :)
  584. lovetox just for info, there are still open issues with bookmarks 2 - 0060 needs changes - bookmarks2 XEP needs many additions - servers dont implement the requirements needed to use the XEP correctly
  585. pep. https://github.com/xsf/xeps/pull/835 ^, as mentioned in the other channel
  586. pep. Also for 0060: https://github.com/xsf/xeps/pull/840
  587. lovetox and for server issue: https://github.com/processone/ejabberd/issues/3044
  588. adiaholic has left
  589. alameyo has left
  590. lovetox and of course we need conversion mods :)
  591. lovetox so long road i would say
  592. Ge0rG flow: have you checked the updated MIX list?
  593. pep. Well 402 can be used standalone once this is pushed
  594. pep. So it would make sense in some setups already
  595. lovetox has left
  596. pep. Maybe not for the "open network" (whatever that would be called)
  597. moparisthebest "reality"
  598. Tobias has left
  599. eevvoor has left
  600. flow Ge0rG, when did you update it? You understood that I am arguing that there shouldn't be a MIX list at all but just a single reference to xep369?
  601. alameyo has joined
  602. Ge0rG flow: around the time you wrote your response. I just wondered whether this new approach is better. People need some way to discover the other MIX parts
  603. Zash Ge0rG, minor thing but why is the web section before the im section?
  604. Ge0rG Zash: it was that way before
  605. Zash And should MLS be mentioned among the E2EE things?
  606. Ge0rG Zash: is there a XEP?
  607. Zash Ge0rG, is XMPP-Core a XEP?
  608. Ge0rG Zash: is there an RFC?
  609. wurstsalat has left
  610. alameyo has left
  611. alameyo has joined
  612. Zash Internet Drafts, https://datatracker.ietf.org/wg/mls/documents/
  613. Zash ~Experimenal or so
  614. Zash "Future things to keep an eye on" maybe. Not sure.
  615. Zash I also wish for more XEP-0288
  616. jubalh has left
  617. !XSF_Martin has left
  618. !XSF_Martin has joined
  619. alameyo has left
  620. wurstsalat has joined
  621. flow Ge0rG, last time I looked at xep369, it did a very good job at pointing out the other MIX parts, if this is not the case, then this should be fixed in xep369 and not in the compliance suites
  622. mukt2 has joined
  623. flow Zash, an XMPP+MLS I-D would be better
  624. Zash flow, I imagine that, or an equivalent XEP, might get written at some point
  625. flow I don't have issues with the compliance suites pointing to MLS, but it should be clearly spelled out that there is no XMPP+MLS thingy yet
  626. Zash "On the horizon" something sometihng header maybe?
  627. flow otherwise people may desperatly search for it because the compliance suites gave them the impression that such a thing exists
  628. Zash No idea what timeframe MLS might be ready in
  629. flow + when XMPP-flavored MLS appears on the market
  630. Chobbes has left
  631. zach has left
  632. zach has joined
  633. mukt2 has left
  634. alameyo has joined
  635. goffi has left
  636. Nekit has left
  637. andrey.g has left
  638. Dele (Mobile) has left
  639. alameyo has left
  640. alameyo has joined
  641. eevvoor has joined
  642. alameyo has left
  643. edhelas has left
  644. edhelas has joined
  645. dragonspirit810 has joined
  646. alameyo has joined
  647. !XSF_Martin has left
  648. !XSF_Martin has joined
  649. Shell has left
  650. dragonspirit810 has left
  651. dragonspirit810 has joined
  652. Ge0rG If it's a time frame of over a year, which it most likely is, there is no reason to put it into CS 2020
  653. zach has left
  654. zach has joined
  655. dragonspirit810 has left
  656. Zash XEP-0286: Mobile Considerations, what does it mean to support that?
  657. Ge0rG Zash: nothing
  658. Zash Informational XEP in CS is kinda odd.
  659. dragonspirit810 has joined
  660. !XSF_Martin has left
  661. alameyo has left
  662. !XSF_Martin has joined
  663. alameyo has joined
  664. dragonspirit810 has left
  665. wurstsalat has left
  666. andrey.g has joined
  667. Zash What's a server meant to do with Direct MUC Invites?
  668. j.r has left
  669. !XSF_Martin has left
  670. andy has left
  671. j.r has joined
  672. mimi89999 has left
  673. andy has joined
  674. eevvoor has left
  675. LNJ has left
  676. !XSF_Martin has joined
  677. mimi89999 has joined
  678. j.r has left
  679. Shell has joined
  680. zach has left
  681. zach has joined
  682. j.r has joined
  683. !XSF_Martin has left
  684. emus has left
  685. vanitasvitae has joined
  686. mukt2 has joined
  687. !XSF_Martin has joined
  688. Daniel has left
  689. Daniel has joined
  690. karoshi has left
  691. Daniel has left
  692. mukt2 has left
  693. Wojtek has left
  694. vanitasvitae has left
  695. Daniel has joined
  696. Daniel has left
  697. UsL has left
  698. UsL has joined
  699. Maranda has left
  700. Maranda has joined
  701. !XSF_Martin has left
  702. Chobbes has joined
  703. vanitasvitae has joined
  704. !XSF_Martin has joined
  705. Daniel has joined
  706. Daniel has left
  707. Chobbes has left
  708. Chobbes has joined
  709. Chobbes has left
  710. Chobbes has joined