My hobby: role-playing how I would respond as the CEO if my company was getting skewered on HN. Here is my version! --- I am [not] the CEO over at IFTTT. We m

My hobby: role-playing how I would respond as the CEO if my company was getting skewered on HN. Here is my version! --- I am [not] the CEO over at IFTTT. We messed up. Big time. Pinboard -- and other services developers love -- played an important role in our success thus far and we dropped the ball with the roll-out of our new platform. We have a shared incentive: to make channels work reliably for our end-users. To both stabilize existing channels and to allow new services to connect to IFTTT, we are publishing documention for a standard API that any new channels will need to conform to. Going forward, we will be allowing existing channels to run on the legacy platform. Additionally, we will be reviewing our ToS to clarify out intent. We're not keen on legalese, but it is part of the game when doing integrations between third parties. To maciej, I've reached out personally via email to apologize for the unclear messaging to our users. If you would like to give us a chance to make things right, we would be grateful and happy to help resolve any other outstanding issues.