You're misreading the article. The problem has to do with uncoordinated breaking changes to a public API. There were no problems for our apps.

Let me draw an analogy: imagine that one day before release MySQL (or pick your favorite DB) decided to deprecate and ignore the the greater than > operator on queries. No errors - it would just pretend that query clause didn't exist and return all rows for queries that used a >. How would that affect your application?

The point is that when you expose a public API it becomes a contract with your developer community. If you make a breaking change to the API you have a fundamental responsibility to effectively communicate the change and ensure that it doesn't create massive and unpredictable results for clients. In this case Twitter didn't do either.