This is the email they've been sending out to users:<p>Dear robgough,<p>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.<p>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.<p>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.<p>Linden Tibbets
IFTTT CEO<p>*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).
Sorry Twitter, but Fuck You. You went from being useless to useful then back to useless.<p>I had set up 10 different actions using the Twitter IFTTT interaction. These actions specifically notify me of emergency alerts and breaking news through the Pushover Channel.<p>I have alerts for breaking news from local media, I have emergency alerts from my university campus, and I have emergency weather/safety-related alerts.<p>Without much technical knowledge, I know of no easier way to receive these alerts, since they are being posted specifically to Twitter.<p>I didn't care too much about the restrictions on 3rd party clients. But this is directly influencing how I perceive my personal safety in this tech-filled world. As soon as we convinced people to post important messages to twitter, we remove the ability to notify ourselves of them? That's malicious.
The terms in question:<p>"You may export or extract non-programmatic, GUI-driven Twitter Content as a PDF or spreadsheet by using "save as" or similar functionality. Exporting Twitter Content to a datastore as a service or other cloud based service, however, is not permitted."<p>So do I own my tweets or not? If I own them, can't I decide what to do with them, such as storing them in a cloud service? Twitter can't have it both ways.
This is really annoying. I've been using IFTTT to e-mail all of my tweets and mentions to a dedicated e-mail address for archival purposes. Looks like I need to quit publishing via Twitter if I can't keep backups.
Suggestion for anyone pissed off (at Twitter) by this: Check out <a href="https://rstat.us/" rel="nofollow">https://rstat.us/</a> . It's a completely open microblogging platform, and at least for now, you can log in using your Twitter account (via OAuth) and cross-post all your Rstat.us updates to Twitter.<p>I've been meaning to try it for some time and this news compelled me to do it. Seems to work fine. You can follow me there if you like: <a href="https://rstat.us/users/graue" rel="nofollow">https://rstat.us/users/graue</a> (not really trying to promote myself though, my updates are pretty boring) Also, I have no relationship with the people who made this site, but they seem pretty passionate about open platforms.<p>I don't think IFTTT supports Rstat.us right now, but it would be great to see them add it.
If I'm understanding this straight:<p>google+: a network that restricts that people _write_ via their website/apps.<p>twitter: a network that is now starting to restrict people to _read_ only via their website/apps.<p>technology does evolve and diverge in lots of directions.
Net Neutrality is the reason the Internet has driven online economic innovation. It protects our right to use any equipment, content, application or service without interference from the network provider. With Net Neutrality, the network’s only job is to move data — not choose which data to privilege with higher-quality service and which to demote to a slower lane.<p>This would be the same for APIs, which are too often driven only by business when investors strategies come in the place.
Stay open for an API without discrimination and tiering on data access and re-use is giving trust to all your ecosystem for building future business on it.
Don't respect it is enfrenging the API neutrality concept.<p>More on what would be API neutrality here : <a href="http://api500.com/post/31465739810/what-is-api-neutrality" rel="nofollow">http://api500.com/post/31465739810/what-is-api-neutrality</a>