XSF Discussion - 2017-02-24

  1. Ge0rG

    I just realized that the old and the new Carbons rules fail to address 0184 and 0333.

  2. Guus

    wiki-maintainers, could we have basic wiki markup functionality and templates?

  3. Guus

    simple references do not appear to work, even the ones that do not use templats.

  4. Guus

    It appears to be a matter of installing extensions: https://www.mediawiki.org/wiki/Extension:Cite#Installation

  5. MattJ

    Maybe we should bundle the roster into bind2

  6. waqas

    MattJ: Clearly a better idea would be a transaction construct ^^

  7. waqas

    <transaction> … stanzas … </transaction> :)

  8. Zash

    <iq type=set><transaction>...</transaction></iq>

  9. Ge0rG

    What would be the implications of allowing carbonation of body-less "normal" messages? Wasn't this recently discussed in the context of MAM?

  10. Tobias

    hmmm..carbonated messages

  11. Tobias

    sprinkling presences

  12. Ge0rG

    Tobias: 0% sugar, 100% copy.

  13. Zash

    Ge0rG: What kind of messages are you thinking of?

  14. Ge0rG

    Zash: specifically 0184, 0333. But it will probably affect many more.

  15. Tobias

    CSN?

  16. Zash

    Don't those two use type=chat?

  17. Zash

    Ge0rG: In the context of MAM, aren't the result messages type=normal with no <body>?

  18. Ge0rG

    'The default value of the 'type' attribute is "normal".' and I see no type= in 0184 nor 0333

  19. Zash

    -xep 184

  20. Bunneh

    Zash: XEP-0184: Message Delivery Receipts is (Draft, 2011-03-01) See: https://xmpp.org/extensions/xep-0184.html

  21. Ge0rG

    there is a value in cc'ing 0184 acks.

  22. Ge0rG

    like in cc'ing errors.

  23. Zash

    CC all the things

  24. Ge0rG

    if I sent a "hey, I'm on my way" from $desktop, I can see on $mobile whether it was delivered/bounced

  25. Ge0rG

    Zash: that's exactly why I'm asking.

  26. Zash

    Ge0rG: Doesn't look like 184 says anything about the type.

  27. Zash

    I'd find it sane to use the same type as the message being ack'd

  28. Ge0rG

    Zash: but you are no client developer.

  29. Ge0rG

    and I can't imagine client developers out there listening to The Word of Zash and therefore doing The Right Thing. At least I didn't.

  30. Zash

    Ge0rG: I am not. I think that's something mentioned in another XEP, which I think should be applied in more contexts.

  31. Ge0rG

    Zash: and then we'll end up with error-acks :>

  32. Ge0rG

    what other XEPs are using type=normal and have no body?

  33. mathieui

    W 13

  34. Tobias

    Zash, did you implement xep-0233 in prosody?

  35. Zash

    "implement"

  36. Tobias

    you reported people being happy :P

  37. Zash

    I made https://modules.prosody.im/mod_saslname.html

  38. Zash

    Whoever I made it for was happy.

  39. Zash

    Don't remember much else.

  40. Ge0rG

    so, which other protocols do use message type=normal without a body?

  41. MattJ

    KIND: message TYPE: normal NOT INSPECT: body LOG=This one: $(stanza:top_tag())

  42. Zash

    xeps-hg$ hg extdiff -r 'last(file("xep-0313.xml"))' -p $PWD/xepdiff | q https://q.zash.se/8629a78c4a3c.txt

  43. Zash

    Best part is that it produces a MIX diff

  44. Zash

    Earlier version was using wdiff, which doesn't like directories, so it picks one file to diff.

  45. Zash

    ah nm

  46. Ge0rG

    MattJ: can I apply that rule to the XEPs repository?

  47. Zash

    grep the examples

  48. Ge0rG

    Zash: for "<message"?

  49. Zash

    what

  50. Zash

    the

  51. Zash shakes fist in the general direction of make

  52. Zash

    https://q.zash.se/3f91f5ba68e7.txt

  53. Ge0rG

    Not quite the answer I hoped for, but thanks

  54. Zash

    https://q.zash.se/d07ea0aae5bc.txt

  55. Zash

    Why isn't 'chat' the default anyways?

  56. Flow

    Zash: because it's not normal

  57. Zash

    Messages of type chat are not normal. But in XMPP they are.

  58. Zash

    XMPP. Not even once.