5 ms·

Seriously? Go check out Matrix or ActivityStreams, XMPP is actually much simpler.

• icedchai 5y ago
  The core of XMPP may be simple, but when you add in various XEPs, the complexity builds really fast. Just look at all this stuff: https://xmpp.org/extensions/ https://xmpp.org/extensions/
  • mst 5y ago
    One of the key points of the article we're discussing is to recommend a small curated set of XEPs. Just look at this relative lack of stuff: https://docs.modernxmpp.org/client/protocol/ https://docs.modernxmpp.org/client/protocol/
  • MattJ100 5y ago
    That's a growing list of documents over the course of XMPP. It doesn't really prove anything other than... XMPP has been around a long time, and people continue to develop it. People saying "look at all this stuff" is one reason the Modern XMPP project was born. To draw attention to the actually important things that developers need to read. The XSF receives a lot of submissions each year. Many of these proposals never make it past the "experimental" stage. Others are only applicable in certain domains (IoT, etc.). Over time some of these become widely adopted and progress through the standards process. Some do not. The XSF publishes annually the "compliance suite" which describes what clients and servers should be supporting in different areas: https://xmpp.org/about/compliance-suites.html https://xmpp.org/about/compliance-suites.html
  • southerntofu 5y ago
    That is true to some extent, however most of extensions listed there are not required or even recommended to implement useful clients/servers. It's just like if you took the list of RFCs using TCP/IP then said "ha! TCP/IP complexity builds really fast".