September 24th, 2013
Trillian for Windows: A focus on performance and stability (5.4 Beta Build 9)
Today’s release of a new beta, Trillian 5.4 for Windows, is primarily focused on improving existing functionality and fixing bugs. We thought the time was right to take a break from building new features to step back and address some common bugs and complaints. Some of the important bits in 5.4:
A change on the Facebook side meant that international users suddenly started seeing junk characters in their chat messages instead of properly encoded characters. This has been fixed in 5.4!
With Outlook.com now supporting the popular IMAP protocol, Trillian’s ability to monitor these email accounts has improved leaps and bounds. See your full mail preview, mark messages as spam, delete messages, etc. In addition, we’ve fixed bugs specific to Yahoo mail, improved our bandwidth consumption when dealing with large messages, and tweaked a few other mail-specific bugs as well.
As more and more of our customers adopt our Trillian Server in-house business solution, we’re also making sure all of our client software can properly connect to an in-house server. Trillian 5.4 accomplishes this for the Windows side, making it possible to connect to servers with self-signed TLS certificates and more.
A few long-standing bugs have been addressed in 5.4, including a few very rare corner cases with message window flashing, improvements to group chat windows, fixes to spellcheck, and a few other great tweaks that long-time users will appreciate.
Last but not least, our Twitter engine gets a few nice enhancements in 5.4: see user displaynames and usernames in your stream, fixes for direct messaging, fixes for RTs being cut off, and more.
We hope you enjoy all the fixes – let us know how the beta runs for you and if you have any bug reports you think we should tackle before the final release! We also have an early alpha of Trillian 2.0 for Mac that we’re testing, available here – more info to come soon.
UPDATE: Build 10 has been released with additional bugfixes.
UPDATE: Build 11 has been released with additional bugfixes.
Posted in Trillian for Windows | Changelog |
September 16th, 2013
Trillian 2.0 for Android
We are pleased to introduce Trillian 2.0 for Android, featuring a more modern user interface that should blend beautifully with your ICS+ devices and a bunch of great new features and enhancements.
Trillian’s new launchpad UI lets you keep up with the people most important to you at a single glance. Paired with optional address book integration, Trillian can now automatically import names and photos for your contacts to make you feel right at home.
Trillian group chats.
You can now easily start group chats with your friends who also use Trillian, with server-backed chat history!
Although we’ve always transmitted passwords using TLS, Trillian 2.0 now uses TLS everywhere, meaning all of your chats are now encrypted over the wire and better protected from third-party eavesdropping.
In-house server compatibility.
If your company runs a Trillian Server you can now connect to it using this version of Trillian for Android!
History has been cleanly integrated into message windows, sending photos has been refreshed, taking photos can now load the camera more easily, emoticons have been overhauled, and a bunch of bugs have been fixed! If you’ve had trouble connecting to MSN or Yahoo! in the past, see if 2.0 helps!
We’re excited to be working with a clean slate for our Android app – let us know what features you’d like to see come to Trillian for Android next!
Posted in Trillian for Android |
June 25th, 2013
Trillian 2.1 for iOS: Trillian group chats, tweaks and fixes!
Trillian group chats.
To start our group chat support, we’re adding support for Trillian to Trillian group chats. If you have any other friends on Trillian you can now easily add them to a group conversation! Now that we’ve tackled the basics of group chat and the underlying UI changes, our next milestone will be to add XMPP conferencing to our iOS version for those of you that rely on these for work.
You can now see the devices you’re connected to directly from the iOS interface in a manner similar to Trillian for Windows.
In-house server support.
Previous versions of Trillian for iOS were incompatible with in-house Trillian Server deployments. If your company runs a Trillian Server you can now connect to it using this version of Trillian for iOS.
We’ve fixed the bug where images would sometimes fail to download or end up in a corrupted, half-downloaded state. We also remember the state of your camera’s flash so you don’t accidentally flash a restaurant while taking a picture of your food. Those of you beta testing iOS 7 will also note we’ve slightly tweaked our icon to make it blend nicer within the flatter world of iOS 7. We plan on making additional changes as well moving forward.
Android users, we haven’t forgotten about you: we’ve been working on Trillian for Android to make sure it was on par, feature-wise, with Trillian for iOS 2.1. Sorry for the delay, but we are now just a few weeks away from a public beta of Trillian 2.0 for Android in full holo-themed glory!
Posted in Trillian for iPhone | Changelog |
June 12th, 2013
Right now, you can pick up the phone and call anyone in the world regardless of the telephone company they use. Email works this way, too: Gmail users can easily send emails to Yahoo! users and so on. Instant messaging has always lacked this back end glue – what we call “interoperability” – and so we’re left signing up with multiple service providers just to ensure coverage across our social network. The result is a mess: Mom is on Facebook, Dad is on Yahoo!, and our co-workers are on Skype. We think this should change, so today we’re making our own small contribution to interoperability by publishing the technical specifications that will allow the outside world to send messages to Trillian users. 1
Why are we doing this? As much as we’re happy to continue reverse engineering IM protocols, Cerulean Studios should also be doing its part to promote open and federated communication. We just so happen to have a great IM protocol we’ve been building and operating for the better part of the past decade – Trillian users will recognize it as the protocol that powers the Trillian IM network – and think the time is right to open it. We’re also laying the foundation to open our network to federation (which means our servers will talk to other servers in the same way an AT&T customer can call a Verizon customer) and continuing our commitment to run a business whose primary focus is its communication products, not advertising. This last point is important – it means we make money when we improve instant messaging, not when we gather enough eyeballs to show them ads.
Some technical bits: while our IM protocol is in production today, it should be considered under active development and therefore subject to (sometimes sweeping!) change. The documentation is also in an early state and should be considered “informational” only. If there’s enough interest in us continuing our documentation efforts we will do so; if not, we still believe publishing our protocol and opening Trillian to future federation is the right thing to do. Feel free to get in touch if you have comments or questions or want to help out in some way, and thanks for your support!
1. Relying on monolithic service providers has other disadvantages as well.
Posted in Cerulean News |
January 29th, 2013
Trillian for Windows (5.3 Build 13)
A new build is heading out today. We’ve been paying attention to the bug reports received after the launch of 5.3 to a larger audience and have fixed most of the major issues reported so far. Fixes include an XMPP crash, an IRC crash, connectivity issues with certain firewall setups, and a few enhancements to some commonly-requested features like the send button and service icons. Check out the full changelog here and thanks for your feedback! We’ll continue hunting down and fixing bugs!
UPDATE: Build 14 has been released to fix a bug with history not appearing for non-Pro users.
UPDATE: Build 16 has been released to fix Twitter connectivity.