On Mittwoch, 18. Oktober 2017 17:28:31 CEST Jonas Wielicki wrote: > On Montag, 16. Oktober 2017 18:38:46 CEST Jonas Wielicki wrote: > > The XMPP Extensions Editor has received a proposal for a new XEP. > > > > Title: Body Markup Hints > > Abstract: > > This document specifies hints about the markup language used in > > elements. > > > > URL: https://xmpp.org/extensions/inbox/bmh.html > > So, I don’t like this.
Two points I’d like to add to my arguments: 1. Discovery doesn’t work in modern IM. It doesn’t work in MUC (with MSN), it doesn’t scale for MIX, it doesn’t work for one-on-one chats (due to Carbons and MAM). So it is not relevant for any applicability of the spec where normal IM clients are on the receiving end. 2. Putting textual markup in the <body/> is an accessibility problem, more so if the markup gets more complex (I can imagine that common markdown flavours (if used well! no inline URLs for example) would work well, because a11y tools might be used to such content from emails, but reStructuredText and CommonMark could be challenging). I mention that specifically because I’ve heard "Jabber clients are not accessible" from affected people more than once as a reason against using Jabber. We shouldn’t make it harder. kind regards, Jonas
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
