When I wrote about workplace tools in a previous post, I neglected to mention twitter - probably because its use is just an intrinsic part of how I work. I use twitter to find stuff, to keep in touch with my (various and not necessarily inter-related communities of practice (web science; technology enhanced learning; personal and educational development; workplace and remote friends and colleagues; running and cycling (think serious juggling plus work life balance here). I have Twitter tools on my various devices, and have been using Twitter with IFTTT to help me build up an archive of useful stuff which I have spotted by saving it in Evernote.
Imagine my disappointment therefore to discover that twitter has decided to self harm to a disastrous extent - of which I learnt courtesy of the IFTTT twitter feed, and the ensuing storm of twitter discussion.
We recently sent an email to everyone with a Recipe that uses a Twitter Trigger outlining some upcoming changes to the Twitter Channel. Here’s the full email:
In recent weeks, Twitter has 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 https://dev.twitter.com/terms/api-terms) and include stricter enforcement of the Developer Display Requirements (https://dev.twitter.com/terms/display-requirements)