bit.ly -> funkatron translation

nk's Avatar

nk

28 Jul, 2011 07:46 PM

When I get tweets that contain a bit.ly shortened URL, for some reason Spaz shows the translated URL, but substitutes the host name to funkatron, so given a bit.ly URL that translates to:

http://host/path

It actually shows up in Spaz as:

http://funkatron/path

Any ideas what I can do to resolve this?

  1. Support Staff 1 Posted by Ed Finkler on 28 Jul, 2011 09:37 PM

    Ed Finkler's Avatar

    Can you give me a repeatable example?

    --
    Ed Finkler
    Sent with Sparrow (http://www.sparrowmailapp.com/?sig)

  2. 2 Posted by Noam Krendel on 29 Jul, 2011 06:14 PM

    Noam Krendel's Avatar

    Well, here is one of the tweets as I see it on twitter.com:

    rp_emd_svn Subversion Commit
    12063 sline trunk (1U, 0A, 0D): STO-17029 removed console.debug() call http://bit.ly/pEYVgd

    This is the same tweet as it shows up in Spaz:

    12063 sline trunk (1U, 0A, 0D): STO-17029 removed console.debug() call funkatron.com/changelog/SEM/?cs=12063

    2 hr ago
    from MyAuthAPIProxy
     
    rp_emd_svn

    The full link shows up when you mosever as:

    http://funkatron.com/changelog/SEM/?cs=12063

    While the original URL that is pointed to by the bit.ly URL is:

    http://source.res.redprairie.com/changelog/SEM/?cs=12063

    This happens all the time so it's repeatable in that sense, although I do occasionally get "good" tweets that show up as expected:

    12061 chad trunk (2U, 0A, 0D): STO-16980 Added report name to the title. bit.ly/qFB5Ci

    1 day ago
    from MyAuthAPIProxy
     
    rp_emd_svn

  3. Support Staff 3 Posted by Ed Finkler on 29 Jul, 2011 06:20 PM

    Ed Finkler's Avatar

    I think the issue may be that the domain is not resolvable, so the server-side script is returning its own domain. It should not do that of course, so it's a bug on our end, in our server-side services.

    --
    Ed Finkler
    http://funkatron.com
    @funkatron
    AIM: funka7ron / ICQ: 3922133 / XMPP:[email blocked]

  4. 4 Posted by Noam Krendel on 29 Jul, 2011 06:33 PM

    Noam Krendel's Avatar

    Ah I see. Yes the domain is only resolved properly when you're on the VPN, but I would imagine that the bit.ly shortened URL would just be passed as is instead of being resolved.

  5. Support Staff 5 Posted by Ed Finkler on 29 Jul, 2011 06:37 PM

    Ed Finkler's Avatar

    If you're curious, this is the method that does the URL resolve:

    https://github.com/funkatron/Spaz-Web-APIs/blob/master/custom/Model...

    The approach we use resolves any URLs, not just certain shorteners, but obviously there's a bug here with handling error responses.

  6. 6 Posted by Noam Krendel on 29 Jul, 2011 08:34 PM

    Noam Krendel's Avatar

    It's interesting that in some cases it handles the error correctly and returns the un-resolved URL, as in the "good" tweet above, (which also resolves to the VPN-only domain) bit.ly/qFB5Ci.

    I guess I'll keep my eyes open for a fix. Thanks for the response!

  7. cringer closed this discussion on 12 Sep, 2011 07:38 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac