4 ms·
XMPP is a protocol. Slack's own RTM API is a protocol. It was claimed that the former cannot be extended but the later can be - which I argued is wrong. Now yo
by drdaeman 9y ago
XMPP is a protocol. Slack's own RTM API is a protocol. It was claimed that the former cannot be extended but the later can be - which I argued is wrong.
Now you're arguing about something completely different. It's not like it's a death sentence if some RTM API-consuming app is not capable of something - why does it suddenly becomes an issue when we switch protocol to XMPP?
- dmitriid 9y agoBecause Slack both develops the protocol, and provides apps for all platforms that support all features in this protocol. There’s exactly one XMPP client (Conversations for Android IIRC) that supports all the XMPP features (many of them in still experimental XEPs) that make it barely suitable for a modern mobile-heavy world, much less for anything else. So yes. When you say it’s developers’ problem to develop clients, it’s not. It immediately becomes the end-users’ problem.