XSF Discussion - 2019-10-04


  1. Link Mauve

    “16:13:14 MattJ> I don't think I have a test account on a server that has websockets atm”, you can create one at jabber.fr, our WebSocket endpoint is listed in our XEP-0156 file and record.

  2. Link Mauve

    board, thanks, I’ll fix the PR but not tonight, I’m a bit tired.

  3. vanitasvitae

    I just created a PR with new SCE changes 🙂 https://github.com/xsf/xeps/pull/838/

  4. vanitasvitae

    I also did some changes to JET and JET-OMEMO with SCE in mind https://github.com/xsf/xeps/pull/839/

  5. intosi

    Heh. Bug in 220. One of the error conditions specified is remote-connection-failed. This is not an error in the urn:ietf:params:xml:ns:xmpp-stanzas namespace.

  6. jonas’

    220?

  7. intosi

    xep-0220

  8. jonas’

    intosi, it is a stream error though

  9. intosi

    I know. But 220 tells us that the error in a db:result or db:verify MUST be in the stanza error namespace.

  10. intosi

    So either that MUST is a lie, or the error condition is an unfortunate relic of the 3920-era stream error replies to dialback issues.

  11. Guus

    What's the fastest way to draft a XEP? I don't think I've ever done that. :-S

  12. Kev

    Find something in inbox, copy it, edit it.

  13. Seve

    that ^ :)

  14. Guus

    How do I render the XML while editing?

  15. Kev

    xsltproc xep.xsl inbox/guus.xml > inbox/guus.html

  16. jonas’

    Guus, make build/inbox/xep-1234.html

  17. jonas’

    Guus, make build/inbox/inboxxepname.html

  18. jonas’

    (if your xep is at inbox/inboxxepname.xml)

  19. jonas’

    Guus, there is also xep-template.xml which is cleaner than most of what you find in the inbox

  20. Guus

    Call me an end-user, but I was hoping for more wysiwyg 🙂

  21. jonas’

    sorry, we don’t have wysiwyg

  22. jonas’

    I call that make and reload the browser tab usually ;)

  23. jonas’

    but I’m also a happy LaTeX user, so....

  24. Zash

    Guus: I have some markdown to xep scripts if you're interested

  25. jonas’

    Zash, could you PR those to the xeps repo as utils?

  26. Guus

    Zash that sounds interesting, given that there are tools that auto-convert markdown changes to output

  27. Kev

    I mean, there are XML editors that do the same, I think.

  28. Kev

    But I don't use one.

  29. Guus

    Maybe those exist for xslt too - Oxygen Author doesn't, it appears.

  30. Zash

    jonas’: I could, if someone reminds me in about 3 hours when I'm off work

  31. Guus

    I realize that we're wading into 'personal preference' territory here.

  32. Zash

    Guus: inotify and make in a loop?

  33. Guus

    Oxygen XML Author, CTRL-SHIFT-T.

  34. Guus

    that's what I'll try

  35. Guus

    It updates the same tab in a browser with the newly generated transformation result.

  36. Guus

    No-one asked for this information, but here it is.

  37. intosi

    If you happen to have a license, Oxygen XML * is a great tool.

  38. MattJ

    `inowait` + `make` + `devd --livereload` ==> automatic reload in the browser when you hit save in the editor

  39. jonas’

    `zsh: command not found: devd`

  40. MattJ

    https://github.com/cortesi/devd

  41. jonas’

    very interesting

  42. MattJ

    https://xmpp.org/uses/iot/testimonials.html - I chuckled

  43. jonas’

    oops :)

  44. Seve

    :(

  45. jonas’

    MattJ, can you create the registry-docker-base repository in https://github.com/xsf for me please?

  46. jonas’

    (and grant the editor team all the powers on it)

  47. jonas’

    well, or at least as many powers as editors have on xep-docker-base

  48. jonas’

    although I’ll still need Kev for the hub.docker.com things

  49. MattJ

    Sure. Just making lunch, so give me a moment

  50. Ge0rG

    MattJ: https://github.com/xsf/xmpp.org/issues/490

  51. MattJ

    jonas’: so sorry, got caught up in meetings and forgot. Here you go: https://github.com/xsf/registry-docker-base

  52. MattJ

    Ge0rG: great

  53. Ge0rG

    MattJ: somebody needs to do something

  54. MattJ

    as always

  55. pep.

    https://xmpp.org/extensions/xep-0001.html#submission wasn't there a change to 2119? I thought we moved to 8174

  56. Zash

    > Updated by: 8174

  57. pep.

    I know, that,s not my question

  58. pep.

    Do we only take into account CAPS keywords or all of them? The "Updated by" doesn't apply automagically right? Otherwise we'd have everybody using 6120/1 by now

  59. Zash

    But Updated doesn't mean it becomes obsolete

  60. Ge0rG

    pep.: there was a debate in council regarding that, some time earlier this year, IIRC. I don't remember the consensus, but I think it was something like "reviewing all the XEPs for lowercase terms and then changing them would be very much work, and probably not even change anything"