On 2017/10/18, Jonas Wielicki wrote: > On Mittwoch, 18. Oktober 2017 10:57:19 CEST Sam Whited wrote: > > On Sat, Oct 14, 2017, at 07:06, Jonas Wielicki wrote: > > > (b) The ecosystem will fracture in islands of different, underspecified, > > > > > > plain-text markups put in <body/>. > > > > With (b) I think that's only likely to happen if the council decides to > > accept multiple different formatting specs as experimental and work on > > all of them in parallel. With my council hat on, I don't think that's > > likely to happen. > > I’m not confident that (b) is not going to happen. We are already seeing > implementations massively endorsing use of some type of markup in <body/>. > > But I see your point and I’m not as opposed as I was before. Thanks for > taking > the time to discuss this. > > > I would also be interested in a protactive measure to > > prevent this, say, starting a group to come up with requirements and > > eventually a spec for the next generation of formatted messages (this is > > something I was already planning on proposing, I'm sure many people who > > have spoken up on this list would be interested in working together > > towards a single spec). > > I am very much interested here. Count me in.
I don't want to shut all doors, but I have a hard time seeing what benefit this will bring. I only see wasted time and effort, and years of incompatibilities and tensions between clients. All of this to bring more or less the same product on the table, in a slightly modified way. We have one XEP that allows embedding rich content in messages, and that is XHTML-IM. I do agree that the XEP is not perfect, and that we can garnish it a bit more with security recommendations, etc., but in general it does the job. Replacing it with JSON or another specified format will certainly lead to the same kind of issues that start this thread. Yes, developers have to be careful, and no, not everybody is. Once we've reached this stage I don't think there is any point in discussing if it's going to be more or less prone to vulnerabilities. -- Maxime “pep” Buquet
signature.asc
Description: PGP signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
