Another reason to push App.net posts to Twitter, rather than vice versa

When I first figured out that IFTTT would enable you to post simultaneously to Twitter and App.net with a single effort, I somehow assumed that Twitter would originate and App.net would echo.

IFTTTtthena

That was silly of me. A prejudice of muscle memory, or emotional co-dependency. (Now, there is actually one practical reason to, if you're planning on parallel posting, post to Twitter first: Twitter has a 140 character limit, whereas App.net permits 256 characters. Go with the lowest common denominator, one might rationally say, so your posts on one medium are not truncated.)

But I soon self corrected and set up an IFTTT recipe where my ADN (App.net) post became the "trigger" to push said content to Twitter.

IFTTTathent

Now there's an official Twitter reason to give app.net primacy.

This explanation from an email I received yesterday from IFTTT:

"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."

In short, Twitter is leaving users with no choice. You may own your tweets, but Twitter seems to own their embodiment in that medium.

Is Twitter trying to give App.net a boost? :)


blog comments powered by Disqus