This is why we have standards for nearly every method of communication on the internet currently – except for IM. Around every system of successful solution is the implementation of a robust standard for communication. The impetus behind Jabber is the need for standardization. (This also eliminates the nickname-selection quandary – no more ChrisWage22423). Rather than having a nickname, you have a exactly like an e-mail address. There would be (ideally) public servers, private servers, corporate servers, etc. Rather, servers are set up on an organizational basis, just as an e-mail server, or a web server is. In the past, all IM clients have been strictly client to server, and so is Jabber, except that there is not just one server. I will not get too deep into the details of how Jabber works, but the biggest difference requires a change of mentality from how most IM clients work. What is it? From ’s FAQ: “Jabber is a set of XML-based protocols for real-time messaging and presence notification.” A simple solution for a simple problem. Rather, I am defending the technology and the protocol – the idea, and the potential. Firstly, let me make it clear that I am not defending the current state of the usability of Jabber’s clients or servers. Trillian is a bandaid at best, and will eventually be rendered useless. The various proprietary IM servers will continue to do everything in their power to prevent third party clients from connecting – and since they own the servers, they will have no trouble doing so effectively. This is why Trillian is ultimately doomed. And I find it hard to believe that others aren’t considering the same course of action.
AOL is in all likelihood developing new additions to their client and service that will prevent Trillian (or any other third party client) from ever hoping to connect. It has calmed down now, but it can only be the eye of the storm.
#TRILLIAN XMPP PATCH#
This went on for almost a week, with a patch every day. Trillian would respond remarkably quickly with a fix, and a patch, and AOL would return in kind, finding a way to block that.
#TRILLIAN XMPP DOWNLOAD#
There was a period of turmoil where AOL continually blocked Trillian clients from connecting to their service, sending down a message advising them to download an authorized client and reconnect. However, as Trillian’s popularity skyrocketed, several of the companies offering IM services took notice – namely, AOL. Trillian is one client that connects to multiple IM services, by implementing all the protocols and consolidating them. I used it too, don’t get me wrong, but it reminded me of a technology already being developed – Jabber – but I will get to that later. To people that found themselves installing 3, 4, and sometimes more IM clients, it was a gift from heaven. Trillian surfaced during the heyday of IM clients. However, development of Jabber is faltering amidst the prolific use of Trillian, which is doomed to eventually fail as a solution, and is only prolonging the inevitable. Something that comes much closer to being exactly that is Jabber. It’s a waste of time and resources that could be invested in something that is a more comprehensive, standardized solution. The problem is that Trillian is only a bandaid. I personally think the UI is written poorly, and it has its bugs, but considering the developers probably spend most of their time hacking around AOL’s blocks, that’s forgivable. It’s a good product written by good people with good intentions. Now that I’ve got your attention, let me say first of all: No, Trillian doesn’t SUCK across the board. They have been reviewing logs for several days.Trillian is a waste of time and resources. I seem to have stumped Cisco TAC as well. I've uploaded his root certs but it still doesn't work.
#TRILLIAN XMPP UPDATE#
His logs are showing 'unknown ca' and suggesting I need to update his root and intermediate certs on my expressway. Trillian support is telling me I need to add new the Root CA to my Expressway which seems silly since it's not necessary for any of the other active domain federations. Also, I have an active outgoing XMPP connection to the Trillian servers IP address. I've checked DNS and nothing has changed in that arena. I'm perplexed by the XMPP logs I'm seeing which are showing DNS_FAIL and 'unable to resolve hostname' messages for the trillian hosted domain. I'll preface by saying it was working but Trillian.im renewed their certificates over the weekend and my users are no longer able to chat with Trillian.im users. However, I am trying to get chat working with a client who is using Trillian.im and I've been unsuccessful. I'm able to federate with Cisco TAC, and other vendors likely all using Cisco Jabber or Spark. Expressway E v8.5.1 CUCM 10.5.2 Not doing anything fancy on my end.