XMPP Council - 2021-09-08

  1. alex11 has joined
  2. sonny has left
  3. sonny has joined
  4. sonny has left
  5. sonny has joined
  6. sonny has left
  7. sonny has joined
  8. sonny has left
  9. sonny has joined
  10. sonny has left
  11. sonny has joined
  12. sonny has left
  13. sonny has joined
  14. pprrks has joined
  15. Kev has left
  16. Kev has joined
  17. pprrks has left
  18. SouL has joined
  19. sonny has left
  20. sonny has joined
  21. alex11 has left
  22. Kev has left
  23. Kev has joined
  24. Kev has left
  25. Kev has joined
  26. marc0s has left
  27. marc0s has joined
  28. me9 has joined
  29. Kev has left
  30. Kev has joined
  31. Tobias has joined
  32. Kev has left
  33. Kev has joined
  34. me9 has left
  35. Kev has left
  36. Kev has joined
  37. Kev has left
  38. Kev has joined
  39. Kev has left
  40. Kev has joined
  41. marc0s has left
  42. marc0s has joined
  43. Kev has left
  44. Kev has joined
  45. Kev has left
  46. Kev has joined
  47. marc0s has left
  48. marc0s has joined
  49. marc0s has left
  50. marc0s has joined
  51. Kev has left
  52. Kev has joined
  53. Kev has left
  54. Kev has joined
  55. Kev has left
  56. Kev has joined
  57. Kev has left
  58. Kev has joined
  59. Kev has left
  60. Kev has joined
  61. Kev has left
  62. Kev has joined
  63. Kev has left
  64. Kev has joined
  65. Kev has left
  66. Kev has joined
  67. sonny has left
  68. sonny has joined
  69. sonny has left
  70. sonny has joined
  71. Kev has left
  72. Kev has joined
  73. Kev has left
  74. Kev has joined
  75. Kev has left
  76. Kev has joined
  77. ChronosX88 has left
  78. ChronosX88 has joined
  79. Kev has left
  80. Kev has joined
  81. debacle has joined
  82. ChronosX88 has left
  83. ChronosX88 has joined
  84. ChronosX88 has left
  85. ChronosX88 has joined
  86. daniel has left
  87. debacle has left
  88. daniel has joined
  89. flow has joined
  90. debacle has joined
  91. Wojtek has joined
  92. ChronosX88 has left
  93. ChronosX88 has joined
  94. sonny has left
  95. sonny has joined
  96. ChronosX88 has left
  97. ChronosX88 has joined
  98. Kev has left
  99. Kev has joined
  100. Kev has left
  101. Kev has joined
  102. Kev has left
  103. Kev has joined
  104. sonny has left
  105. sonny has joined
  106. Kev has left
  107. Kev has joined
  108. Kev has left
  109. Kev has joined
  110. Kev has left
  111. Kev has joined
  112. Kev has left
  113. Kev has joined
  114. sonny has left
  115. sonny has joined
  116. sonny has left
  117. sonny has joined
  118. Kev has left
  119. Kev has joined
  120. Kev has left
  121. Kev has joined
  122. Kev has left
  123. Kev has joined
  124. Kev has left
  125. Kev has joined
  126. Kev has left
  127. Kev has joined
  128. Kev has left
  129. Kev has joined
  130. sonny has left
  131. sonny has joined
  132. sonny has left
  133. Kev has left
  134. sonny has joined
  135. Kev has joined
  136. Kev has left
  137. Kev has joined
  138. Kev has left
  139. Kev has joined
  140. Kev has left
  141. larma has left
  142. sonny has left
  143. sonny has joined
  144. sonny has left
  145. sonny has joined
  146. sonny has left
  147. sonny has joined
  148. sonny has left
  149. sonny has joined
  150. Ge0rG Oh, it's almost time, and I'm so excited to be the standin-chair today!
  151. Ge0rG It's Meeting Time!
  152. Ge0rG 1) Roll Call
  153. daniel Hi
  154. Zash Hello
  155. Ge0rG Jonas is excused.
  156. Ge0rG Do we have a dwd?
  157. dwd Sorry, yes!
  158. Ge0rG Awesome!
  159. Ge0rG 2) Agenda Bashing
  160. Ge0rG It's not my fault, so feel free to fire at will!
  161. Zash Surprise MAM vote!
  162. Ge0rG It's on the agenda, so not so much of a surprise.
  163. Ge0rG Maybe surprise MAM PR?
  164. Ge0rG I suggest we can discuss the PR ahead of voting.
  165. Ge0rG 3) Editor’s Update - Last Call for XEP-0459, Compliance Suites 2022
  166. Ge0rG I'm not sure if the author of CS'22 actually asked for the LC or if it was warranted by the remaining time for Old Council.
  167. Ge0rG But thank you very much to jonas’ the Editor.
  168. Ge0rG 4) Items for voting
  169. Ge0rG 4a) PR#1064: XEP-0227: New revision 1.1 URL: https://github.com/xsf/xeps/pull/1064
  170. Zash +1
  171. daniel +1
  172. dwd +1
  173. Ge0rG +1
  174. Ge0rG I'm sure that jonas’ will on-list.
  175. Ge0rG 4b) Advance XEP-0313 to Stable as-is
  176. Ge0rG There was a surprise PR update to this in https://github.com/xsf/xeps/pull/1104
  177. Ge0rG So I suggest to instead vote on: - accept PR#1104 - include CVE-2019-16235 and CVE-2020-26547 blocks from 0280 - accept the resulting XEP as Stable
  178. dwd Yeah, so wait for that PR to go in, and the security considerations you wanted?
  179. dwd Well, we can't really vote on anything given that.
  180. Ge0rG dwd: that PR is an author update based on LC feedback.
  181. Ge0rG and the CVE inclusion is viewed as Editorial.
  182. ChronosX88 has left
  183. ChronosX88 has joined
  184. dwd Oh, is it? Either way, I'd like to vote once we have those merged.
  185. daniel > Oh, is it? Either way, I'd like to vote once we have those merged. +1
  186. dwd I'm not sure that writing a load of security considerations really can be Editorial.
  187. Ge0rG Okay, so we wait for jonas’-the-Editor to push the merge button and to perform the respective boilerplate tasks.
  188. Ge0rG dwd: the security considerations are LC feeback ;)
  189. dwd Yes... But that doesn't make them editorial.
  190. Ge0rG dwd: no
  191. Ge0rG the question is: do we need another LC for feedback integrated from a previous LC?
  192. Zash I think not
  193. Ge0rG If not, then the next step would be to apply the PR and to vote for advancement into Stable.
  194. dwd Yes, sounds right to me.
  195. Ge0rG Or to vote for advancement based on the pre-condition of the PR being applied.
  196. dwd As in, no need for another LC.
  197. dwd But we can't vote on a XEP not in front of us.
  198. Ge0rG That's a tough point indeed.
  199. daniel Technically we have in the past I think
  200. daniel But there is absolutely no rush
  201. Ge0rG So let's have the Editor merge the PR and then we will re-elect.
  202. Ge0rG daniel: I'm actually not sure why there is sudden activity on this XEP after half a year of silence, but I'm very glad that it *is* happening.
  203. Ge0rG That said, I still have a long list of issues that weren't addressed in this PR, given that they were not blocking the advancement.
  204. Ge0rG 5) Pending Votes None.
  205. Ge0rG Good job, everyone :)
  206. Ge0rG 6) Date of Next
  207. Ge0rG +1W WFM
  208. daniel +1w wfm
  209. dwd +1WFM2
  210. Ge0rG Zash?
  211. Zash +1w wfm
  212. Ge0rG Awesome. Let's hope that jonas’ comes back well after the party.
  213. Ge0rG 7) AOB
  214. daniel Non here
  215. dwd daniel, Bit French, that.
  216. Ge0rG dwd: even if PR#1104 fixes the blockers for me, I'd still love to see some more discussion of the usefulness and treatment of type=groupchat in user's MAM. It would be great if you could follow-up on list.
  217. dwd Yes. And I will.
  218. daniel Tldr It makes no sense with plain xep45 but can be very useful with muc light, muc/sub and stuff?
  219. Ge0rG Thanks!
  220. Ge0rG daniel: looks like that.
  221. daniel And maybe or maybe not with MIX
  222. Ge0rG But in that case I'd say that 0313 should say "don't do that" and the other specs define how and when to store
  223. Ge0rG the only reason we get the include-groupchat query var is not breaking legacy systems.
  224. sonny has left
  225. sonny has joined
  226. Ge0rG Well, that's my fringe opinion at least.
  227. Ge0rG AAOB?
  228. sonny has left
  229. sonny has joined
  230. Ge0rG Alright, then.
  231. Ge0rG 8) EOM
  232. Ge0rG Thanks, everyone.
  233. Zash Thanks Ge0rG
  234. dwd Thanks Ge0rG
  235. Kev has joined
  236. Kev I don’t agree it makes no sense with 45, FWIW.
  237. Kev If you want the user to be able to search their archive for messages they’ve seen, it’s the only choice you’ve got.
  238. Zash Not as straight-forward at least
  239. Ge0rG Kev: I'd love to see a response from you on-list :)
  240. Kev There are assorted problems with it, and I’m ok (obviously) with the patch that makes it optional, but we simply don’t have another mechanism for it.
  241. dwd I mean, it's a bit crappy with XEP-0045, but then, everything is if what you really wanted was persistent groupchats.
  242. Kev And FWIW, I think requiring people to restate their arguments over and over and treat them eventually getting bored of repeating themselves as a sign that their arguments don’t need to be considered to be distinctly suboptimal.
  243. Ge0rG Kev: I'm sorry for leaving such an impression. I'm guilty of deriving "this doesn't make sense" from "this doesn't make sense for me"
  244. Kev I get that lots of people don’t care about being able to have complete archives of chats they’ve been in, and that’s fine, and making this optional means whole deployments can not have to care about it, but some people do care about that, and we shouldn’t be pointlessly changing protocol to prohibit servers from addressing that use case.
  245. Ge0rG Kev: it's a very valid use case, and I'm using a dedicated client with a local on-disk archive to solve that problem in a different way.
  246. Kev Storing MUC history in MAM sucks royally. But if you want to have access to chat history for all chats you’ve been in, it’s the only thing we’ve got, and it sucking is better (for some people) than not having it.
  247. Ge0rG Kev: what I'm saying is that as written, 0313 is not well suited to solve this problem, but opens a large number of 0045ities instead.
  248. Ge0rG Normally, Experimental is the phase in which we convert an ugly hack into a sort of viable long-term solution.
  249. Ge0rG 0045 logs in user MAM still fall into the "ugly hack" category for me, so please convince me it's not.
  250. Kev Protocol-wise, I think 313 as-written (at least after the patch that makes it optional) is fine. It defines what’s needed for interop. But the onus is definitely on the server to somehow make the presented archive not suck. I can add some additional words explaining some of the ways that gc in user archives sucks, if that helps.
  251. dwd Ge0rG, How would you address the user requirements without a local on-disk archive?
  252. Kev Or even with an on-disk archive, if you have multiple clients.
  253. dwd Kev, That's easy, you just make MAM queries to the client you keep continuously online...
  254. Ge0rG Again, I'm not saying that your problem is invalid, I'm questioning the non-solution that is "stuff all groupchat into user MAM"
  255. Ge0rG full-text-search is not even part of MAM.
  256. dwd Ge0rG, Yes, but my assertion would be that it's not MAM that's the issue, but MUC.
  257. dwd Ge0rG, Also, not in the core, but it is an enabler for it.
  258. Kev That somewhat depends what you mean by ‘part of MAM’ - 313 as-written allows arbitrary form fields, and those can be used for search.
  259. Ge0rG dwd: yes, but having "stuff all groupchat into MAM" makes it a MAM issue, too.
  260. pprrks has joined
  261. Ge0rG Kev: yes, and I'd love to see a dedicated FTS XEP on top of MAM, and that one could cover "store all groupchat messages in the user's archive, and search them for FTS queries"
  262. Ge0rG But as written now, as a client developer I must expect random subsets of past MUC histories from unrelated clients to fall upon me during initial startup sync.
  263. dwd Ge0rG, Which is quite useful with MUCSUB, Muclight, or MIX. :-)
  264. Kev You will always have to expect that as a client.
  265. Ge0rG dwd: none of which are MUC
  266. dwd Ge0rG, Well, MUCSUB is, kinda-sorta.
  267. Kev MAM is out there with gc results in it, you can’t change that. So the option is to disallow that with a namespace bump, or make it optional as in Dave’s proposal and my text (or to fix any non-compliant implementation currently out there that *doesn’t* do that).
  268. dwd Ge0rG, Also I think the Tigase people have something around groupchat to offline members.
  269. Kev There’s no way out of this that doesn’t involve clients written against this namespace of MAM having to accept gc messages if presented them.
  270. Ge0rG Kev: yes, you convinced me of that much. But I still don't see why or how it could make sense.
  271. Ge0rG And if namespace bumps weren't that expensive, I'd rather have suggested to remove gc and to bump.
  272. Kev Ignoring MAM search, what if you’re a full-sync client that wants to be able to search local archives? The only way to do that full sync is MAM, and that would also rely on gc messages in a full-sync query in order to build the local archive.
  273. Ge0rG Kev: you can't rely on a full gc history in the user archive, so you must ask the MUC for gc history anyway.
  274. Kev If your server includes gc in the archive you can rely on it returning the full history of what you’ve seen.
  275. Ge0rG Kev: so a full sync is to ask the user archive for non-gc and then each relevant MUC for its respective gc history.
  276. Kev Searching a full MUC history is different to searching your chats you’ve been in.
  277. Ge0rG the full history of what I've seen is not the full history.
  278. Kev And your client has no way of knowing what MUCs you’ve been in in the past.
  279. Ge0rG Yes.
  280. Kev (Unless it queries MAM for it)
  281. Wojtek > Ge0rG, Also I think the Tigase people have something around groupchat to offline members. this is just based on "registration" to the room and then sending messages irregardless if someone is in the room or not (with presence); though - this doens't necesarily invovled MAM and can be handled with regular "offline messages" spool
  282. Kev None of this is nice, but it is where we are.
  283. Ge0rG Kev: But now you've promoted a technical service interruption to a permanent message loss.
  284. Kev If we were writing XMPP from scratch there are many things we wouldn’t do this way.
  285. dwd It's nice that everyone has a non-interoperable solution to avoiding using MIX. :-)
  286. Ge0rG Kev: we have written MAM from scratch
  287. dwd (Though I think Tigase's is perhaps the neatest)
  288. Kev Indeed, and MAM isn’t the problem, MUC is.
  289. Ge0rG Kev: and once again, storing MUC messages in MAM makes it a MAM problem.
  290. Kev MAM storing group chat messages is absolutely fine in the face of MIX or whatever that doesn’t do fan-out.
  291. Ge0rG Kev: yes, and that's preconditioned on the MIX feature, and clients will use a MIX signal to obtain that history
  292. dwd (And good luck if you want servers to figure out what sort of GC it is)
  293. Ge0rG Even though MIX also didn't solve the s2s interruption message loss problem.
  294. Ge0rG dwd: do it based on the <x> element.
  295. Zash Isn't that something XEP-0198 is supposed to solve?
  296. Kev Although I don’t think anyone’s written it yet, I haven’t yet heard (that I can remember) why the MIX-sync stuff from the last summit wouldn’t work.
  297. Ge0rG Zash: s2s 0198 when?
  298. Zash We already have it
  299. Ge0rG Kev: I wasn't there and I didn't hear it, so I need to read it to say if it works.
  300. dwd I'm not entirely sure that it's possible to fix entirely. But '198 on S2S should mitigate at least. If you want to detect loss, you'll need a Merkel tree.
  301. Zash s2s-198 might be a touch underspecified tho, but it seems to at least not horribly break stuff
  302. Ge0rG I'd *love* to see answers to all that questions, and it might even be possible to learn from them to improve MUC.
  303. Zash dwd, did you say Blockchain?
  304. dwd Zash, No, I didn't. I said Merkel tree.
  305. Ge0rG s2s-0198 won't easily work over server restarts.
  306. Ge0rG please get Merkel out of my head.
  307. dwd Ge0rG, As I said, you can't prevent message loss.
  308. dwd Ge0rG, And she'll be gone soon enough.
  309. Ge0rG dwd: thanks for reminding me that the alternatives are all worse.
  310. Kev Youdon’t need a merkel tree to detect loss, it’s sufficient to be sequenced.
  311. dwd Kev, If you assume a sequencing point, yes.
  312. Zash Pointer to previous message?
  313. Zash Linked list?
  314. Ge0rG dwd: you can prevent message loss with a client that directly queries the MUC MAM archive.
  315. Kev Zash: That was the unit proposl, yes.
  316. Kev Zash: That was the summit proposal
  317. Kev Zash: That was the summit proposal, yes
  318. dwd Ge0rG, You can if the remote server's down.
  319. Ge0rG dwd: the remote server is not going to remain down forever, right?
  320. dwd Ge0rG, Whyever not?
  321. Ge0rG (well, if it is, at least we know that it is down and that we are somewhere near the end of the room history)
  322. Ge0rG I think the probabilities of "server gets disconnected" and "server goes down forever" are multiple orders of magnitude apart.
  323. Ge0rG It might make sense to optimize for the frequent event.
  324. dwd Ge0rG, Sure.
  325. dwd Ge0rG, I'm just saying you can't eliminate the problem, just mitigate.
  326. Ge0rG And the flaky network infrastructure that I live on causes more than one MUC disconnect per day, on average.
  327. Kev has left
  328. Ge0rG dwd: but you can't paper over the problem by pretending that "all the user has seen" = "all there is"
  329. dwd Ge0rG, No, you can't. But if you wan tto search for a message you've seen, that's enough.
  330. Ge0rG and now we have completed the circle :)
  331. me9 has joined
  332. debacle has left
  333. Kev has joined
  334. marc0s has left
  335. marc0s has joined
  336. Kev has left
  337. Kev has joined
  338. Kev has left
  339. sonny has left
  340. sonny has joined
  341. sonny has left
  342. sonny has joined
  343. marc0s has left
  344. marc0s has joined
  345. paul has left
  346. paul has joined
  347. Ge0rG I wonder if it would be feasible to add all discussed XEP numbers into the title of council meeting minutes, for easier mailbox search.
  348. me9 has left
  349. sonny has left
  350. sonny has joined
  351. Kev has joined
  352. Kev has left
  353. chronosx88 has joined
  354. Ge0rG So I've finally worked through the LC feedback on XEP-0280, and created three patches at https://gitlab.com/xsf/xeps/-/merge_requests/42
  355. Ge0rG Rendered version at https://ge0rg.gitlab.io/-/xeps/-/jobs/1573759155/artifacts/rendered-changes/xep-0280.html
  356. Ge0rG I'd like to discuss https://gitlab.com/xsf/xeps/-/merge_requests/42/diffs?commit_id=64f87e1d2ac8c60edd1355bc96ecfda25a603fc8 in next week's meeting, as it looks to me like it would require Council approval.
  357. Kev has joined
  358. sonny has left
  359. sonny has joined
  360. sonny has left
  361. sonny has joined
  362. Wojtek has left
  363. paul has left
  364. paul has joined
  365. Wojtek has joined
  366. Wojtek has left
  367. ChronosX88 has left
  368. stpeter has joined
  369. ChronosX88 has joined
  370. daniel has left
  371. daniel has joined
  372. daniel has left
  373. daniel has joined
  374. sonny has left
  375. sonny has joined
  376. sonny has left
  377. sonny has joined
  378. debacle has joined
  379. eta has left
  380. eta has joined
  381. pprrks has left
  382. Sam has left
  383. Sam has joined
  384. Kev has left
  385. Kev has joined
  386. sonny has left
  387. sonny has joined
  388. sonny has left
  389. sonny has joined
  390. sonny has left
  391. sonny has joined
  392. SouL has left
  393. flow has left
  394. ChronosX88 has left
  395. ChronosX88 has joined
  396. Kev has left
  397. Kev has joined
  398. chronosx88 has left
  399. Tobias has left
  400. sonny has left
  401. sonny has joined
  402. ralphm has left
  403. ralphm has joined
  404. sonny has left
  405. sonny has joined
  406. sonny has left
  407. sonny has joined
  408. sonny has left
  409. sonny has joined
  410. sonny has left
  411. sonny has joined
  412. sonny has left
  413. sonny has joined
  414. sonny has left
  415. sonny has joined
  416. debacle has left
  417. sonny has left
  418. sonny has joined
  419. sonny has left
  420. sonny has joined
  421. marc0s has left
  422. marc0s has joined
  423. sonny has left
  424. sonny has joined
  425. sonny has left
  426. sonny has joined
  427. sonny has left
  428. sonny has joined
  429. sonny has left
  430. sonny has joined
  431. alex11 has joined
  432. Kev has left
  433. Kev has joined
  434. pprrks has joined
  435. Kev has left
  436. Kev has joined