3 ms·
We need open protocols. Then let a thousand clients with different paradigms bloom
by tambourine_man 11y ago
We need open protocols.
Then let a thousand clients with different paradigms bloom
- vannevar 11y agoFor reasons that have never been entirely clear to me, chat has been reinvented more times than perhaps any other common Internet utility, and every time it is, there are no shortage of investors lined up for it. I think the cycle is largely driven by fashion, as youth get online and demand chat apps that are distinct (if not different in any meaningful functional way) from the existing ones.
- abraae 11y agoPerhaps because "chat" is the oldest human activity there is, so the idea that chat will ever be "done" is a chimera.
- vannevar 11y agoIf the medium is the message, then yes. A chat on ICQ is different from a chat on WhatsApp, because the app itself is part of the tribal identity. Like slang for existing words. So even if the functionality stays identical (and I would argue that it has, there's only so much you can do with a chat app), the cultural context of the app is different.
- tambourine_man 11y agoYes, I have thought about that as well many times. AIM, ICQ, Yahoo, MSN, Gtalk, WhatsApp, WeChat, iMessage… Perhaps because the hard part of creating an online chat is the network effect and scaling, everyone thinks they can have shot. With so many being thrown at the wall, eventually a lot of them stick.
- moonshinefe 11y agoI have the same thought. Heck, voice and video chat, file sharing, even primitive forms of 'integrations' (in the form of IRC bots and the like) have been around for many years at this point. I remember the Yahoo messengers and the MSN messengers of yore having a majority of the features that I see in the modern chat clients. It really perplexes me that these new chat services are apparently worth so much money. Yes, you took some trends and put everything into a convenient package. Is that alone worth billions of dollars? The actual technical innovation is minimal.
- andrey_utkin 11y ago> We need open protocols. You have that - SIP and XMPP. Please don't complain that they are complex and consist of a lot of documents, and have hard feature standartization path. It is the only possible way to openly evolve such systems - to publish serious writeups as documents on their own and have them discussed with criticism and then gradually adopted. And then you may end up with competing alternative implementations of same feature in different standards - that's also inevitable if the system is open. Because, would you be happy to have the same video codec everywhere, or you admire the fact that existing systems are flexible enough to interoperate with _different_ codecs?
- scrollaway 11y agoThe specs are not directly the problem in XMPP. They just amplify it. The real issue is XMPP does not directly solve the problems the authors of those chat apps deal with. Doing things properly requires writing XEPs and just a lot of hassle which a company building its own little Slack killer doesn't want to invest in, and doesn't have a reason to invest in either because none of the current ones support XMPP in the first place (the bootstrap problem). If you want to fix this, you have to do that work for them. You have to make XMPP a direct solution that says "Spin up this server, write a cool UI, and your product is done".
- andrey_utkin 11y ago> XMPP does not directly solve the problems the authors of those chat apps deal with Could you please recap which problems exactly? I though the problems which matter nowadays is independence from vendors, and, after that, reuse of existing software. > Doing things properly requires writing XEPs and just a lot of hassle which a company building its own little Slack killer doesn't want to invest in So they don't. But I think it's obvious that the point of current discussion is that owned networks are no more satisfactory because of lack of openness and freedom. XEPs and IETF RFCs are exactly for this purpose, so they are necessary. > If you want to fix this, you have to do that work for them. For whom "them"? Vendors of yet another IM service? I don't need any of them. > You have to make XMPP a direct solution that says "Spin up this server, write a cool UI, and your product is done". It is pretty much so nowadays. You would be surprised how many commercial messaging systems run XMPP software internally, and how much building up the solution is close to what you've said.