IFTTT deshabilita las recetas con Twitter

No sé vosotros pero yo utilizo mucho IFTTT (If This Then That: Si Esto, Entonces lo Otro) una herramienta que permite delegarle tareas y que funciona con los principales servicios basado en web :

  • App.net
  • bitly
  • Blogger
  • Box
  • Boxcar
  • Buffer
  • BuzzFeed
  • Craigslist
  • Date & Time
  • Delicious
  • Diigo
  • Dropbox
  • Email
  • Evernote
  • Facebook
  • Facebook Pages
  • Feed
  • ffffound!
  • Flickr
  • foursquare
  • Gmail
  • Google Calendar
  • Google Drive
  • Google Reader
  • Google Talk
  • Instagram
  • Instapaper
  • Last.fm
  • LinkedIn
  • Phone Call
  • Pinboard
  • Pocket
  • Posterous
  • Pushover
  • Readability
  • Salesforce Chatter
  • SMS
  • SoundCloud
  • Stocks
  • Storify
  • Svpply
  • Tumblr
  • Twitter
  • Vimeo
  • Weather
  • WeMo Motion
  • WeMo Switch
  • WordPress
  • Yammer
  • YouTube
  • Zootool

Debido a los recientes cambios introducidos por Twitter en su API (para dificultar el uso del servicio por parte de clientes de terceros) IFTTT acaba de enviar un mail a sus usuarios para informarnos que deshabilitará todas las recetas basadas en Twitter; seguirán trabajando para encontrar fórmulas que cumplan con los “nuevos” requisitos del servicio del pajarito.

Casi todas las recetas que tengo en este momento tienen que ver con Twitter por lo que me quitan un 75% del uso que doy al servicio… una pena…

Aquí mismo la carta que he recibido esta noche:

Dear rodrigompaz, 


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 protected]


Linden Tibbets 




*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).

Add a Comment