25 Apr
2026
25 Apr
'26
7:35 a.m.
Hi,
I had already added the same note on the PR with the ProtoXEP before it
got merged. [1] My suggestion would be to add an additional value for
disposition that indicates that the file should not be provided as
downloadable attachment or displayed directly in the chat, but is only
used as a reference. That way still all of the logic of SFS remains
intact (like source attaching), which would potentially be broken or
with increased complexity if the <file-sharing> became a sub-element.
The problem of course being that SFS doesn't have this disposition yet
and there is no obvious compatible way to introduce it without a
namespace bump, so I haven't actually done it yet. Maybe this would be
a good point to ask for feedback or issue a last call, so we only have
to do a single namespace bump?
Marvin
[1] https://github.com/xsf/xeps/pull/1525#issuecomment-4201452130
On Sat, 2026-04-25 at 15:01 +0200, Philipp Hörist wrote:
Hi
With this syntax, a client which does not understand <markup> or does
not want to implement it, but understands File Transfers, cannot
differentiate that these files are only useful if markup is
supported, and belong to the markup.
So i think this would not be desirable. Somehow the SFS stuff needs
to be inside a markup namespaced element.
Regards
Philipp
On Fri, Apr 24, 2026, at 12:26, Daniel Gultsch wrote:
The XMPP Extensions Editor has received a
proposal for a new XEP.
Title: Emoji Markup
Abstract:
This specification leverages and (or ) to send custom emojis
URL: https://xmpp.org/extensions/inbox/emoji-markup.html
The Council will decide in the next two weeks whether to accept
this
proposal as an official XEP.
_______________________________________________
Standards mailing list -- standards(a)xmpp.org
To unsubscribe send an email to standards-leave(a)xmpp.org
_______________________________________________
Standards mailing list -- standards(a)xmpp.org
To unsubscribe send an email to standards-leave(a)xmpp.org