I love Twitter, except when I’m pissed at them.
Today I’m pissed at them.
Twitter, for whatever reason they’re spouting — I can’t really understand what the hell they’re talking about — is no longer going to allow IFTTT.com to use tweets in their recipes.
IFTTT.com is a great site that’s built on the logical construction of If This, Then That. If this condition is met, then that action will take place.
You can use it to create recipes like “email me whenever someone uses ‘No Bullshit Social Media’ in a tweet. (Or to put it in their vernacular, if “No Bullshit Social Media” is used in a tweet, then email me.)
Except now you can’t.
That’s because Twitter continues to drop brick after brick into their garden wall so no one else can use their tweets except them. It’s stupid things like this that make me glad I backed App.net when I did. (I’m user #264 or something.)
Here’s the email IFTTT sent out to all their users, from CEO Linden Tibbetts.
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 email@example.com.
* These Twitter policy changes specifically disallow uploading Twitter Content to a “cloud based service” (Section 4A and include stricter enforcement of the Developer Display Requirements (https://dev.twitter.com/terms/display-requirements).
Sadly, IFTTT’s comments are the same hopefully-optimistic-trying-to-be-calm happy face that every other third-party developer has had to put on after getting royally screwed by the messaging giant. That, “we really think they’re bastards, but we’re too mature to actually say so” tone that people adopt after finding out their spouse tells them they want a divorce and you have to leave the house.
Times like this, I fire up the App.net page and start using it even more. I worry that Twitter is going to turn into another Facebook, where they can’t see beyond their own success, and think they’re immortal.
I really do want Twitter to succeed, but it’s days like this that I wonder if they’re going to be around in a few years. Networks like App.net are constantly baying at their heels, like a pack of hounds trying to bring down the stag. The stag may be a badass, but one day it’s going to trip, and the hounds will overtake it.