If you’re brave and on 10.6, you might want to try grabbing the latest Adium nightly and test out some new stuff that’s targeted to Adium 1.5.
Not the smallest of which is a new log indexing implementation that’s faster and actually works1. So, if you want to take the risk, download the nightly and reindex your logs2. That will blow away your old index and generate a new one (yes, it’s faster, but depending on how many logs you have it still may take a while).
Just remember, the Adium team makes no guarantee that nightly releases will be stable or actually released nightly, so backup your Adium folder in ~/Library/Application Support. Download and run at your own risk. You can always revert to a stable version of Adium by downloading the version linked to from the Adium homepage.
Adium 1.3 has finally been released!
In addition to tons of overall improvements, this release includes the new BSD-Licensed AutoHyperlinks Framework, which offers many, many improvements over the old architecture.
So, right now I’m working on AutoHyperlink’s thread safety. Luckily for us, flex – the lexical analyzer AH uses to check a URI’s validity – allows us to create a reentrant lexer.
Combined with some API refactoring I’m doing (AHHyperlinkScanner works much like NSScanner now), it’ll be a nice slick little framework that’s thread safe and nice to work with.
I’m planning on committing the source post Adium 1.3 branch since it plays with API elements and I don’t want any surprise regressions to hold up release, but, if you’re curious, you can get a patch to apply to Adium’s svn trunk here.
[Update:] Just a quick edit to add that this version of the framework, which is included in Adium’s svn tunk and will be released alongside Adium 1.3, will be dubbed AutoHyperlinks.framework 1.0 and added to the maccode repository.