3 ms·

Interoperability is arguably a hit to innovation. You start with just text messages, one company wants to add images, either (A) they have to push for a standar

Interoperability is arguably a hit to innovation. You start with just text messages, one company wants to add images, either (A) they have to push for a standard which takes years or (B) they add a non-standard extension. Then someone wants to add video clips, audio clips. Okay you say, older clients will skip those. But then someone wants to add threading, suddenly the entire format needs to change (see A and B above). Or, you just let each developer go as fast as they want to adding new features and/or selecting the ones they want (Apple putting adding in memoji that works by sending only the parameters, to very specific and copyright protected assets)

dane-pgp 5y ago
> Okay you say, older clients will skip those. Yes, that is what I say. > But then someone wants to add threading, suddenly the entire format needs to change Does it? If older clients don't want to implement threading, they can just receive the message bodies in the order they were posted. The old API should continue to work regardless of the extra metadata which one provider might be storing about it. Ideally, the host with the new feature would also add an "In response to #123456789:" line at the top of each message, so that users of the older clients can construct the threads in their mind (assuming that these older clients have been listing the IDs of the messages), but I don't think anyone's arguing that a service is breaking interoperability by failing to add such an affordance.