Facebook uses xmpp everywhere, you can connect to their chat directly with an xmpp client. Xmpp is its own standard, and a very low bandwidth, low resource system. I can run server all day and only generate a few mb worth of data where an ajax chat can reach 150mb or more a day with only 20 or so people online, messaging sparratically. And yes, xmpp has extensive privacy systems that can duplicate the one in wedge(with a little scripting), plus handle interactions with other websites and chat servers.
I understand its not your primary concern, but its something I personally like on my forums. I have jappix running on my site as the primary chat and it works very well, far better than any of the many ajax solutions I have tried. So far with smf I have not had any luck trying to make a bridge. Wedge has a lot of improvements over smf, but it isn't a realtime chat, it doesn't have voice or video calling built in, and it has no native client as of yet (that I know of). The forum and blogging systems are beatiful, but it can't fill every role. Not just yet anyway. But if it can send off a realtime notification to a server admin's phone when something goes wrong in the middle of the night, without having to go through an email filter, that is another step that it goes beyond what everyone else can do.
Posted: January 25th, 2014, 07:21 PM
Just as a reference. In march the entire bandwidth of a site I run was just 5gb with the forum + xmpp chat running 24/7. When I switched to ajax chat this doubled or even trippled the bandwidth for that day, then that month. Most recently over 17gb, and it overtaxed our mysql server as well. I have had to tone the chats down to their lowest just to have it stable. And the logs show the increase in the exact day and hour I switched. Bandwidth increased by over 100kbs from the original 20kbs. I haven't run tests on wedge yet, so I can't say what the performance is like. But as you can see in my case ajax based chat systems have been a bane, and the only reason I don't still use Jappix on that specific site is because the sessions would not stay properly linked with the smf logins, so users complained about constant disconnections.
While it may have started as an experiment, xmmp proved to be a very reliable setup, and in this case it only failed because I was personally unable to utilize the API effectively. I know someone here could do better.
This is only a request. Not a demand on anyone. You have no obligation to jump to help me out and I realize that. I just ask that someone consider it.