Re: [Standards] Fixing XEP-0066 (Out of Band Data)

Am Freitag, den 23.10.2020, 15:04 + schrieb Tedd Sterr: > (This is tangential to Dave's thread, but I didn't want to hijack > that, hence a new one.) > > There may be some argument to include the url in the body anyway for > backwards compatibility, but given the XEP is over 14 years old and

Re: [Standards] Fixing XEP-0066 (Out of Band Data)

> FWIW at least one popular client will happily accept messages with an > x-oob URL and *no* body. What it (currently) won’t accept is 'mixed' > content with body != x-oob. The XEP clearly explicitly allows them to be different - indeed, it's expected they are different - so if an implementation

Re: [Standards] Fixing XEP-0066 (Out of Band Data)

Am Fr., 23. Okt. 2020 um 15:06 Uhr schrieb Tedd Sterr : > For the message method, I expect what happened was that at least one popular > client, rather than leave the body empty, inserted the content of the url > element into the body, and then others did the same, so now that has become a >

Re: [Standards] Council Minutes 2020-10-21

On 10/23/20 3:31 PM, Tedd Sterr wrote: *4a) MR !22 (XEP-0118: add composer, date, genre, language, lyricist, and performer tags; make rating optional)* - https://gitlab.com/xsf/xeps/-/merge_requests/25 Zash notes that XEP-0118 is Draft and the

[Standards] Fixing XEP-0066 (Out of Band Data)

(This is tangential to Dave's thread, but I didn't want to hijack that, hence a new one.) XEP-0066 defines two OOB methods for transmitting a URI to another recipient, an 'iq' method and a 'message' method. The iq method contains a 'url' element and an optional 'desc' element, and the

[Standards] Council Minutes 2020-10-21

https://logs.xmpp.org/council/2020-10-21?p=h#2020-10-21-b57e703886bf4bfe 1) Roll Call Present: Zash, Dave, Jonas, Daniel, Georg 2) Agenda Bashing No. 3) Editor's Update * Accepted XEP-0352 (Client State Indication) as Draft * Accepted XEP-0411 (Bookmarks Conversion) as Draft 4a) MR !22