Earlier quoted context omitted.
> I apologize for any misunderstanding our communications today have caused I'm not so sure there is a misunderstanding. The facts seem relatively clear: - You want services to implement your proprietary API so that IFTTT integration with their service runs more smoothly. - Your business success is predicated on other services providing those APIs, but you want them to do the work for no reward. - You have license te…
On the other side of the spectrum, do you expect Slack to maintain the Slack integration you write for your webapp? Do you expect Microsoft to maintain Excel plugins? Of course they might do so for a couple vital ones to help jumpstart the integration system, but it's not black and white. IFTTT is a bit different because this is their value-add. But is it so different that you can make a claim that in a context-free…
No. Because the situations are different.
Here, Pinboard did essentially nothing to get IFTTT to work the first time. IFTTT wrote the integration code, and has been maintaining it. They're now trying to push that effort onto other people.
i.e. They're trying to make YOU maintain code THEY wrote. Or worse, they're trying to make YOU write code which has no value for you, but value for THEM.
If you refuse to work for free, they will remove you from IFTTT integration... to the detriment of their own users.
> Of course they might do so for a couple vital ones to help jumpstart the integration system, but it's not black and white.
It is. Given their ToS, it's pretty damned black and white. IFTTT is pushing their development costs onto the platforms they pull data from. And then claiming that those platforms have to continue working for free, and that IFTTT owns the results of that work.
If you can't see a problem with that, I'm going to make you work for my company, for free, forever.
What? You don't like that?
Well... the same applies here.