2018-01-19 19:13 GMT+01:00 Sam Whited <[email protected]>: > On Fri, Jan 19, 2018, at 11:55, Peter Saint-Andre wrote:
> I also hope they make it far easier to navigate the XEPs list. When I talk to > developers at events and mention XMPP one of the biggest complaints I get is > "oh, we looked at XMPP but there were multiple things to implement the > feature we wanted and we didn't know what to do" or "we saw the giant list of > extensions and didn't think we'd be able to implement all of them in a > reasonable time frame". Very much this. XMPP has the much deserved reputation of being an unnavigable jungle of extensions. The Compliance Suite is a good and overdue map for that jungle. Yes fancy tables like the compliance tester page that Sam mentioned can act as a guideline for server admins but I don't necessarily need the XSF for that. What the XSF should do with the compliance suite is to create a roadmap for developers who have never had any exposure to XMPP before. And I'm not even talking about Jabber developers who want to cater to the Jabber (federated) ecosystem but also developers who want to build their own systems from scratch. Like for example something we should have given to the RocketChat people before they went and created their own protocol. That's also the reason I'm against putting legacy stuff in there like vCards or private xml only because Pidgin still uses it. If a larger company like RocketChat wants to develop their own communication tools they don't necessarily care about being compatible with Pidgin. They just want to list of 'the right XEPs that combined provide a good IM experience for the user'. It's those companies and developers the XSF should focus on if they want XMPP to be used. Focusing our advertisement on the end user is a lost cause. cheers Daniel _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
