Our Blog

Twitter just killed IFTTT’s Twitter triggers


Posted by
21 September 2012
9:11
0 comments

Twitter kills IFTTT

We love IFTTT. Its usability is superb, allowing you to harvest almost any aspect of any social network (or anything with an API, for that matter), and push it to anything else with an API. Want to auto-create WordPress posts of your tweets that receive more than 5 retweets? Nothing could be simpler.

Up until now.

Because of the latest Twitter API restrictions, this is the best example so far of how Twitter killed a superb service in their quest to make money. Below is a full copy of IFTTT’s sad but brave message to users:

In recent weeks, Twitter announced policy changes* that will affect how applications and users like yourself can interact with Twitter’s data. As a result of these changes, on September 27th we will be removing all Twitter Triggers, disabling your ability to push tweets to places like email, Evernote and Facebook. All Personal and Shared Recipes using a Twitter Trigger will also be removed. Recipes using Twitter Actions and your ability to post new tweets via IFTTT will continue to work just fine.

At IFTTT, first and foremost, we want to empower anyone to create connections between literally anything. We’ve still got a long way to go, and to get there we need to make sure that the types of connections that IFTTT enables are aligned with how the original creators want their tools and services to be used.

We at IFTTT are big Twitter fans and, like yourself, we’ve gotten a lot of value out of the Recipes that use Twitter Triggers. We’re sad to see them go, but remain excited to build features that work within Twitter’s new policy. Thank you for your support and for understanding these upcoming changes. If you have any questions or concerns, please contact us at support@ifttt.com.

Linden Tibbets
IFTTT CEO

*These Twitter policy changes specifically disallow uploading Twitter Content to a “cloud based service” (Section 4A https://dev.twitter.com/terms/api-terms) and include stricter enforcement of the Developer Display Requirements (https://dev.twitter.com/terms/display-requirements).

Posted by

Leave a Comment

Your email is never shared. Required fields are marked *