I can't find out whether Twitter had reached out to IFTTT in the past about this, since I cannot get a statement from either company, but let's get one thing straight, this move has nothing to do with Twitter's new APIchanges, which I have felt strongly about, when it comes to constraining its usage.
In this case, it seems like IFTTT didn't want to change its ways to play by the rules, but I'd like to hear it directly from them.
Facts are facts, and these are the facts. While this may be a "new" Twitter when it comes to enforcing rules, this is not a case of a new rule affecting a company. Someone is in the wrong here, and it's not Twitter.
No comments:
Post a Comment