[twitter-dev] Re: Get resolved URLs?
Gnip's beta testing URL unwinding in all of its streams. All short URLs that move through Gnip get unwound (one level), in real-time, when we transform to Activity Streams. We're representing the unwinding as follows (as an example). If you're interested in trying this out, you can sign up for a trial at http://try.gnip.com . We have to manually toggle the feature on for you (as it's in beta), so be sure to email us (i...@gnip.com) w/ said request after signing up for the trial. gnip:urls gnip:url gnip:short_urlhttp://bit.ly/aC7YVr/gnip:short_url gnip:long_urlhttp://www.twitlonger.com/show/ 1e65c74b49302a0afd8580561e63456a/gnip:long_url /gnip:url /gnip:urls On Aug 6, 10:35 am, Brian Medendorp brian.medend...@gmail.com wrote: I can see that twitter itself must be resolving any shortenedURLs somewhere, because if you search for a domain name (such as amazon.com), you get a bunch of results that don't seem to match until you resolve the shortened URL in the tweet and see that it points to the domain you searched for, which is fantastic! However, I am wondering if there is any way to get thoseresolvedURLs from the API, or (better yet) if there is anyway that thoseURLscould be exposed in the search results themselves. Currently, I am resolving theURLsmyself by requesting the URL and saving the resulting location, but that starts to take a while when there are a lot of results returned.
[twitter-dev] Re: Get resolved URLs?
Agreed, this would make a lot of sense for Twitter to return, especially as the t.co link wrapping gets rolled out. On Aug 6, 3:17 pm, Tom allerleiga...@gmail.com wrote: I agree - it would be nice to have this. Possibly as an entity? http://dev.twitter.com/pages/tweet_entities Tom On Aug 6, 6:35 pm, Brian Medendorp brian.medend...@gmail.com wrote: I can see that twitter itself must be resolving any shortened URLs somewhere, because if you search for a domain name (such as amazon.com), you get a bunch of results that don't seem to match until you resolve the shortened URL in the tweet and see that it points to the domain you searched for, which is fantastic! However, I am wondering if there is any way to get those resolved URLs from the API, or (better yet) if there is anyway that those URLs could be exposed in the search results themselves. Currently, I am resolving the URLs myself by requesting the URL and saving the resulting location, but that starts to take a while when there are a lot of results returned.
[twitter-dev] Re: Get resolved URLs?
I agree - it would be nice to have this. Possibly as an entity? http://dev.twitter.com/pages/tweet_entities Tom On Aug 6, 6:35 pm, Brian Medendorp brian.medend...@gmail.com wrote: I can see that twitter itself must be resolving any shortened URLs somewhere, because if you search for a domain name (such as amazon.com), you get a bunch of results that don't seem to match until you resolve the shortened URL in the tweet and see that it points to the domain you searched for, which is fantastic! However, I am wondering if there is any way to get those resolved URLs from the API, or (better yet) if there is anyway that those URLs could be exposed in the search results themselves. Currently, I am resolving the URLs myself by requesting the URL and saving the resulting location, but that starts to take a while when there are a lot of results returned.