Hacker News new | ask | show | jobs
by ryandrake 471 days ago
> XMPP doesn't support all these (and future) content types, and it's difficult to ensure an XMPP client is rendering them appropriately. As such we've decided to sunset the XMPP Chat API.

This is such a lame excuse, and reveals how much they're control freaks. One of the main points of an open, federated protocol is that people can choose clients that behave the way they want and render things the way they want. "Oooohhh, we can't guarantee with an iron fist that our stupid 'stickers' render correctly on all clients, therefore we can't deal with it!"

This same mentality infests the web, and is why companies insist on slathering JavaScript into everything to force browsers to render their pages exactly as designed, rather than just letting the user agent serve the user's needs.