Comment 2 for bug 380842

This is a really cool idea, but it's not practical to implement in Gwibber right now because of certain architectural limitations in the program. Gwibber currently pulls down the whole stream on every refresh rather than just grabbing the latest items. This means that we would have to expand all of those shortened URLs every single time or maintain an internal cache that matches short/long URLs.

This will be a lot easier to implement after I finish refactoring Gwibber to use an internal cache for all messages. At that point, we will be pulling down only the latest messages during every refresh, so the impact of doing this will be much less noticeable.