TL;DR: Turns out, the way to derive value from web APIs is to let your community run off and do free research and development. Harvest the results, and profit. We were never promised participation, but it felt like it was a 2-way street. Silly us. Where do we go from here?

You know, there wasn’t much to Twitter when I first signed up. Sure, there’s lots now, and tons of work behind it. But, a lot of that was paving the cow paths and ensuring those paths could endure stampedes. Many, many of Twitter’s current features were first brainstormed and pioneered by its users and 3rd-party developers – like the @-reply, the #hashtag, or the retweet. I’m sure I could assemble a list of UI innovations cobbled up by 3rd-party Twitter clients that are now folded back into Twitter itself.

I’m not saying the Twitter crew have nothing to be proud of, but a quite a lot of it started with users and developers outside the company. But now, the company is talking about more thoroughly enforcing certain guidelines for a “consistent Twitter experience”.

To me as a user and sometimes developer, that sounds like: “Thanks, we’ll take it from here. Enjoy the show!” Which, having somehow fooled myself into thinking this was a 2-way street, comes as a bit of cold water to the face. I can’t say I wasn’t warned early and often, though. It’s not like Twitter is suddenly going rogue & evil, or even going away soon. They’re just more firmly grabbing the reins on the product that was never ever really ours to begin with. That’s their prerogative, and they’ll enjoy success.

But, still, it kind of sucks. In the 2000’s, I was gonzo about web services and APIs. One of the things I’d looked most forward to when I joined and Yahoo! back in 2006 was to build up their web APIs. Of course, no one really knew how these things would get monetized – but damn, weren’t mashups cool?

They’ve figured out how to derive value by now, though: Not everything yields a charge-per-request billing concern. It turns out that you can harvest free research and development from your community and fold the good stuff back into the main product. We even did this at – see also, the old for:{username} tag convention and the inbox that followed later. (Do they even have that any more?) But, it seems like Twitter is reaching a point where they’ve harvested enough, and want to polish things up.

What’s left behind are things that aren’t owned by a single entity. RSS, rssCloud, Atom, AtomPub, PubSubHubbub, JSON Activity Streams, Salmon, WebFinger, OStatus, etc and so forth. We could talk to each other with these things, and make beautiful mashups.

But, a lot of us have been distracted by shiny corporate APIs, building value for others and sometimes making a little for ourselves. Why bother writing a web spider chasing microformatted relationships to build a social graph, when we could make a single HTTP GET and have a JSON-formatted friends list tossed back – and thus, get on with the real thing we wanted to do with that list?

And honestly a lot of us fail at things like basic usability and design, making it so much easier for someone to just sign up for a social silo than muck around with trying to get some PHP witchery working on some strange webhost. WordPress may be a relative dream to set up, these days, but not in comparison to a sign-up form.

Sure, back in circa-2000’s era blogosphere, we were figuring out things like feeds and aggregators and autodiscovery and trackbacks and blogrolls and mashups. But, along the way, startups wrapped the best of those things up in packages friendly to broader swaths of humanity. You know, kind of like how Apple is now making glued-together laptops.

That’s where I think the social silos like Twitter and Facebook have won: They’ve made things practical for users that we blogosphereans never did. And on the other end, they gave us nerds free access to APIs that let us build things that were rewarded by real use. Because, for many of us, that’s the real payoff beyond a literal paycheck: seeing our stuff get used and praised as clever.

Now, the social silos don’t need us nerds as much. If they do, they hire us. But, out on the open web, things are a bit stale. The users don’t care to use our complex crap, and don’t even know what it is or why to bother. And we don’t spend much time on it, because how rewarding is it without users?

So now what? Seems like a hard catch-22 to break, and I haven’t had much time lately to do my part in breaking it. Maybe I will soon, so I’m thinking about what to hack on next.