Hi,

While I am all for gathering feedback, I'd like to remind that the purpose of a last call is to advance the status of the specification. Both XEPs can't be advanced without also advancing some other XEPs they depend on.

Specifically about XEP-0385, I'd like to point out that for what I know, the specification diverts from what is implemented in the wild and from the examples in itself: The normative text does not describe the XEP-0372 <reference> container element around the XEP-0385 <media-sharing> and even the references inside the XEP-0385 <sources> element are not described in the normative part to use XEP-0372.

While implementations (for what I know) do mandate the <reference> element around the <media-sharing> they often don't support the begin/end attribute shown in the example. Some implementations do allow the uri attribute of the XEP-0372 <reference> to be set and will interpret it as a download source for the file. Many (all?) implementations only support a single source uri and many (all?) don't support the XEP-0358 file retrieval defined in XEP-0385. Some implementation will even support no uri being present on either the outer <reference> or the <reference> inside <sources> for as long as an appropriate oob tag is present. Finally, it is unclear if sending multiple media files within a single message is intended to be supported by XEP-0385, but if it is (which I personally would have assumed, based on being able to have <reference> begin/end attributes for multiple parts of the message body), I doubt that implementations do have support for it.

Marvin

On Sat, 2026-04-04 at 23:15 +0200, Philipp Hörist wrote: