I got an email from IFTTT last night, simply stating:
As of today, IFTTT has stopped supporting the Posterous Channel. The Channel has been removed, along with any Recipes that made use of Posterous Triggers or Actions.
If you have any questions or concerns, please contact us at firstname.lastname@example.org. Thanks for your continued support.
—The IFTTT Team
This announcement, follows a similar one a couple weeks ago, where IFTT also ceased support for channels that pull your data from Twitter.
Since Posterous is owned by Twitter, it's easy to see the parallels in the decision by IFTTT.
blog comments powered by Disqus
Latest Blog Posts
- Open Data as Defined By the White House
- Lack of Cloud Awareness Impacted Twitters Perspective, Setting Bad Tone for How It Deals With Ecosystem
- The 3 Legs Of An Open API
- The Executives Guide to Power and Retention In An API Driven World
- Three Layers of Open
- API Transparency Report as Essential Building Block
- Government and Vendor Data Access Via My Platform OAuth
- At What Point Should Twitter Be Considered An Essential Service?
- Are We Eliminating The Open From the Internet By Using APIs?
- Making Transparency Reports Standard Operating Procedure