3 ms·
I think Chat is one of those core services, like Email that has standardized around one common standard. People use a wide variety of clients, and very differen
by SeoxyS 14y ago
I think Chat is one of those core services, like Email that has standardized around one common standard. People use a wide variety of clients, and very different uses from basic to power user needs. The reason most chat services fail is that even if they have fantastic mobile and web clients, they cannot provide the sheer range of clients needed for the entire range of use cases.
At Chartboost, we've tried pretty much every protocol there is, but we still stick to IRC. It's the only protocol that has clients that suit all of us, from hardcore `irssi` to newbie Adium integration. There's also bouncers and solid local histories and it's easy to hop onto tech channels for some help and it's widely supported with chatbots and libraries for building your own chatbot. (eg. Ruby-IRC)
- oskarth 14y agoI agree that IRC is still the chat protocol to use. Though in choosing a chat solutions there are some questions that often arise: 1) persistency (BNCs are still a techie solution, servers) 2) good web interface and 3) file support (other than DCC, unless a bot is present) Here is where for example Campfire managed to take quite a big chunk out of the startup chat market. Are there any clients that integrates well with IRC with those 3 qualities? (file support could be solved by a custom file repo with imgur-like links, or a DCC bot for those on irssi)
- wladimir 14y agoQuassel solves (1) in a user friendly way. It does not address your other points, though (there's a Linux, Windows, Mac desktop version and an Android app, but not a web interface AFAIK).