jonmwords

He wouldn't give me any specifics at all, but I can tell you that the challenge was related to the extremely low tolerance for lag on a search result page that's treated as law company-wide. He had to do it without slowing down the search page AT ALL, for anybody. Check it out; it even works on mobile.

Hehehe

Meeeeee, too. Me, too. Believe me, I tried.

Glad you liked it. I'm glad people are finding out about this and think it's as cool as I do.

Here's the interview I published with the creator! http://www.readwriteweb.com/archives/how-a-google-engineer-b...

Thanks for that, Matt! I've replaced the promo video with the actual demo in the post.

The guarantee that App.net won't kneecap its developers is that its developers are paying customers.

I don't know. Twitter said they were going to launch annotations in the API, too, and that never materialized.

It's not for common users. It's for people who want to pay for this service. Developers will build federation out to Twitter to reach those who don't want to participate.

The whole spec is there on GitHub for your perusal and criticism, though. https://github.com/appdotnet/api-spec

That doesn't have to happen. Even though the conversation has barely begun, most of the people who are behind this are already concentrating on federation with Twitter. That's how the reach problem will be solved.