XSF Discussion - 2018-07-25

  1. jonasw

    SamWhited: you win the bet with "interesting challenge"

  2. Seve/SouL

    Congrats :)

  3. Seve/SouL

    Did you post it?

  4. jonasw

    no

  5. pep.

    For once it's not xmpp bashing, that's good

  6. Ge0rG

    hackernews love pointless brain exercises.

  7. Ge0rG

    jonasw: you should add the Jeff Goldblum quote to the testimonials

  8. jonasw

    maybe

  9. jonasw

    -EBUSY though

  10. jonasw

    oh my god why are people sending pull requests against xmpp-echo-bot

  11. Ge0rG

    jonasw: somebody woken up the dragon

  12. Holger

    Finally a successful XMPP project.

  13. edhelas

    and in 3 months xmpp-echo-bot will support MIX

  14. jonasw

    it doesn’t even support MUC

  15. edhelas

    MUC is has been, all the cool kids are using MIX

  16. Andrew Nenakhov

    MIX is never be 😂

  17. Ge0rG

    jonasw: you could maybe get by by using GC1.0

  18. jonasw

    Guus, uh... about https://github.com/xsf/xeps/pull/579/files#diff-9661ef8d60d796f8a9156c049dba3a30R403

  19. jonasw

    this doesn’t make sense to me

  20. jonasw

    ahh, now it does

  21. jonasw

    enable ≠ resume

  22. jonasw

    nevermind

  23. jonasw

    Guus, sorry, another question: why do you use <conflict/> here? https://github.com/xsf/xeps/pull/579/files/aaf23bf79081c7e1efa6861e2217809a60e13ea1#diff-9661ef8d60d796f8a9156c049dba3a30R431

  24. jonasw

    this seems extremely confusing to me: 1. conflict doesn’t really signal an invalid value. I think the list consensus was more along the lines of <undefined-condition/> + an application-specific condition element ✎

  25. jonasw

    this seems extremely confusing to me: 1. conflict doesn’t really signal an invalid value. I think the list consensus was more along the lines of <undefined-condition/> + an application-specific condition element 2. conflict is used as error to signal that another connection is currently resuming the stream. this is ambiguous ✏

  26. flow

    + no stream management specific stream error

  27. flow

    https://github.com/xsf/xeps/pull/579/commits/aaf23bf79081c7e1efa6861e2217809a60e13ea1#r205162639

  28. Guus

    Jonasw, you might be right. Or not. I included it mainly as a byproduct of the list discussion. I'm going to remove all changes other than the one I care about personally (the r/a sync issue) in the interest of advancing _that_ change. Other changes can go in separate PRs.

  29. Guus

    But first, dinner.

  30. Yagiza

    About XEP-0280: Message Carbons...

  31. Yagiza

    It seems to be lacking of point about sending messages between own resources.

  32. jonasw

    Guus, but this is exatcly about your sync change

  33. jonasw

    I suspect you might’ve done a copy/paste error or something here

  34. Guus

    Jonasw, I (intended to) use conflict for a second, different situation to the r/a sync issue (which indeed should have undefined, not conflict).

  35. Guus

    I'm quite literally at a trampoline with my youngest. Can't fix it now.

  36. jonasw

    Guus, no worries

  37. Guus

    Wth

  38. Guus

    Indefinitely messed up a copy/paste there

  39. Guus

    https://xmpp.igniterealtime.org:7483/httpfileupload/b5fab7c9-cf37-46ff-965d-e35901087705/yOHexJ7eSPydqT1UmejwMQ.jpg

  40. Guus

    We progressed from trampoline to cocktails though. Might take while. 😉

  41. jonasw

    heh

  42. Guus

    As I wrote in a different MUC: should be fixed now.