On Mon, Oct 16, 2017, at 15:30, Florian Schmaus wrote: > So the case for BMH are things like > - Bots sending potential large status information, where there's a > desire to bring some structure into that information by using a markup > language
In this particular case it seems like we'd be creating a huge potential for incompatibility between clients. If half the worlds bots support restructured text and half support markdown, certainly clients only work well with certain bots. I'd be curious to hear a bit about how that could be mitigated if you have anything in mind. > - Bridges sending textual content which is already formatted using a > certain markup language to an XMPP client (guess who is currently > writing on a discourse to XMPP bridge *cough* *cough*) In this case, what do you expect the client or service receiving the message from the bridge to do with it? Would it render the markup generated by Discourse? In that case, see my previous question about compatibility and fragmentation among clients. —Sam _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
