Hacker News Reader

Here's the post about this on Ribbon's blog:

http://blog.ribbon.co/an-update-on-in-stream-payments-on-twi...

The preview doesn't look anything like their final implementation. That preview looks like an actual movie player, while the final card screenshots I've seen look like regular content cards with a lot of custom branding.

This looks like a clever hack of the Twitter implementation of the Player card and not the intended use. The stream and content type attributes both are empty, for example. Does anyone know if this sort of implementation is what that card is supposed to allow?

Sadly, I think you might be right - perhaps Ribbon showed one system, and deployed another.

I say "sadly," as if this is the case, Ribbon have just made every other developer's life that bit more difficult.

I really hope they haven't been that underhand, though.

Indeed. If you look at the screenshot, it looks like they showed Twitter that they would embed a video, but if you follow the URL they're embedding, it goes to the now-banned implementation - https://ribbon.co/086f0a?twitter=true

Maybe it's just an old screenshot though. I don't know.

Reply on news.ycombinator.com