You're on crack. IRC is not the most used groupchat protocol on the Internet. Most Internet users have never heard of IRC, but the overwhelming majority of them have an IM address somewhere that does group chat.
By "in use on millions of websites", I presume you're cheating by saying that any website that mentions IRC is "using" IRC.
Obviously the big ones - ustream, jtv...
Here's a few more.
http://www.quantcast.com/p-1as4Vqt4eFyrI/traffic/syndicators
Re:The 37signals Effect
by whatusername on Monday January 19, 2009 @09:45PM
(#441258)
Compared to MSN / Sametime / Facebook Chat / Yahoo Chat / AOL Chat / etc - I don't think ustream or jtv are very big.
I'm not trying to cast aspersions on your front-end work, but why-oh-why would you use IRC as your backend? Icb is "proven" too.
If you were building a website, would you use HTML, which completely sucks and is an abomination, or would you create a fantastic new system with its own browser?
I would use HTML, but I really don't think HTML is an abomination. Whereas IRC clearly is, and it's not hard to replace, unlike HTML.
You could probably change Mibbit to use the MibbitChat protocol and most of your users would never care.
Why do you assume that's not my longer term plan?
I already layer things ontop of IRC such as typing notify, recent chat on channel join etc...
IRC is a simple, solid chat protocol. It's about as ugly and broken as HTML IMHO.
You don't get users by forcing them to use some swanky new protocol/system off the bat. That's a recipe for quick failure.
I'm doing some IRC stats for langpop.com, and if you want technical help, someplace like Freenode is still the place to be. Where can you get Ruby help on IM?
It's in use on millions of websites. It's the most used groupchat protocol on the internet.
So I'm not quite sure where you get your data from.
Maybe you personally hate IRC for some reason, but to say "I can't imagine why anyone would waste time using it in 2009." Is just idiotic.