Why IFTTT being forced to remove its Twitter triggers is a red alert for developers | TheNextWeb

See on Scoop.itdigital culture

We just got word this morning that the very cool internet glue service IFTTT was being forced to remove any of its Triggers that have to do with Twitter.Yes, IFTTT is a service beloved by tech nerds, but this change also signals something important about Twitter’s future relationship with developers — something contrary to its previous statements about its recent API changes.

 

IFTTT, if you’re not familiar, is a service that allows you to hook together cool Internet things like Twitter, Facebook, Pusher, SMS, RSS and many more to do interesting stuff. You could, for instance, push a tweet out when an RSS feed is updated, or pull down your tweets to archive them or, and this is a big one, cross-post tweets to other services.

 

Well, earlier today, IFTTT CEO Lane Tibbets said that it would have to stop offering the Triggers related to Twitter. “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.”

 

At this point, any third party developer using Twitter’s platform for their product should probably take a very hard look at the capabilities of their apps. If there’s any chance that they might overlap with Twitter’s desire to be the only way that people read tweets…it might be time to get out.

See on thenextweb.com

Advertisements