The latest victim of the Great Twitter Purge of 2012? IFTTT. We just received an email from CEO Linden Tibbets indicating that “Twitter Triggers” will stop functioning next week. IFTTT (short for “If this, then that”) is a glorious, time-saving little startup that lets users set up recipes to link services and apps. (One of the most popular recipes is getting an SMS message if it rains.)
Animated Twitter avatars are also on the growing no-fly list.
The impending change will not affect posting new tweets via IFTTT, but common uses, like pushing tweets to Evernote, will be disabled. The only upside we can see to this disappointing turn of events is that the one recipe we could never get to work properly (only sending favorited tweets with URLS to our Instapaper) will stop cluttering up the app.
Here’s the email from Mr. Tibbets:
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 email@example.com.
*These Twitter policy changes specifically disallow uploading Twitter Content to a “cloud based service” (Section 4Ahttps://dev.twitter.com/terms/api-terms) and include stricter enforcement of the Developer Display Requirements (https://dev.twitter.com/terms/display-requirements).