XSF Discussion - 2020-04-17

  1. flow

    hmm conversations.im gives me "504 - wait: Stream reset by peer"

  2. flow

    that just me?

  3. Link Mauve

    conversations@conference.siacs.eu is also down.

  4. Link Mauve

    And now it’s back.

  5. Guus

    In context of XEP-0357 Push Notifications, I was told this: > Because of this an informal standard emerged which is not codified in the push xep: The push has to be a push summary and the last-message-body field has to be set for pushes that were triggered by a message stanza containing a body

  6. Guus

    to what extend is that correct and complete?

  7. Guus

    Is there any documentation around this?

  8. Guus

    (basically, to would be needed to facilitate ios)

  9. Ge0rG

    Guus: did you catch up with the Last Call thread?

  10. Guus


  11. Ge0rG

    Guus: it might have the answers for that

  12. Guus


  13. Ge0rG

    I haven't catched up yet either

  14. Guus

    oh boy. Text in bold.

  15. flow

    when a user is involuntarily removed from a MUC, will the unavailable presence *always* contain a muc#user extension element?

  16. pep.

    Is there already some kind of public XEP TODO? That is non-existing XEP ideas, or maybe past attempts (protoXEP) that haven't been accepted for which there's feedback that is to be gathered

  17. pep.

    If not I'm creating something on the wiki

  18. pep.

    Not sure if that goes in XEP-remarks

  19. Zash

    grep logs "someone should write a XEP about"

  20. pep.

    https://wiki.xmpp.org/web/Category:Specs I added this (the XEP_ideas/ pages). And then I saw XEP-Remarks/XEP-xxxx_Message_Reactions.. I'm happy with whatever people prefer, but I assume it'll stay this way as nobody will do it anyway :)

  21. MattJ

    flow: I think that element is defined to be in all presence sent from a MUC, no?