IFTTT to stop supporting Twitter triggers on September 27th
IFTTT, which stands for “if this then that“, is an awesome online service that lets you build little scripts. Say for example you’re using Last.fm and an awesome song comes on. You click the like button and with IFTTT you can program it to automatically tweet out the track you just liked, post that track to Tumblr, share it to Evernote, and so on and so forth. IFTTT calls these little scripts “recipes”, and the community is more than eager to share what they’ve come up with so you can get the most out of the service. If you love Android because it lets you tweak just about everything in the operating system, you’re going to fall head over heels with IFTTT and all the things it can let you do.
Now Twitter, in an effort to make more money, is discouraging people from using their API. They told IFTTT that they can no longer give their customers Twitter “triggers”. What’s a trigger? Say you setup IFTTT to send you an email anytime your favorite band sends out a tweet that has the name of your city in it. That tweet, with that keyboard, “triggered” IFTTT to do something. Starting September 27th, you’ll no longer be able to do things like that.
If you want to tell IFTTT to send out a tweet on your behalf, then that’s cool. Twitter doesn’t have a problem with IFTTT sending tweets. Twitter just doesn’t want IFTTT to be constantly hitting their servers, waiting for specific tweets so they can perform specific actions.
We’re huge fans of IFTTT at Android Authority, so we’re deeply saddened by this, but at the same time we understand why this had to happen. Many, probably all, of the online services we use are free. The people who create and run those services have to figure out how to pay their employees. If it means they have to turn off certain features that are too cost prohibitive, well, that’s life.