Or as I said here: https://twitter.com/davidu/status/313826471019954176
The risk to sharecropping on another platform just seems too great to outweigh the audience / signup / integration / etc. benefits.
11–20 of 62 posts
Or as I said here: https://twitter.com/davidu/status/313826471019954176
The risk to sharecropping on another platform just seems too great to outweigh the audience / signup / integration / etc. benefits.
So how did this happen? Did someone at Ribbon not bother to check the TOS? Did they check and just think they wouldn't get caught? The article says Ribbon is trying to contact Twitter to find out what happened, I'd think it would make sense to have somewhat closer relations with anyone who has that much power over your company, so you could find out before they shut you down.
"We’ve had discussions with Twitter in the past, and are eager to find a way to work together."
Are you surprised? Why don't we all go back to AOL and Geocities. The problem with Twitter is that it is not clear exactly what their approach to their revenue problem might be. I understand they want to monetize their API but does that go hand-in-hand with quashing every potential competitor who happens to use the API with a modicum of success? I'm bearish about any company that builds a data warehouse on the basis…
Further, we haven't heard Twitter's side to this -- was there a violation of the TOS that the Tech bloggers didn't catch (or bother finding the other side of the story?)
Essentially you're jumping the gun in saying that Twitter is two-faced ("They say they're open but they're really not") all based upon no data or concrete evidence.
Are you surprised? Why don't we all go back to AOL and Geocities. The problem with Twitter is that it is not clear exactly what their approach to their revenue problem might be. I understand they want to monetize their API but does that go hand-in-hand with quashing every potential competitor who happens to use the API with a modicum of success? I'm bearish about any company that builds a data warehouse on the basis…
Further, why does twitter make it hard to pay them for API use?
Here's the post about this on Ribbon's blog: http://blog.ribbon.co/an-update-on-in-stream-payments-on-twi...
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?
That's why they shut it down.