First of all, thanks so much for the work on the Twitter API. It's a great tool.
I was wondering what the timetable was for supporting include_entities in search API. Right now, when I search for, e.g. news.com.au, I'd be getting a hit on a tweet with "http://bit.ly/aLoB4i";, which in turn resolves to news.com.au. That's perfect, but if include_entities was supported, I'd be able to get the resolved url without having to make an extra HEAD request myself. After all, it clearly is in the Twitter DB. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
