Sean Murphy's dashboard

Sean Murphy set one of Sean Murphy's replies as an official response to ""Javascript error: current_domain is invalid"" in Statiksoft, LLC

Sean Murphy replied on October 24, 2009 15:56 to the question ""Javascript error: current_domain is invalid"" in Statiksoft, LLC:

You can install the experimental 2.0.1 extension which fixes this problem: https://addons.mozilla.org/en-US/fire....0.1

A comment on the problem "Version 2.0.0 of the FireFox LongURL Mobile Expander has caused it to quit working in FF3.0.11." in Statiksoft, LLC:

There was a rather long queue of extensions waiting to be reviewed when I uploaded mine. In the mean time, I found out you can install it as experimental here: https://addons.mozilla.org/en-US/fire....0.1 – Sean Murphy, on August 28, 2009 11:15

Sean Murphy replied on August 14, 2009 17:47 to the question "LongURL makes Gmail slow in Firefox 3.5+" in Statiksoft, LLC:

Thanks for reporting this. I'll look into it and see what I can do to improve performance.

Sean Murphy set one of Sean Murphy's replies as an official response to "Version 2.0.0 of the FireFox LongURL Mobile Expander has caused it to quit working in FF3.0.11." in Statiksoft, LLC

Sean Murphy replied on August 14, 2009 17:44 to the problem "Version 2.0.0 of the FireFox LongURL Mobile Expander has caused it to quit working in FF3.0.11." in Statiksoft, LLC:

Hi guys,

So for not getting to this sooner. I've uploaded a new version of the extension which fixes these problems. It has to be reviewed by the Mozilla folks before it's made public, but hopefully that wont take too long.

Sean Murphy set one of Sean Murphy's replies as an official response to "Expanded Tooltip "sticks" on screen" in Statiksoft, LLC

Sean Murphy replied on June 28, 2009 15:10 to the problem "Expanded Tooltip "sticks" on screen" in Statiksoft, LLC:

This problem should be fixed in the new extension which was just approved and made public yesterday: https://addons.mozilla.org/en-US/fire....0.0

Sean Murphy replied on June 13, 2009 19:09 to the question "longurl mobile expander stopped working" in Statiksoft, LLC:

Intermittent problems are the hardest to debug. Is the extension still giving you problems? Have you tried un-installing/re-installing? I'd like to help you fix this, but I don't have any idea what the problem could be at this point.

Sean Murphy replied on June 09, 2009 21:17 to the question "longurl mobile expander stopped working" in Statiksoft, LLC:

Hi Paul,

I'm sorry to hear you're having trouble with the LongURL Mobile Expander extension. Could you give more details about what isn't working? i.e. Do you get an error, do you see a tooltip, do you see nothing at all.

You might try re-installing it and see if that fixes anything.

Also, do you have any other add-ons installed which provide a similar feature, or modify links in some way?

Sean Murphy set one of Sean Murphy's replies as an official response to "Return appropriate titles for links that don't lead to html content" in Statiksoft, LLC

Sean Murphy replied on May 13, 2009 13:16 to the idea "Return appropriate titles for links that don't lead to html content" in Statiksoft, LLC:

With version 2.0 of the API there will be an option to return the content-type along with the response. It should then be easy enough for you to adjust the title as you see fit when none is returned.

A comment on the idea "I'd love to see support for ow.ly." in Statiksoft, LLC:

Sorry, I didn't include enough context in my last comment.

The way web page titles are retrieved is by first performing a HEAD request to ensure the document is in fact a web page. It is important that this first step uses a HEAD request to prevent retrieving large resources like mp3 files, exes, pdfs, etc. Once it is confirmed that the URL points to a web page a GET request is made and the <title></title> is parsed out.

In this case with this particular usnews.com URL, they don't send consistent headers between HEAD and GET requests and therefor LongURL doesn't recognize it as a web page.

I hope it isn't too big of a deal. Are you having problems with other ow.ly URLs? – Sean Murphy, on May 10, 2009 01:30

A comment on the idea "I'd love to see support for ow.ly." in Statiksoft, LLC:

I looked into it and that is an edge case with no easy solution. In this case usnews.com doesn't send the same headers for a HEAD request as it does for a GET request, so the *final* destination isn't returned. (If you visit the URL that API request returns you'll see there is one last redirection that takes place) The URL that is returned from a HEAD request has a content-type of application/octet-stream and therefore no title search is attempted on the document.

I hope that makes sense. – Sean Murphy, on May 09, 2009 01:30

Sean Murphy set one of Sean Murphy's replies as an official response to "I'd love to see support for ow.ly." in Statiksoft, LLC

Sean Murphy replied on May 07, 2009 22:57 to the idea "I'd love to see support for ow.ly." in Statiksoft, LLC:

Ow.ly, adjix.com, and 307.to should now be supported.

Sean Murphy set one of Sean Murphy's replies as an official response to "Problem with short url that leads to feedproxy.google.com" in Statiksoft, LLC

Sean Murphy replied on May 07, 2009 01:34 to the problem "Problem with short url that leads to feedproxy.google.com" in Statiksoft, LLC:

Okay, this change has been pushed live. Enjoy.

Sean Murphy set one of Sean Murphy's replies as an official response to "Don't expand urls that aren't shortened" in Statiksoft, LLC

Sean Murphy replied on May 03, 2009 00:32 to the idea "Don't expand urls that aren't shortened" in Statiksoft, LLC:

Thanks. This will be fixed in the next version of the extension to be released soon.