IFTTT nimmt Twitter größtenteils aus dem Programm

IFTTT nimmt Twitter größtenteils aus dem Programm

Wegen der kürzlich angekündigten Änderungen der Policy hat der beliebte Automatisierungsdienst IFTTT (if this then that) alle Trigger, mit denen Tweets behandelt werden können, deaktiviert. Twitter hatte angekündigt, in Zukunft das Publizieren von Tweets in cloud-basierten Umgebungen zu untersagen. Das bedeutete dann das Aus von Twitter Handle bei IFTTT. Das Posten von Inhalten auf Twitter bleibt von dieser Policy Änderungen unberührt. 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)