Jump to content

Open Protocol/API

Featured Replies

Posted

One of the reasons why IRC is so widespread is because the protocol is open - anyone can create a client on any platform.
Right now, most of my members are lamenting that they have to keep a browser open to stay in chat.

Why not have some (basic) features open via an API/protocol, so people can create an external client for IP.Chat?
Most people want to be able to chat on their phones, without a browser (on windows), etc.

Whilst the main problem here is most of our loyal members don't like to chat in a browser, this also creates developer opportunities like bots, etc.

While it's an interesting idea, in all reality I don't see anyone actually writing phone clients for IP.Chat. Just my .02.

  • Author

If you can make this protocol compatible with that of IRC, you'll have clients for virtually every platform.

We weren't exactly shooting for an IRC implementation. If you want to host an IRC server, there are plenty of available scripts out there. :)

If you want IRC-like functionality, just embed something like qwebirc with an iframe.

You'll need a dedicated server (or VPS) to run it on though.

  • Author

I was thinking of a partial implementation just to get IRC clients working, because of the numerous benefits that would bring.
If not, how about a good Windows and iPhone client?

  • 5 weeks later...

I was thinking of a partial implementation just to get IRC clients working, because of the numerous benefits that would bring.


If not, how about a good Windows and iPhone client?




I can use IP.Chat on my iPod touch... I don't see why it should require a dedicated client

Archived

This topic is now archived and is closed to further replies.

Recently Browsing 0

  • No registered users viewing this page.