But, you realized this would be the case when Twitter introduced it's new API restrictions recently, right? I'm not sure why the angst now - the big deal was a month or so ago when Twitter made clear what direction they were taking their API. This is just the implementation of that policy change.
I browsed the restrictions and sort of understood how they changed the game for 3rd party clients, but this is something different, isn't it?
Obviously Twitter is still benefitting from IFTTT publishing to their platform. It would then be a mutually beneficial relationship, then, when IFTTT benefits from Twitter's platform. Twitter is a leech.
Comments
But, you realized this would be the case when Twitter introduced it's new API restrictions recently, right? I'm not sure why the angst now - the big deal was a month or so ago when Twitter made clear what direction they were taking their API. This is just the implementation of that policy change.
I browsed the restrictions and sort of understood how they changed the game for 3rd party clients, but this is something different, isn't it?
Obviously Twitter is still benefitting from IFTTT publishing to their platform. It would then be a mutually beneficial relationship, then, when IFTTT benefits from Twitter's platform. Twitter is a leech.
It's not that IFTTT violates their terms directly, but twitter triggers give IFTTT users the tools to violate the terms.