Sam Johnston's dashboard

Sam Johnston marked one of Doug Smith's replies in atebits as useful. Doug Smith replied to the idea "Add "rel=shortlink" support for auto-detecting short links".

Sam Johnston replied on August 19, 2009 22:02 to the idea "Add "rel=shortlink" support for auto-detecting short links" in HootSuite:

Good to hear - thanks for the update and prompt response.

Sam Johnston marked one of Moni's replies in HootSuite as useful. Moni replied to the idea "Add "rel=shortlink" support for auto-detecting short links".

Sam Johnston replied on August 19, 2009 20:29 to the idea "Add "rel=shortlink" support for auto-detecting short links" in HootSuite:

While that may be true it's unfortunate as I'm sure many of your users would happily forego stats if they were able to be offered a "native" short URL - I know I would and knowing that this feature won't be supported any time soon may well keep me from signing up.

Sam Johnston replied on August 19, 2009 10:05 to the idea "Add "rel=shortlink" support for auto-detecting short links" in twitterfeed:

So when you pick up a new post you don't want to tweet the canonical URL (often you can't because it exceeds 140 chars) and therefore you need to compress it somehow. Presumably you currently hit up a 3rd party shortener like bit.ly but if you were to use something like the code behind http://rel-shortlink.appspot.com/ (which you are welcome and indeed encouraged to run yourself) then you could auto-detect short links offered by the content creator. Wordpress.com have just announced that rel=shortlink has been added to the HTTP headers and HTML HEAD of over 100 million pages so there is immediate value in implementing this feature. There's even a temporary whitelist at the Google Code project so you can tell in advance whether it's worth checking for shortlink.

Sam Johnston replied on August 19, 2009 09:52 to the idea "Add "rel=shortlink" support for auto-detecting short links" in atebits:

Trey, rev=canonical is a dead duck... good idea, yes (in fact rel=shortlink was based on it) but it doesn't work, is confusing, dangerous, reliant on an attribute obsoleted by HTML 5 and has been widely and comprehensively criticised by the web standards community (e.g. Counting the ways that rev="canonical" hurts the Web).

Sam Johnston shared an idea in Orangatame on August 19, 2009 09:41:

Add "rel=shortlink" support for auto-detecting short links

Please add support for the rel=shortlink standard so that TwitterBerry can detect short links from the site (HTTP headers and/or HTML code) rather than having to manufacture them itself using tinyurl.com, bit.ly, etc. This results in better quality (less opaque), more reliable links in a way that doesn't hurt the Internet.

Sam Johnston shared an idea in 83 Degrees on August 19, 2009 09:31:

Add "rel=shortlink" support for auto-detecting short links

Please add support for the rel=shortlink standard so that PowerTwitter can detect short links from the site (HTTP headers and/or HTML code) rather than having to manufacture them itself using tinyurl.com, bit.ly, etc. This results in better quality (less opaque), more reliable links in a way that doesn't hurt the Internet.

Sam Johnston shared an idea in Ping.fm on August 19, 2009 09:26:

Add "rel=shortlink" support for auto-detecting short links

Please add support for the rel=shortlink standard so that Ping.fm can detect short links from the site (HTTP headers and/or HTML code) rather than having to manufacture them itself using tinyurl.com, bit.ly, etc. This results in better quality (less opaque), more reliable links in a way that doesn't hurt the Internet.

Sam Johnston shared an idea in TwitPic on August 19, 2009 09:16:

Add "rel=shortlink" support for auto-detecting short links

Please add support for the rel=shortlink standard so that TwitPic can detect short links from the site (HTTP headers and/or HTML code) rather than having to manufacture them itself using tinyurl.com, bit.ly, etc. This results in better quality (less opaque), more reliable links in a way that doesn't hurt the Internet.

Sam Johnston shared an idea in twitterfon on August 19, 2009 09:08:

Add "rel=shortlink" support for auto-detecting short links

