-
flow
hmm conversations.im gives me "504 - wait: Stream reset by peer"
-
flow
that just me?
-
Link Mauve
conversations@conference.siacs.eu is also down.
-
Link Mauve
And now it’s back.
-
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
-
Guus
to what extend is that correct and complete?
-
Guus
Is there any documentation around this?
-
Guus
(basically, to would be needed to facilitate ios)
-
Ge0rG
Guus: did you catch up with the Last Call thread?
-
Guus
no
-
Ge0rG
Guus: it might have the answers for that
-
Guus
tx
-
Ge0rG
I haven't catched up yet either
-
Guus
oh boy. Text in bold.
-
flow
when a user is involuntarily removed from a MUC, will the unavailable presence *always* contain a muc#user extension element?
-
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
-
pep.
If not I'm creating something on the wiki
-
pep.
Not sure if that goes in XEP-remarks
-
Zash
grep logs "someone should write a XEP about"
-
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 :)
-
MattJ
flow: I think that element is defined to be in all presence sent from a MUC, no?