Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Throwing in my 2 cents:

It looks like what Ribbon submitted to the Twitter validator was a video using the "player" card: http://cl.ly/image/2R2i1J302Z2g

The player card is designed to handle embedding videos, which is what Ribbon initially showed, however when they launched their new feature they morphed the embedding options to display a custom in-stream purchase button / unit.

In reality, they should have just used a 'product' card (granted, they would not have the added ability to purchase in stream - it would need to link back to their website).

Using the player card was a pretty clever way to get the payments to happen directly on twitter, but it seems that it bent too many of their rules. They'll probably just have to use the product card like everyone else.



Spot on. It was a bait and switch and violation of TOS.

Chirpify has been enabling in-stream commerce and payments on Twitter for over a year now. Also in-stream on Instagram and Facebook. No TOS violations http://chirpify.com


Completely agree. It's clear that they found a loophole in order to do something that twitter had no intentions of permitting.

It is very likely that a user would find these cards and inadvertently start a purchase without realizing that this actually not supported by twitter.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: