Autoexpand tinyurls

[GoogleCodeExporter]

When displaying a tweet, witty should autoexpand tinyurls into the real
urls.  You really don't know what could be behind a tinyurl (granted, you
could argue the same with a standard url too, but still) which can be annoying.

Probably add this as an option as it will slow down displaying tweets (or
do it in a seperate thread).

Original issue reported on code.google.com by bre...@gmail.com on 12 Feb 2008 at 2:21

Attachments:

[GoogleCodeExporter]

Sounds like a great idea.  I took a quick look and this might be do-able with 
the
tinyurl api.

Original comment by alan...@gmail.com on 19 Mar 2008 at 1:06

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I've been working on this.  :-)   I've got the tinyurl URLs expanding to full 
URLs. 
Currently it's just doing it inline.  I agree that it should be in a separate 
thread.
 I also was thinking it might be nice to show the tiny URL and have the full url as a
tooltip.

I've also been seeing lots of other url shortening services being used (like 
is.gd,
shrinkster.com, rurl.com, and a whole bunch of others).  I think I've got it 
designed
so we can plug in new "handlers" without much hassle.

Original comment by jeremy.w...@gmail.com on 29 Apr 2008 at 1:17

[GoogleCodeExporter]

May just handle this on tooltip. It seems like the only way to handle this for 
multiple shortening services is like this:

    private static string GetRedirect(string Uri)
    {
        HttpWebRequest req = (HttpWebRequest)WebRequest.Create(Uri);
        HttpWebResponse myResp = (HttpWebResponse)req.GetResponse();
        return myResp.ResponseUri.AbsoluteUri;
    }

Original comment by jongallo...@gmail.com on 14 Dec 2008 at 6:51

[GoogleCodeExporter]

Links from Ben:
http://userscripts.org/scripts/review/37982
http://www.longurlplease.com/docs

Original comment by jongallo...@gmail.com on 1 Feb 2009 at 6:54

[GoogleCodeExporter]

Added test spike which uses the longurlplease service to expand short uls of all
shapes and sizes. Response is in Json format so we should consider moving Witty 
to
3.5 in order to leverage DataContractJsonSerializer class and other fun stuff.  
See
http://www.longurlplease.com for more.

Original comment by bgrisw...@gmail.com on 1 Feb 2009 at 9:00

• Changed state: Started