More feedback; Thanks to zinid for catching this. XEP 405 2.4 Client Determines MIX Capability of Local Server
First of all I think that the feature should be announced on the account not on the server because we make all requests to the account as well. Second of all the example 3 isn’t correct in itself. The request is made to the account (indicated by omitting the to) but the response is coming from the server. So I think the text should be fixed to clearly indicate that the feature is annouced on the account and the response in the example should be fixed to not have a from. (or from=bare jid of the account) cheers Daniel Am Fr., 30. Nov. 2018 um 09:08 Uhr schrieb Daniel Gultsch <[email protected]>: > > Hi, > > As promised in the other thread here are some notes in no particular order > > > A Nick MAY be associated with a participant, which provides a user-oriented > > description of the participant. The nick associated with the user is stored > > in a <nick/> child element of the <participant/> element. The nick for each > > channel participant MUST be different to the nick of other participants > > (where nicks have been assigned). > > That paragraph basically repeats the last two sentences in the prior > paragraph, no? > > Example 24 in MIX > > <retract id='123456#[email protected]'/> > > I believe that should read <retract id="123456"/> _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
