Twitter @Anywhere

» see dev.twitter.com/anywhere as it lived, on the wayback machine

~ the eulogy ~

Evan Williams took the SXSW stage on 15 March 2010 and announced a platform called @Anywhere. The pitch was that any website could add two lines of JavaScript and get Twitter inside its own pages: usernames in the article body turning into links, a box to post from, a follow button that handled the login for you. Facebook had shipped Connect eighteen months earlier and was collecting the whole web into itself. This was the answer.

It went live with the kind of launch list that makes a platform look inevitable, publishers and portals running from the New York Times through to eBay. Developers had working builds to poke at by the start of April, and the formal release came at Chirp, Twitter's first developer conference, on 14 April 2010. For roughly two years this was the supported way to put Twitter on a page you owned.

On Thursday 6 September 2012 Twitter posted a note titled "Sunsetting @Anywhere." The reasoning was that a newer bundle called Twitter for Websites had already rebuilt the pieces people actually used, so there was no reason to carry two. The post set a date: 6 December 2012. That date did not survive, and neither did the one after it.

~ the dossier ~

~ the hovercard ~

One feature had no replacement and Twitter said so in writing. The hovercard was the small panel that appeared when your mouse rested on a username, showing the account's bio and most recent post without taking you off the page. It was the demo everyone remembered from the keynote and the single most @Anywhere-looking thing @Anywhere did.

The sunset post handled it in one sentence: this was the one piece of functionality they would not provide an alternative for, "as we haven't seen it deliver the value to users we hoped for." The closest surviving thing required a click and a popup. Three years after selling the hover as the future of reading, Twitter had measured it and found nobody cared.

~ who was supposed to notice ~

I cannot tell you whether I ever used this, and that is the product working as designed. @Anywhere was built to be invisible: you were meant to experience it as a feature of whichever news site you happened to be reading, not as a Twitter thing with a name. I was an engineering student turning into an engineer across its whole lifespan, reading plenty of English-language tech press on a TTNet connection in Ankara, so the odds are good that some page I loaded between 2010 and 2012 had the library in it. Nothing in the experience told you either way. Developer platforms die without anyone noticing precisely because they were designed so that nobody would.

~ the date that moved twice ~

December 2012 came and went with @Anywhere still working. An update was appended to the bottom of the original announcement rather than published anywhere new: the retirement had been extended to March 2013, and @Anywhere would now be switched off alongside API v1.

The file itself records what happened next better than the blog did. The library at platform.twitter.com/anywhere.js is archived at around 3.4 kilobytes through 26 January 2013. The next capture, on 15 March, is 613 bytes. Somewhere in that seven-week gap the real thing was swapped for a stub, and the date the trade press carried was 5 March, the day Twitter ran its first API v1 blackout test. API v1 itself then slipped again and did not finally retire until 11 June 2013, which left @Anywhere dead three months ahead of the thing it was supposed to die with.

~ what still answers ~

The stub is still being served. Request platform.twitter.com/anywhere.js in October 2026 and you get 531 bytes of JavaScript that defines window.twttr.anywhere as a function taking no arguments and doing nothing, except loop over three strings and write each one to the console as a warning. The first says @Anywhere has been retired and support discontinued. The other two send you to dev.twitter.com for the announcement and for the replacement documentation, and dev.twitter.com has been a redirect to somewhere else for years.

Thirteen years of uptime for a function whose only job is to not throw an error, so that pages nobody has edited since 2012 keep loading. Somewhere out there a site is still calling it, and the browser console on that page is still printing a shutdown notice to an audience of nobody.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »