This time of year our nio team (should be) in the final stages of a frantic push to deliver what would have been our 4th Annual nio Super Bowl Streaming Experience. Last year thousands of friends, family, and fans from all over the world experienced a niofied Super Bowl 49 via our nowtbg.com streaming experience.
But sadly, with an apology to our community, we will not continue the tradition this year.
Because of Twitter’s continual deceptive practices relating to its API usage terms, we have made the decision not to design another Super Bowl experience. Over each of the last three years, the team has worked tirelessly through rapid iteration sessions, custom development sprints, and design of dynamic visuals to show the context of the Super Bowl in a unique way; the nio way.
There were a lot of motivating reasons for this effort and investment of time. We love sports. We love football; we love the Super Bowl advertisements and all that the Super Bowl implies – all of it! Plus, streaming and processing millions of messages (asynchronously) from over 40 publishers including Twitter is the ultimate wildcard testing situation for an early stage software company – nio innovation. And lastly, we believe that no other company or software can handle the content from an event like the Super Bowl better than nio – nobody!
So this year we’ve decided to call-out Twitter (yeah you @jack). @Twitter, a company that ironically is built by developers, lives off the backs of many developers outside of Twitter and now is struggling to find its way in the public markets. Karma?
Twitter and Comcast, volume throttling soul mates?
As every Netflix user with Comcast cable will angrily agree with, buffering is beyond frustrating. Just like Comcast, Twitter restricts access to content more than ever by capping the amount of data they permit via the “Open” Twitter Streaming API. The continued lack of transparency from Twitter is disappointing, but unfortunately not surprising. Facebook, LinkedIn, Pinterest and others have similarly screwed loyal developers with their API offerings and policy bait and switch tactics. Twitter shamelessly yanks access from the developer community without notice, selectively denies access to the firehose (ask Datasift), and is vague at best when disclosing its policies about streaming volume caps.
Capping content without disclosing is within legal boundaries, but we find it disingenuous.
Makes your blood boil right? Us too! Make sure to check our Twitter API Antics page for a demonstration of the Twitter cap in real-time and tweet it to @jack to let him know that restricting the developer community is not cool.