Another BIG difference is that trilliant doesn't have a lot of bugs. MSN client has buffer overflows everywhere and even crashes randomly.
On the other hand, the free trillian version doesn't allow you to maintain several accounts as separate lists as I'd like to do with my aim and msn ones...
I've also had Trillian crash occasionally (I'm using no addons other than any that are preinstalled with it), but unlike the MSN client, I don't lose my current chat, so it doesn't matter as much when it does happen. A limitation of Trillian, at the moment, is that it doesn't use any up-to-date protocols on anything, so each client plugin has at least something that it doesn't support. The MSN and AIM plugins don't support offline messages, the Yahoo plugin doesn't work with chat rooms or file transfers anymore (as far as I can tell) and doesn't support communication with MSN users unlike the official client (and in turn, the MSN plugin doesn't support communication with Yahoo users), and the ICQ plugin can no longer update your profile info for your account (it has a save option you can see, but it doesn't really work). Also various other features with video and audio may not work at all anymore, as well as various other features for each of the protocols not ever having been implemented.
Haha, the current version of Trillian is fairly easy to crack for someone who has the right disassembler and at least some experience with reading assembler (no I'm not giving out my copy, ever). I'm hoping it is still just as easy when they release the newer version, called something like Trillian Astras.
That won't work. What shadowflare meant is that if msn crashes before you close a conversation window, you lose it's contents, since it only archieves the conversation at the moment you click the 'X'.
Yeah, that's exactly what I meant. I do have the automatic logging enabled already. If Microsoft wanted to fix that, it would be extremely easy to fix, and they could have it optional for those cases where you wouldn't want to use it. (not exactly a good idea to write the logs so often if they would be stored on a flash drive, for example)
To do so, they could just increment LastSessionID in the file when the first new message in the new window is written to the file (LastSessionID is normally incremented each time you close a window that has new messages, basically each new session). Then for each message, strip </Log> from the end of the file, append the message, and add the </Log> back to the end. This probably wouldn't really even require much work to implement.
None.