If you were going to bypass the character limit, I'd go with using URL encode on your message with a special domain. URLs can be substantially longer (2083 char

If you were going to bypass the character limit, I'd go with using URL encode on your message with a special domain. URLs can be substantially longer (2083 characters), and Twitter is happy to only count that as ~10 characters against your message. Then to decode it and bypass the 3rd-party client ban, release a Greasemonkey script that grabs a[title*="http://supertweets.example.com/" http://supertweets.example.com/"] and replaces the 'a' element with the URL decoded 'a.title' instead. Even better, actually register the domain, and have it be a simple script that URL decodes the path and prints it out for you, so that people don't have to install Greasemonkey to see your longer message (but doing so inlines the content.) But ... don't blame me when Twitter bans you for trying this ;)