Please add support for the rel=shortlink standard so that TwitterFon can detect short links from the site (HTTP headers and/or HTML code) rather than having to manufacture them itself using tinyurl.com, bit.ly, etc. This results in better quality (less opaque), more reliable links in a way that doesn't hurt the Internet.

Sam Johnston shared an idea in twitterfeed on August 19, 2009 09:04:

Add "rel=shortlink" support for auto-detecting short links

Please add support for the rel=shortlink standard so that TwitterFeed can detect short links from the site (HTTP headers and/or HTML code) rather than having to manufacture them itself using tinyurl.com, bit.ly, etc. This results in better quality (less opaque), more reliable links in a way that doesn't hurt the Internet.

Sam Johnston shared an idea in HootSuite on August 19, 2009 07:41:

Add "rel=shortlink" support for auto-detecting short links

Please add support for the rel=shortlink standard so that HootSuite can detect short links from the site (HTTP headers and/or HTML code) rather than having to manufacture them itself using tinyurl.com, bit.ly, etc. This results in better quality (less opaque), more reliable links in a way that doesn't hurt the Internet.

Sam Johnston shared an idea in HootSuite on August 19, 2009 07:39:

Add "rel=shortlink" support for auto-detecting short links

Please add support for the rel=shortlink standard so that HootSuite can detect short links from the site (HTTP headers and/or HTML code) rather than having to manufacture them itself using tinyurl.com, bit.ly, etc. This results in better quality (less opaque), more reliable links in a way that doesn't hurt the Internet.

Sam Johnston replied on August 19, 2009 00:57 to the idea "Add "rel=shortlink" support for auto-detecting short links" in Twitter:

There are literally hundreds of URL shorteners like shortlink.in (bit.ly is currently the Twitter default) but this is completely unrelated. In fact the adoption of this standard obviates the need for 3rd-party URL shorteners by allowing webmasters to advertise their own short links for auto-detection by clients.

The idea is that when you create content you pre-allocate a short link and when someone tweets that content using a long URL, Twitter (or their client software) will ask the site for the short link. That way all clients have the same short link and none of them have to generate it (nor rely on 3rd parties).

Sam

Sam Johnston shared an idea in Twitter on August 19, 2009 00:34:

Add "rel=shortlink" support for auto-detecting short links

Please add support for the rel=shortlink standard so that Twtiter can detect short links from the site (HTTP headers and/or HTML code) rather than having to manufacture them itself using tinyurl.com, bit.ly, etc. This results in better quality (less opaque), more reliable links in a way that doesn't hurt the Internet.

Sam Johnston replied on August 19, 2009 00:11 to the idea "Add support for rev=canonical when shortening URLs" in atebits:

rev=canonical support is a notoriously bad idea, having been pretty much universally condemned by the web standards community (myself included): mnot's Web log: Counting the ways that rev="canonical" hurts the Web.

Forutnately a more sensible alternative has already been suggested in the form of the rel=shortlink standard. It's been adopted by a number of high profile sites - most notably WordPress.com with over 100 million pages - so it will deliver immediate value.

Sam Johnston shared an idea in atebits on August 18, 2009 15:44:

Add "rel=shortlink" support for auto-detecting short links

Please add support for the rel=shortlink standard so that Tweetie can detect short links from the site (HTTP headers and/or HTML code) rather than having to manufacture them itself using tinyurl.com, bit.ly, etc. This results in better quality (less opaque), more reliable links in a way that doesn't hurt the Internet.

Sam Johnston replied on August 14, 2009 11:16 to the question "Why is transcription so inaccurate, even if I have the caller spell the word(s)?" in Twilio:

Using mturk for this is a great idea (I know because I had it myself independently following SpinVoxGate). Definitely interested to hear how you go, particularly if you're able to make your code available.

Sam

Sam Johnston replied on August 03, 2009 00:14 to the question "When are you implementing Oauth?" in HootSuite:

Security is not optional - it should be one of your top priorities!

I was excited about trying your product but am definitely not giving you my password with all the security concerns around Twitter these days.

Sam