XSF Discussion - 2020-04-20

  1. serge90 has left

  2. serge90 has joined

  3. xsf has left

  4. serge90 has left

  5. serge90 has joined

  6. serge90 has left

  7. serge90 has joined

  8. mukt2 has left

  9. serge90 has left

  10. serge90 has joined

  11. serge90 has left

  12. serge90 has joined

  13. xsf has joined

  14. serge90 has left

  15. serge90 has joined

  16. serge90 has left

  17. serge90 has joined

  18. aj has joined

  19. serge90 has left

  20. serge90 has joined

  21. lskdjf has left

  22. serge90 has left

  23. serge90 has joined

  24. pdurbin has joined

  25. serge90 has left

  26. serge90 has joined

  27. xsf has left

  28. serge90 has left

  29. serge90 has joined

  30. xsf has joined

  31. pdurbin has left

  32. aj has left

  33. xsf has left

  34. xsf has joined

  35. serge90 has left

  36. serge90 has joined

  37. arc has left

  38. arc has joined

  39. Seve has left

  40. moparisthebest has joined

  41. xsf has left

  42. xsf has joined

  43. stpeter has joined

  44. stpeter has left

  45. serge90 has left

  46. serge90 has joined

  47. serge90 has left

  48. serge90 has joined

  49. Neustradamus has left

  50. Neustradamus has joined

  51. serge90 has left

  52. serge90 has joined

  53. serge90 has left

  54. serge90 has joined

  55. andrey.g has left

  56. serge90 has left

  57. serge90 has joined

  58. andrey.g has joined

  59. serge90 has left

  60. serge90 has joined

  61. arc has left

  62. arc has joined

  63. serge90 has left

  64. serge90 has joined

  65. serge90 has left

  66. serge90 has joined

  67. serge90 has left

  68. serge90 has joined

  69. arc has left

  70. arc has joined

  71. serge90 has left

  72. serge90 has joined

  73. arc has left

  74. arc has joined

  75. pdurbin has joined

  76. arc has left

  77. arc has joined

  78. serge90 has left

  79. serge90 has joined

  80. serge90 has left

  81. serge90 has joined

  82. serge90 has left

  83. serge90 has joined

  84. serge90 has left

  85. serge90 has joined

  86. serge90 has left

  87. serge90 has joined

  88. serge90 has left

  89. serge90 has joined

  90. serge90 has left

  91. serge90 has joined

  92. serge90 has left

  93. serge90 has joined

  94. serge90 has left

  95. serge90 has joined

  96. andy has joined

  97. serge90 has left

  98. serge90 has joined

  99. bear has left

  100. serge90 has left

  101. serge90 has joined

  102. Seve has joined

  103. serge90 has left

  104. serge90 has joined

  105. serge90 has left

  106. serge90 has joined

  107. DebXWoody has joined

  108. serge90 has left

  109. serge90 has joined

  110. Nekit has joined

  111. serge90 has left

  112. serge90 has joined

  113. serge90 has left

  114. serge90 has joined

  115. serge90 has left

  116. serge90 has joined

  117. bear has joined

  118. Tobias has joined

  119. serge90 has left

  120. serge90 has joined

  121. serge90 has left

  122. serge90 has joined

  123. serge90 has left

  124. serge90 has joined

  125. werdan has joined

  126. Mikaela has joined

  127. bear has left

  128. serge90 has left

  129. serge90 has joined

  130. lorddavidiii has joined

  131. serge90 has left

  132. serge90 has joined

  133. Mikaela has left

  134. Tobias has left

  135. Tobias has joined

  136. Jeybe has joined

  137. Jeybe has left

  138. Jeybe has joined

  139. serge90 has left

  140. serge90 has joined

  141. Mikaela has joined

  142. Jeybe has left

  143. Jeybe has joined

  144. serge90 has left

  145. serge90 has joined

  146. Jeybe has left

  147. Jeybe has joined

  148. werdan has left

  149. Jeybe has left

  150. Jeybe has joined

  151. mukt2 has joined

  152. serge90 has left

  153. serge90 has joined

  154. lovetox has joined

  155. paul has joined

  156. serge90 has left

  157. serge90 has joined

  158. Jeybe has left

  159. Jeybe has joined

  160. adiaholic_ has left

  161. Jeybe has left

  162. Jeybe has joined

  163. paul has left

  164. serge90 has left

  165. serge90 has joined

  166. Jeybe has left

  167. adiaholic_ has joined

  168. Jeybe has joined

  169. adiaholic_ has left

  170. adiaholic_ has joined

  171. paul has joined

  172. Mikaela has left

  173. Mikaela has joined

  174. wurstsalat has joined

  175. serge90 has left

  176. serge90 has joined

  177. bear has joined

  178. Jeybe has left

  179. Jeybe has joined

  180. Jeybe has left

  181. Jeybe has joined

  182. Jeybe has left

  183. Jeybe has joined

  184. adiaholic_ has left

  185. Jeybe has left

  186. Jeybe has joined

  187. serge90 has left

  188. serge90 has joined

  189. serge90 has left

  190. serge90 has joined

  191. j.r has left

  192. bear has left

  193. serge90 has left

  194. serge90 has joined

  195. Jeybe has left

  196. Jeybe has joined

  197. serge90 has left

  198. serge90 has joined

  199. Jeybe has left

  200. Jeybe has joined

  201. serge90 has left

  202. serge90 has joined

  203. j.r has joined

  204. nyco has left

  205. serge90 has left

  206. serge90 has joined

  207. adiaholic_ has joined

  208. paul has left

  209. paul has joined

  210. serge90 has left

  211. serge90 has joined

  212. rion has left

  213. mukt2 has left

  214. serge90 has left

  215. serge90 has joined

  216. sonny has left

  217. emus has joined

  218. serge90 has left

  219. serge90 has joined

  220. Jeybe has left

  221. Jeybe has joined

  222. karoshi has joined

  223. bear has joined

  224. serge90 has left

  225. serge90 has joined

  226. Jeybe has left

  227. Jeybe has joined

  228. mukt2 has joined

  229. kevin has joined

  230. kevin has left

  231. adiaholic_ has left

  232. adiaholic_ has joined

  233. adiaholic_ has left

  234. adiaholic_ has joined

  235. Jeybe has left

  236. Jeybe has joined

  237. adiaholic_ has left

  238. adiaholic_ has joined

  239. serge90 has left

  240. serge90 has joined

  241. Jeybe has left

  242. rion has joined

  243. Jeybe has joined

  244. mukt2 has left

  245. jubalh has joined

  246. Jeybe has left

  247. sonny has joined

  248. Jeybe has joined

  249. mukt2 has joined

  250. bear has left

  251. serge90 has left

  252. serge90 has joined

  253. serge90 has left

  254. serge90 has joined

  255. mukt2 has left

  256. Neustradamus

    MattJ: Any news? - https://github.com/xmpp-observatory/xmppoke-frontend/issues/8#issuecomment-616323674

  257. lovetox has left

  258. Jeybe has left

  259. nyco has joined

  260. Jeybe has joined

  261. jonas’

    Neustradamus, is xmpp.net working?

  262. serge90 has left

  263. serge90 has joined

  264. lovetox has joined

  265. xecks has joined

  266. karoshi has left

  267. karoshi has joined

  268. Jeybe has left

  269. Jeybe has joined

  270. jubalh has left

  271. lovetox has left

  272. rion has left

  273. serge90 has left

  274. serge90 has joined

  275. Jeybe has left

  276. Jeybe has joined

  277. serge90 has left

  278. serge90 has joined

  279. Jeybe has left

  280. kevin has joined

  281. rion has joined

  282. serge90 has left

  283. serge90 has joined

  284. eevvoor has joined

  285. aj has joined

  286. mukt2 has joined

  287. bear has joined

  288. kevin has left

  289. serge90 has left

  290. serge90 has joined

  291. robertooo has joined

  292. serge90 has left

  293. serge90 has joined

  294. mukt2 has left

  295. aj has left

  296. mukt2 has joined

  297. emus has left

  298. serge90 has left

  299. serge90 has joined

  300. bear has left

  301. larma has left

  302. marc

    SamWhited: yes, I'll ping you 👌

  303. lovetox has joined

  304. larma has joined

  305. serge90 has left

  306. serge90 has joined

  307. SamWhited has left

  308. SamWhited has joined

  309. serge90 has left

  310. serge90 has joined

  311. lovetox has left

  312. lovetox has joined

  313. serge90 has left

  314. serge90 has joined

  315. serge90 has left

  316. serge90 has joined

  317. mukt2 has left

  318. mukt2 has joined

  319. mukt2 has left

  320. mukt2 has joined

  321. serge90 has left

  322. serge90 has joined

  323. mukt2 has left

  324. mukt2 has joined

  325. mukt2 has left

  326. serge90 has left

  327. serge90 has joined

  328. lskdjf has joined

  329. lskdjf has left

  330. serge90 has left

  331. serge90 has joined

  332. mukt2 has joined

  333. bear has joined

  334. serge90 has left

  335. serge90 has joined

  336. lskdjf has joined

  337. serge90 has left

  338. serge90 has joined

  339. j.r has left

  340. j.r has joined

  341. Nekit has left

  342. Nekit has joined

  343. serge90 has left

  344. serge90 has joined

  345. !XSF_Martin has left

  346. bear has left

  347. serge90 has left

  348. serge90 has joined

  349. emus has joined

  350. serge90 has left

  351. serge90 has joined

  352. Daniel has left

  353. Daniel has joined

  354. kevin has joined

  355. kevin has left

  356. serge90 has left

  357. serge90 has joined

  358. serge90 has left

  359. serge90 has joined

  360. Daniel has left

  361. Daniel has joined

  362. mukt2 has left

  363. serge90 has left

  364. serge90 has joined

  365. Daniel has left

  366. Daniel has joined

  367. !XSF_Martin has joined

  368. mukt2 has joined

  369. Daniel has left

  370. Daniel has joined

  371. serge90 has left

  372. serge90 has joined

  373. eta has left

  374. eta has joined

  375. serge90 has left

  376. serge90 has joined

  377. debacle has joined

  378. Daniel has left

  379. Daniel has joined

  380. bear has joined

  381. serge90 has left

  382. serge90 has joined

  383. Steve Kille has left

  384. serge90 has left

  385. serge90 has joined

  386. APach has left

  387. APach has joined

  388. serge90 has left

  389. APach has left

  390. serge90 has joined

  391. APach has joined

  392. Steve Kille has joined

  393. bear has left

  394. APach has left

  395. APach has joined

  396. serge90 has left

  397. serge90 has joined

  398. Daniel has left

  399. Daniel has joined

  400. Daniel has left

  401. Daniel has joined

  402. mukt2 has left

  403. Daniel has left

  404. edhelas has left

  405. Daniel has joined

  406. serge90 has left

  407. serge90 has joined

  408. edhelas has joined

  409. serge90 has left

  410. goffi has joined

  411. serge90 has joined

  412. goffi has left

  413. serge90 has left

  414. serge90 has joined

  415. emus has left

  416. emus has joined

  417. !XSF_Martin has left

  418. !XSF_Martin has joined

  419. serge90 has left

  420. serge90 has joined

  421. Ingo has joined

  422. Ingo has left

  423. mukt2 has joined

  424. arc has left

  425. arc has joined

  426. goffi has joined

  427. serge90 has left

  428. serge90 has joined

  429. Shell has joined

  430. Daniel has left

  431. Daniel has joined

  432. Daniel has left

  433. Daniel has joined

  434. Jeybe has joined

  435. serge90 has left

  436. serge90 has joined

  437. Shell has left

  438. Shell has joined

  439. goffi has left

  440. goffi has joined

  441. bear has joined

  442. serge90 has left

  443. serge90 has joined

  444. serge90 has left

  445. serge90 has joined

  446. Nekit has left

  447. serge90 has left

  448. serge90 has joined

  449. sonny has left

  450. Daniel has left

  451. Daniel has joined

  452. bear has left

  453. serge90 has left

  454. serge90 has joined

  455. Nekit has joined

  456. !XSF_Martin has left

  457. Jeybe has left

  458. !XSF_Martin has joined

  459. Jeybe has joined

  460. serge90 has left

  461. eevvoor

    How do I connect to a IRC via XMPP? I did that bevore but cannot refind instructions nor remember how I did that.

  462. serge90 has joined

  463. Zash

    You would use a transport like Biboumi or something.

  464. eevvoor

    Zash, how exactly? I used Gajim that time and only remeber that it was easy, nothing else :D.

  465. Ge0rG

    eevvoor: there are a few public hosted biboumi instances, and you can run your own of course

  466. eevvoor

    Ge0rG, ah ok. I will not host my own at the moment.

  467. Ge0rG

    eevvoor: there is a semi-public one on irc.yax.im that I'm running and I think there was also one on jabberfr

  468. eevvoor

    How would I use yours Ge0rG

  469. Ge0rG

    eevvoor: /join #channel%ircserver@irc.yax.im should work, or ad-hoc-configure irc.yax.im

  470. Ge0rG

    provided that s2s works for it.

  471. Ge0rG

    no idea though ;)

  472. MattJ

    No DNS

  473. MattJ

    irc.jabberfr.org responds though

  474. sonny has joined

  475. Ge0rG

    ah right, you'd have to add irc.yax.im CNAME xmpp.yaxim.org for it to work.

  476. goffi has left

  477. Ge0rG

    ...on your xmpp server. security by obscurity.

  478. goffi has joined

  479. serge90 has left

  480. serge90 has joined

  481. eevvoor

    hm Ge0rG where do I use the /join cmd?

  482. Ge0rG

    eevvoor: in your xmpp client

  483. eevvoor

    ah :D

  484. xsf has left

  485. goffi has left

  486. goffi has joined

  487. serge90 has left

  488. serge90 has joined

  489. serge90 has left

  490. serge90 has joined

  491. Daniel has left

  492. serge90 has left

  493. Daniel has joined

  494. serge90 has joined

  495. Daniel has left

  496. Daniel has joined

  497. eevvoor

    Ok. it worked. thx Ge0rG, this time I document it for myself.

  498. eevvoor

    In case I would need to specify the port, would it be also in the join line?

  499. pep.

    To configure the port you'll need ad-hoc support I would say

  500. serge90 has left

  501. serge90 has joined

  502. bear has joined

  503. Daniel has left

  504. Daniel has joined

  505. jubalh has joined

  506. serge90 has left

  507. serge90 has joined

  508. goffi has left

  509. Jeybe has left

  510. serge90 has left

  511. Jeybe has joined

  512. serge90 has joined

  513. serge90 has left

  514. serge90 has joined

  515. MattJ

    Anyone know of a client library (not web-based) that supports websockets?

  516. bear has left

  517. serge90 has left

  518. serge90 has joined

  519. mukt2 has left

  520. mukt2 has joined

  521. jubalh has left

  522. Shell has left

  523. SamWhited has left

  524. serge90 has left

  525. serge90 has joined

  526. Jeybe has left

  527. Jeybe has joined

  528. Jeybe has left

  529. Jeybe has joined

  530. serge90 has left

  531. serge90 has joined

  532. Link Mauve

    MattJ, nbxmpp, from Gajim.

  533. MattJ

    Ah nice, thanks

  534. serge90 has left

  535. serge90 has joined

  536. Jeybe has left

  537. Jeybe has joined

  538. serge90 has left

  539. serge90 has joined

  540. jubalh has joined

  541. eevvoor

    ok pep. the question was luckily just for curiosity.

  542. Shell has joined

  543. serge90 has left

  544. serge90 has joined

  545. pdurbin has left

  546. Jeybe has left

  547. Jeybe has joined

  548. serge90 has left

  549. serge90 has joined

  550. adiaholic_ has left

  551. adiaholic_ has joined

  552. serge90 has left

  553. serge90 has joined

  554. Jeybe has left

  555. Jeybe has joined

  556. serge90 has left

  557. serge90 has joined

  558. andrey.g has left

  559. Jeybe has left

  560. Jeybe has joined

  561. serge90 has left

  562. bear has joined

  563. serge90 has joined

  564. Jeybe has left

  565. Jeybe has joined

  566. SamWhited has joined

  567. SamWhited has left

  568. mukt2 has left

  569. serge90 has left

  570. Jeybe has left

  571. Jeybe has joined

  572. serge90 has joined

  573. serge90 has left

  574. serge90 has joined

  575. Shell has left

  576. Nekit has left

  577. Jeybe has left

  578. Jeybe has joined

  579. Nekit has joined

  580. bear has left

  581. serge90 has left

  582. serge90 has joined

  583. andrey.g has joined

  584. nyco has left

  585. jubalh has left

  586. Jeybe has left

  587. Jeybe has joined

  588. serge90 has left

  589. serge90 has joined

  590. Neustradamus has left

  591. nyco has joined

  592. goffi has joined

  593. jubalh has joined

  594. Neustradamus has joined

  595. Jeybe has left

  596. Jeybe has joined

  597. MattJ

    flow, just sent a mail regarding list-multi

  598. MattJ

    XEP-0004 forbids arbitrary values there

  599. serge90 has left

  600. MattJ

    Hmm, what do people think about a <comment> block in XEPs that isn't rendered by default?

  601. serge90 has joined

  602. Neustradamus has left

  603. Neustradamus has joined

  604. pep.

    Comment for whom to see?

  605. MattJ

    People working on the XEP

  606. pep.


  607. MattJ

    Potentially useful for detailed rationale, etc.

  608. pep.

    Sorry I read "block" and "XEP" and I made the wrong connection

  609. jonas’

    MattJ, <!-- ... -->?

  610. MattJ

    It would be nice if we /could/ render these though

  611. MattJ

    e.g. in a different colour

  612. pep.

    MattJ, I would prefer to render the rationale tbh :x

  613. jonas’

    I think detailed rationale should simply go in the document itself

  614. MattJ

    That could lead to a lot of noise

  615. MattJ

    I don't think XEP-0313 needs a detailed explanation of why it uses list-multi or text-multi

  616. pep.

    Do you have an example ?

  617. pep.

    Do you have an example?

  618. pep.


  619. MattJ

    That's just going to be noise for people trying to implement it

  620. jonas’

    MattJ, ah indeed

  621. jonas’

    just put it in <

  622. MattJ

    But for people working on the XEP, or curious in these decisions, it's valuable

  623. pep.

    Well that can go into a "rationale" section that people can skip

  624. jonas’

    just put it in <!-- .. --> I think

  625. MattJ

    No, I kinda want it inline

  626. leo has joined

  627. jonas’

    MattJ, so put it inline?

  628. Zash

    Oh but XEP-0122 lets you alter the behavior of list-multi

  629. jonas’

    (ah that was in reply to pep)

  630. leo has left

  631. Zash


  632. Zash

    Tremble before the tower of complexity!

  633. MattJ

    It would be nice for a HTML rendering with author notes visible

  634. Kev

    I agree that a 'real' block that's unrendered but renderable would be useful for quite a lot of things.

  635. MattJ

    and we can even render both versions on the site by default

  636. serge90 has left

  637. serge90 has joined

  638. MattJ

    Zash, aha, thanks

  639. Zash


  640. MattJ


  641. Zash

    Hm, views. Separate renditions / views for users, implementors, authors?

  642. MattJ

    Users? No thanks

  643. Zash

    User view = just a description of the feature + list of implementatinos

  644. MattJ


  645. Zash

    Becasue XEP == Feature now.

  646. flow

    MattJ, replied

  647. Kev

    MattJ: Oh, I was thinking of a JS toggle, rather than a different document.

  648. flow

    MattJ, I also think the statement "text-multi is defined to be multiline" to be problematic. text-multi values appears to be explicitly *not* multi lines, as should not contain newlines

  649. MattJ

    Either works for me (Zash's solution doesn't even use JS)

  650. Zash

    Kev, `<details>` !

  651. MattJ

    "The field enables an entity to gather or provide multiple lines of text. ***"

  652. Kev

    Whatever :)

  653. MattJ

    "an application that receives multiple <value/> elements for a field of type "text-multi" SHOULD merge the XML character data of the value elements into one text block"

  654. Zash

    What happens if you put newlines in the individual <value>s?

  655. Kev

    MattJ: It's fine isn't it? We can use list-multi, just have to have the server generate a form that has all the IDs in it so the client can then choose from them.

  656. Zash

    Kev: Perfect!

  657. Zash

    How many unique IDs do you think the MUC logs of this chat room has?

  658. flow

    MattJ, that requirement appears strange to me. but irregardless text-multi should be a good fit?

  659. Shell has joined

  660. serge90 has left

  661. Kev

    text-multi is just a way of providing a multi-line text field, it's not multiple text entries.

  662. serge90 has joined

  663. MattJ

    Other than I expect any sensible library is going to return a multiline string from this form, it's "ok"

  664. Kev

    So I think that's a worse fit than list-multi, TBH.

  665. MattJ

    As long as newlines aren't allowed in message ids...

  666. MattJ

    list-multi does feel cleaner

  667. Jeybe has left

  668. Jeybe has joined

  669. Zash

    ``` <field var="archive-ids" type="list-multi" label="Archive IDs of messages to retrieve"> <validate xmlns="http://jabber.org/protocol/xdata-validate" datatype="xs:string"> <open/> </validate> </field> ```

  670. goffi has left

  671. flow

    MattJ> Other than I expect any sensible library is going to return a multiline string from this form, it's "ok" definetly, although low layers of an API would (and should) probably allows access to the individual values

  672. Shell has left

  673. Shell has joined

  674. APach has left

  675. flow

    ahh the requirement above explicitly talks about "an application", everything is fine then ;)

  676. MattJ

    You certainly could get that info in Prosody, for example. But it's a mess, you have to then access that field differently to all the others that are parsed, validated and returned automatically

  677. MattJ

    Would be easier just to split by newline again

  678. MattJ

    But ugly

  679. MattJ

    I think I'm going with list-multi

  680. waqas has joined

  681. Zash

    Luckily we don't have any validation that values are among the offered options \o/

  682. serge90 has left

  683. serge90 has joined

  684. Zash

    Haha, maybe IDs should be JIDs, then we use jid-multi :D

  685. serge90 has left

  686. serge90 has joined

  687. mukt2 has joined

  688. lovetox

    hm if list-multi says a client is not allowed to add new options

  689. serge90 has left

  690. lovetox

    but we never receive a form from the server in the MAM spec anyway

  691. lovetox

    so tecnically we dont add new values

  692. serge90 has joined

  693. bear has joined

  694. Zash

    What's about the iq-get?

  695. MattJ

    You do receive a form (but you don't have to)

  696. lovetox

    ah yeah you can request it i remember

  697. Zash

    You receive the form from the allmighty XEP author when you read the holy text.

  698. serge90 has left

  699. serge90 has joined

  700. mukt2 has left

  701. Jeybe has left

  702. serge90 has left

  703. krauq has left

  704. flow

    I think the fact that you can retrieve a (blank) gather form for MAM query options is a strong argument against list-multi, since you usually would have that field populated in gather forms

  705. serge90 has joined

  706. krauq has joined

  707. bear has left

  708. serge90 has left

  709. serge90 has joined

  710. Kev

    Maybe it shouldn't be a list at all, but just a single value? :)

  711. MattJ

    At which point we might as well stick with the current non-form proposal

  712. serge90 has left

  713. serge90 has joined

  714. adiaholic_ has left

  715. adiaholic_ has joined

  716. mukt2 has joined

  717. MattJ

    <p>A special note about the 'ids' field: this field is of type 'list-multi' which typically is used to allow the client to select from a provided list of options. In this form the list of all possible ids MUST NOT be provided by the server, as it is likely to be extremely large. Instead the server MUST include a &xep0122; &lt;validate/&gt; element that signals the list is open to arbitrary values provided by the client.</p>

  718. serge90 has left

  719. serge90 has joined

  720. pdurbin has joined

  721. Kev

    Seems pragmatic.

  722. nyco has left

  723. serge90 has left

  724. serge90 has joined

  725. pdurbin has left

  726. Mikaela has left

  727. Mikaela has joined

  728. Mikaela has left

  729. Mikaela has joined

  730. serge90 has left

  731. serge90 has joined

  732. mukt2 has left

  733. Mikaela has left

  734. Mikaela has joined

  735. Shell has left

  736. serge90 has left

  737. serge90 has joined

  738. flow

    Kev> Maybe it shouldn't be a list at all, but just a single value? :) Wouldn't that be an indicator that there is a hole in xep4 which we may want/need to fill?

  739. mukt2 has joined

  740. flow

    ahh, TIL <open/> from xep122 is actually defined as what we need

  741. serge90 has left

  742. serge90 has joined

  743. j.r has left

  744. nyco has joined

  745. flow

    must the <open/> only appear on form retrieval or also on form submission?

  746. Zash


  747. Zash

    The entity you're submitting it to should know what the form looks like

  748. Zash

    so, sending them such metadata would be redundant

  749. flow

    yeah I know, I just wondered if there is some spec text on that

  750. Zash

    IIRC 0004 says that the basic type attrs are optional on submitting, same logic

  751. flow

    not sure if my spec laywer would agree to that, but yes ;)

  752. serge90 has left

  753. serge90 has joined

  754. bear has joined

  755. Zash

    20% of Council agrees :P

  756. andy has left

  757. andy has joined

  758. serge90 has left

  759. serge90 has joined

  760. goffi has joined

  761. serge90 has left

  762. serge90 has joined

  763. goffi has left

  764. goffi has joined

  765. j.r has joined

  766. serge90 has left

  767. serge90 has joined

  768. stpeter has joined

  769. stpeter has left

  770. xecks has left

  771. xecks has joined

  772. bear has left

  773. serge90 has left

  774. serge90 has joined

  775. eevvoor

    > not sure if my spec laywer would agree to that, but yes ;) layer or lawyer flow ;)

  776. flow

    not sure if my spec lawyer would agree to that, but yes ;)

  777. serge90 has left

  778. serge90 has joined

  779. serge90 has left

  780. serge90 has joined

  781. jubalh has left

  782. serge90 has left

  783. serge90 has joined

  784. serge90 has left

  785. serge90 has joined

  786. serge90 has left

  787. serge90 has joined

  788. Steve Kille has left

  789. serge90 has left

  790. serge90 has joined

  791. Steve Kille has joined

  792. j.r has left

  793. j.r has joined

  794. mukt2 has left

  795. bear has joined

  796. serge90 has left

  797. mukt2 has joined

  798. werdan has joined

  799. jubalh has joined

  800. mukt2 has left

  801. mukt2 has joined

  802. pdurbin has joined

  803. jubalh has left

  804. pdurbin has left

  805. lovetox has left

  806. mukt2 has left

  807. Wojtek has joined

  808. sonny has left

  809. flow

    Friendly (and probably only) reminder that you can suggest characters for the XSF to adopt by the end of the week at: https://wiki.xmpp.org/web/Adopt-a-Character or by writing me an email: flo@geekplace.eu

  810. sonny has joined

  811. adiaholic_ has left

  812. adiaholic_ has joined

  813. Ge0rG


  814. arc has left

  815. arc has joined

  816. jubalh has joined

  817. pep.

    <💡/> 4 chars

  818. xecks has left

  819. Jeybe has joined

  820. Zash

    <🗪 xmlns=💡/>

  821. Zash

    `<💬 xmlns=💡 type=🗫><body>Nobody said XML element names are restricted to ASCII</body></💬>

  822. pep.

    missing a >

  823. pep.

    Or is that my terminal

  824. Zash


  825. lovetox has joined

  826. xecks has joined

  827. lovetox has left

  828. bear has left

  829. nyco has left

  830. arc has left

  831. arc has joined

  832. rion took a look on the calendar. Doesn't seem to be 1st..

  833. Nekit has left

  834. david has left

  835. david has joined

  836. APach has joined

  837. mukt2 has joined

  838. Steve Kille has left

  839. Neustradamus has left

  840. Neustradamus has joined

  841. Steve Kille has joined

  842. waqas has left

  843. waqas has joined

  844. Syndace

    Zash, MattJ: if you want to have a look at what I came up with for Quick Response: https://github.com/xsf/xeps/pull/933

  845. Syndace

    no idea if this is the formally correct way to re-propose a protoXEP that has been rejected before 😀

  846. pep.

    As an editor I am not sure how to deal with this :p

  847. MattJ

    Let's just say it is

  848. Syndace

    Technically you can treat it as a new protoXEP, it has a different name and 99% different content

  849. pep.

    Do we need an ACK from the original author

  850. krauq has left

  851. krauq has joined

  852. MattJ

    I have some feedback but can't type it up right now

  853. bear has joined

  854. Syndace

    okay I converted it to a draft pr for now

  855. pep.

    Syndace, thanks

  856. mukt2 has left

  857. Nekit has joined

  858. aj has joined

  859. lorddavidiii has left

  860. lorddavidiii has joined

  861. bear has left

  862. aj has left

  863. lovetox has joined

  864. jubalh has left

  865. j.r has left

  866. goffi has left

  867. goffi has joined

  868. jubalh has joined

  869. goffi has left

  870. goffi has joined

  871. j.r has joined

  872. goffi has left

  873. goffi has joined

  874. bear has joined

  875. goffi has left

  876. goffi has joined

  877. pdurbin has joined

  878. goffi has left

  879. goffi has joined

  880. mukt2 has joined

  881. goffi has left

  882. goffi has joined

  883. pdurbin has left

  884. Zash

    pep., enough of an ack? https://github.com/xsf/xeps/pull/933#issuecomment-616742618

  885. pep.


  886. Zash

    Did I spell Syndace correctly this time?

  887. pep.


  888. APach has left

  889. Zash

    Wrote "Syndance" first :)

  890. Syndace

    Hahaha I like it :D

  891. pep.

    Syndace, poke me when you remove the WIP state and it's ready to merge

  892. pep.

    Or another editor

  893. Syndace

    Sure, thanks

  894. Zash

    I suppose you want to add your own version block as well

  895. Zash

    Oh wait, you did

  896. Zash

    Confused by indentation. nm me.

  897. Syndace


  898. Zash

    Not sure you want to delete the old one tho, since that was a thing that was proposed

  899. Syndace

    theoretically protoxeps are supposed to be version 0.0.0 anyway afaik

  900. Zash

    Oh no!

  901. pep.

    I'm always so confused by our versioning scheme

  902. pep.

    I don't like it

  903. Syndace

    but I'll wait for an editor to tell be that :)

  904. bear has left

  905. Jeybe has left

  906. Vaulor has left

  907. Seve has left

  908. Seve has joined

  909. Vaulor has joined

  910. Shell has joined

  911. APach has joined

  912. Jeybe has joined

  913. stpeter has joined

  914. stpeter has left

  915. pep.

    XEP-0001 doesn't actually say protoXEPs are not versioned

  916. pep.

    It just seems to say a XEP (experimental) gets published with version 0.1

  917. Syndace

    oh, I think I read something in the readme of the xeps repo

  918. pep.

    Maybe the xep-README thing contains useful info

  919. Wojtek has left

  920. pep.

    2§ XEP Editor Responsabilities: 11. List administration ??

  921. pep.

    "Set the version to 0.0.1."

  922. pep.

    for a protoXEP

  923. pep.

    I would like to note that this file mentions a mercurial repo for XEPs :o

  924. Syndace


  925. Zash

    I think I still have a clone of that repo, from ... bitbucket? or whatsitcalled?

  926. jubalh has left

  927. Jeybe has left

  928. xsf has joined

  929. Jeybe has joined

  930. pep.

    Does anybody still have access to editor@xmpp.org?

  931. Wojtek has joined

  932. Syndace

    Zash: do you have any feedback on the content? Did I about grasp what we discussed yesterday?

  933. Zash

    I got distracted before I got that far :)

  934. bear has joined

  935. Jeybe has left

  936. Jeybe has joined

  937. andrey.g has left

  938. MattJ

    Ok, I'm here for a few

  939. Syndace


  940. Syndace


  941. MattJ

    Syndace, a big one I'd like to comment on is internationalized responses

  942. MattJ

    I think it came up while discussing the previous protoXEP, and it also has come up for me again in Hats, and possibly elsewhere too

  943. Syndace

    hmm yes, I thought it would be weird if you see a frensh message and a frensh button but then on click suddenly there is an english "yes"

  944. MattJ

    and we had a big discussion a while back about multiple <body> tags

  945. Syndace

    (oh boi, french I mean)

  946. MattJ

    I think what I'm converging on is the approach that generally each interaction is confined to one language

  947. MattJ

    and this can be indicated by xml:lang for clarity

  948. DebXWoody has left

  949. Nekit has left

  950. MattJ

    A Spanish bot, or a multilingual bot in a Spanish MUC is just going to use Spanish for all interactions

  951. Syndace

    does the bot always know the preferred language of the recipient?

  952. Zash

    If it's responding, it can know

  953. MattJ

    My argument is that yes, in practice it does

  954. Zash

    Dunno if you have bots initiating interactions ever

  955. MattJ

    We have basically never used the multiple xml:lang <body> thing, it's basically a lurking security issue at this point

  956. bear has left

  957. Zash

    💡️🤖️> Hello Zash, you haven't voted yet. Maybe you wanna do that now? Eh?

  958. MattJ

    It has many problems in practice, and I think it's good to keep things simple, and not add stuff just because we can

  959. MattJ

    I was planning hats (aka Badges, whatever) to offer translations, and I decided to drop it on similar grounds

  960. Syndace

    okay. So what would you propose? Remove all the xml:lang stuff and replace the i18n considerations with "if the entity aims to support multiple languages, it should do so by detecting the preferred language of its communication partner and then using only that one language"?

  961. Zash

    Syndace, not remove, but only allow one

  962. Zash

    xml:lang is still allowed everywhere in theory

  963. MattJ

    It should have (optional?) xml:lang

  964. MattJ

    But not support for multiple

  965. Zash

    Hm, multilingual bot interactions, would that be an informational XEP?

  966. Zash

    Actually applies to servers

  967. pep.

    "MattJ> A Spanish bot, or a multilingual bot in a Spanish MUC is just going to use Spanish for all interactions" I'm sorry to be the exception again, but it happens quite often in two different MUCs I'm in that it's not the case :(

  968. pep.

    There's no "one language defined"

  969. pep.

    poezio@ is such an example

  970. MattJ

    pep., I'm fine with that

  971. MattJ

    But you wouldn't deploy a Spanish-speaking bot in that room, would you?

  972. pep.

    I could deploy a french + english bot

  973. Zash

    MUC deos have that "primary langage" field that we're using now :)

  974. MattJ

    I don't think in this case you are the exception

  975. MattJ

    In reality we all speak different languages, but each room does tend to have a primary (and sometimes a preferred secondary)

  976. pep.

    and that bot would not just use french or english, it'd used french and english

  977. MattJ

    I really don't think it harms anyone for the bot to be just like anyone else

  978. MattJ

    It can

  979. MattJ

    But it can't mix both in one message

  980. pep.

    in one <message>?

  981. MattJ


  982. Syndace

    my thought process was that bots are probably the only real use-cases of a message with multiple bodies in different languages

  983. pep.

    why not, I'm not sure I get it

  984. Zash

    Normala människor don't mix olika språk in the same meddelande!

  985. Syndace

    but if the multiple bodies is a think you'd rather see die (which I can totally understand) then I will remove the support

  986. Zash

    pep., most bot interactions is responding to humans, right? just respond in the same language and things should be fine.

  987. Zash

    so !ping would respond pong and !shtrudel would reply kartoffel

  988. Zash

    easy peasy

  989. pep.


  990. pep.

    That's fine when answering maybe

  991. pep.

    Not when initiating

  992. pep.

    (I'm only reading now what's being said above)

  993. Syndace

    anything else matt? 🙂

  994. MattJ

    If you're in any doubt, you should dig up the previous xml:lang discussions

  995. pep.

    which ones!!

  996. MattJ

    Yes, there was something else, let me check

  997. pep.

    Somebody(tm) should write an informal XEP about @xml:lang

  998. pep. adds that to XEP ideas

  999. MattJ

    Oh, I think it was just the naming "allowed response" - it makes it sound like other responses are disallowed

  1000. Syndace

    well they probably are

  1001. Zash

    Oh no

  1002. Syndace

    if you reply "lol maybe" to memberbot it won't be happy

  1003. MattJ

    I don't think that's necessarily the case

  1004. Zash

    My freedom to reply "lol maybe"!!!

  1005. MattJ

    Providing shortcuts for common responses, but also allowing freeform responses is definitely a valid use case

  1006. pep.

    Zash, and the bot's freedom not to listen to your "lol maybe"!

  1007. Syndace


  1008. Zash

    pep., mutual freedom, mmmmmmmm

  1009. MattJ

    and for legacy client's it's a reality you'll have anyway

  1010. Syndace

    taking ideas for alternative element names :D

  1011. MattJ

    Oh no, that's the hard part!

  1012. Syndace

    right xD

  1013. Syndace

    maybe just response, there should be no ambiguity as we're using a namespace anyway

  1014. MattJ

    Yeah, that sounds good

  1015. Zash


  1016. Max has left

  1017. moparisthebest

    Next you'll be asking about the proper first array index and the lua devs will pipe up and it'll be all out war!

  1018. pep.

    https://wiki.xmpp.org/web/XEP_ideas/@xml:lang !

  1019. Max has joined

  1020. flow

    https://xmpp.org/extensions/xep-0045.html#roomconfig: really stupid question: do I have to submit all fields with values or just the changed fields with their new values?

  1021. MattJ

    flow, "yes" ;)

  1022. flow

    ahh the universally valid answer

  1023. MattJ

    flow, as far as I'm concerned you can just submit the changed fields, but I don't think it is actually defined what happens to the rest

  1024. pep.

    the latter?

  1025. pep.


  1026. MattJ

    Other than "default"

  1027. MattJ

    which for Prosody at least means "whatever it currently is"

  1028. flow

    smack currently sends all values, but I see a possiblity to save bytes on the wire!!!

  1029. MattJ

    Yeah, I think it's sensible

  1030. MattJ

    But I can't say that another server won't reset all the missing fields to their defaults

  1031. flow

    lets see what ad-hoc commands do…

  1032. flow

    hmm ex11 and ex12 in xep50 not helpful

  1033. murabito has joined

  1034. flow

    hmm ex11 and ex12 in xep50 are not helpful

  1035. flow

    is that really not defined? :(

  1036. nyco has joined

  1037. andrey.g has joined

  1038. MattJ

    Syndace, I'm also unsure about whether responses or actions should be limited to the previous message

  1039. MattJ

    Responses, probably, I guess... since there is no id

  1040. MattJ

    But actions, a bot could (and probably would) put a sensible unique id on each action, that's up to the bot

  1041. Syndace

    I obviously had the bot use-case in the back of my mind and I think having responses to messages that are not the last would probably only cause confusion and nothing else

  1042. MattJ

    If I push some more commits to the same PR, it might cause another notification, but the 'merge' button could have the same id

  1043. pep.

    You're starting to comfort me that these may be two different use-cases

  1044. MattJ

    If it's a textual response then yeah, it's not clear what it's replying to

  1045. Syndace

    for actions it's not limited to the last message but the last message that contains actions. A bot _could_ obviously assign unique ids to every action it ever sends out, but that's not guaranteed and if it doesn't things become weird

  1046. MattJ

    (without the in-reply-to thing we discussed)

  1047. MattJ

    If it doesn't, that's the bot's responsibility. I just gave an example of non-unique ids being fine

  1048. MattJ

    It's likely worth mentioning, but I don't think it is necessary to forbid actions on older messages

  1049. pep.

    I also find this weird

  1050. Syndace

    but if there's a new message with a new merge button, do you think it's valuable to have the change to trigger the action on the old message?

  1051. pep.

    I wouldn't forbid it

  1052. Syndace


  1053. pep.

    I don't think we can do much about this until threads or whatever other magical solution

  1054. pep.

    If there's an id and I support it, I'll use it

  1055. pep.

    if it's between people, they'll figure it out

  1056. Syndace

    > I don't think we can do much about this well what we can do it say that only the newest actions should be accessible

  1057. pep.

    Syndace, what if they're different?

  1058. pep.

    Why would you prevent this

  1059. Syndace

    but I can remove that restriction and add a note that this should be kept in mind

  1060. pep.


  1061. pep.

    "There might be cases where.. *handwave-maybe-somebody-will-figure-out-a-solution*"

  1062. Syndace

    yeah right, will do that

  1063. pep.

    And hope you get feedback from implementing clients

  1064. Syndace

    yeah. first of all I hope it gets accepted as experimental 🙂

  1065. Syndace

    the changes we're discussing right now are already too advanced for a protoxep that might just get rejected 😀

  1066. pep.


  1067. MattJ

    It would be a bit weird if two PRs came in and only the second one had a merge button

  1068. pep.


  1069. Syndace

    hmm that's true

  1070. pep.

    Maybe the merge button can actually be "merge !234" and "merge !345"

  1071. Syndace

    yes I'm convinced, for actions it doesn't make sense to limit the messages just because the dev of a bot might mess up the ids

  1072. werdan has left

  1073. Max has left

  1074. bear has joined

  1075. Max has joined

  1076. pdurbin has joined

  1077. arc has left

  1078. arc has joined

  1079. jubalh has joined

  1080. Tobias has left

  1081. pep.

    I find the current experimental XEP updating flow a bit weird. An author pushes changes, doesn't open any thread on standards (they're the author after all, they can just push things), I have feedback that I won't be able to get in before it gets pushed. Changes get pushed, new revision, my feedback is heard, another revision

  1082. pep.

    We could have skipped an editor roundtrip in between

  1083. pep.

    I kinda prefer what's happening with MAM atm

  1084. gav has left

  1085. mukt2 has left

  1086. Mikaela has left

  1087. pdurbin has left

  1088. Mikaela has joined

  1089. gav has joined

  1090. mukt2 has joined

  1091. Nekit has joined

  1092. wurstsalat has left

  1093. wurstsalat has joined

  1094. adiaholic_ has left

  1095. adiaholic_ has joined

  1096. pep.

    What would be a use-case for allowing registering accounts (IBR2) after bind

  1097. krauq has left

  1098. murabito has left

  1099. murabito has joined

  1100. adiaholic_ has left

  1101. Jeybe has left

  1102. Jeybe has joined

  1103. wurstsalat has left

  1104. Jeybe has left

  1105. Jeybe has joined

  1106. murabito has left

  1107. murabito has joined

  1108. mano has joined

  1109. mano has left

  1110. arc has left

  1111. arc has joined

  1112. Jeybe has left

  1113. arc has left

  1114. arc has joined

  1115. Jeybe has joined

  1116. robertooo has left

  1117. Jeybe has left

  1118. krauq has joined

  1119. jubalh has left

  1120. mukt2 has left

  1121. Syndace

    Quick Response updated, here's the rendered version: https://syndace.com/xeps/inbox/quick-response.html

  1122. Syndace

    pep. I'll remove the WIP now I guess, this should be ready to be voted on, even if it's not perfect yet

  1123. pep.

    gogo, I'm merging stuff nao

  1124. Syndace


  1125. Zash

    Nit: In general, data that's to be considered "content" ought to be in text elements, and attrs should be used for more metadata-ish things.

  1126. Syndace

    ah interesting, was wondering when to use which

  1127. Zash

    I forget if this is mentioned in some XEP but otherwise it's a general XML guideline thing.

  1128. pep.

    I'm unsure if buttons should be removed from the inbox though

  1129. Zash


  1130. Syndace


  1131. Mikaela has left

  1132. Zash

    Seems a weird thing to do

  1133. Syndace

    If this should be seen as a totally new protoXEP, buttons should probably not be removed. If this is seen as a rework of buttons, then it _os_ buttons

  1134. Syndace

    If this should be seen as a totally new protoXEP, buttons should probably not be removed. If this is seen as a rework of buttons, then it _is_ buttons

  1135. Syndace

    I mean, locally I didn't `rm` buttons but I `mv`ed buttons to quick-response 😀

  1136. Zash

    This is why working on protoXEPs is generally discouraged

  1137. pep.

    Zash, how do you rework refused XEPs?

  1138. pep.

    To repropose them once feedback is integrated

  1139. Zash

    Why couldn't that be done in experimental?

  1140. pep.

    Don't ask me, I'm not part of council rejecting stuff :p

  1141. pep.

    Don't refuse protoXEPs, people wouldn't have to work on them :P

  1142. Zash

    I wasn't on council then

  1143. pep.


  1144. Syndace

    can the author of a rejected protoXEP ask the editor to remove that rejected protoXEP from inbox?

  1145. mimi89999 has left

  1146. Syndace

    If so I'd propose that Zash just formally asks pep. to remove buttons and we're good 😀

  1147. Zash

    I'd say leave it. It was voted on, it's good to be able to go back and see what that was.

  1148. Syndace

    fair enough

  1149. pep.

    Syndace, can you do that? unrm it

  1150. Syndace

    on it

  1151. pep.


  1152. pep.

    Zash, on a related note, I want to work on ToS (inbox/tos.html) and if possible keep the name, how to do? :p

  1153. Zash

    oh glob

  1154. Syndace

    there we go, feel free to squash obviously

  1155. Syndace

    hmm now I wonder whether I should remove all traces of buttons from quick-response

  1156. Syndace

    like old version blocks and zash as author

  1157. Zash


  1158. Syndace

    whatevs, if that's not an editorial issue leave it at that

  1159. Zash

    Let's not try to determine if this constitutes an original work or a derived work.

  1160. pep.

    I'm fine with that I've got a signed message from the original author

  1161. Syndace

    nah it's cool, feel free to merge now

  1162. Syndace

    I hope you don't have to wait for the pipeline 😀

  1163. pep.

    I do, to update xmpp.org at least

  1164. Zash

    > this is not always the case due to reasons

  1165. Shell has left

  1166. Shell has joined

  1167. goffi has left

  1168. mimi89999 has joined

  1169. lorddavidiii has left

  1170. Shell has left

  1171. Shell has joined

  1172. paul has left

  1173. pdurbin has joined

  1174. xecks has left

  1175. xecks has joined

  1176. gav has left

  1177. pdurbin has left

  1178. Nekit has left

  1179. eevvoor has left

  1180. j.r has left

  1181. j.r has joined

  1182. j.r has left

  1183. j.r has joined

  1184. andy has left

  1185. xecks has left

  1186. andy has joined

  1187. Neustradamus has left

  1188. Neustradamus has joined

  1189. aj has joined

  1190. Neustradamus has left

  1191. aj has left

  1192. debacle has left