[bambax]

Being CEO of IFTTT must not be a very demanding job if you offer to come over to every service that connects to your platform, in order to contribute to coding their API.

Joking aside, Maciej isn't asking for "more time", he's asking for:

1. Money, if he has to do your work for you

2. Some kind of guaranty that your undocumented, private API won't change without notice in the future, rendering all this work useless

3. Legal terms that would be acceptable, ie that would not attempt to rob him blind of all intellectual property regarding any work in relation to your service (from which he derives exactly zero money!) and that would not prevent him from competing with you.

Your answer so far does not even attempt to address any of those points.

[idlewords]

Actually, all I want is for existing IFTTT recipes that use Pinboard not to break.

I am fine with IFTTT discontinuing support for my site because of our diverging views on whether a service like IFTTT should be a platform or a roll of duct tape, but the stuff people have duct-taped together should stay duct-taped together.

[SolarNet]

This whole thing is exactly my problem with duct-tape as a service. Stuff a Huginn docker container (FOSS IFTTT) on your own server and bam, personal duct-tape.

[WCityMike]

In case it's not immediately clear, this is Maciej from Pinboard. Note the handle is the same as his blog's name.

[kefka]

I think the other part here, is that IFTTT is making it sound blackmail-y...

IFTTT to users: Weeeeelllll, we had great integration with X service, but they refuse to play ball with us any more. And now, their connector broke, and they refuse to fix it!

It makes you look bad to the users. And if you refuse this faustian 'deal', you're slandered and stuff breaks. And that break isn't because software rot, but because they broke it. And then blame you for it.

Yeah, blackmail is the right word.