iparamonau

Thanks for the mention (and contributing) Mathias.

A quick clarification: #1: our endpoint is "community" one. It's free and open for dev purposes, but it's not suggested for production use as one can easily self-host it (though we use same server for number of heavy traffic apps like Iframely for Gmail chrome ext).

#2: Iframely now has the oEmbed endpoint too. We trim much richer infos into oembed format for backwards compatibility.

We tried and I think successfully put together the UI that combines two distinct contexts - one with the content and one with the discussions/chats.

Would be great to know if you guys find it usable/elegant

if 42 is the answer, is 'how many URLs have OG tags' the new ultimate question?

It's not about the Protocols over APIs. It's not even about open-web over walled-gardens.

Take a quick look back: Google Wave wasn't a safe bet, even though it was a federated protocol. On the other hand Facebook's Open Graph is a safe bet, even though it is hardly a protocol, but rather FB's API.

If you'd like to be sure something doesn't get deprecated, make sure it is widely adapted before you use it. In this case you would be a part of community, whose opinion has a leverage over technology providers.

But this way you may miss an early opportunity. It's all about choices. Luckily, we have plenty.