IFTTT v Pinboard

IFTTT v Pinboard

Never mind Batman v Superman. Now it’s IFTTT v Pinboard and I’m caught in the cross-fire.

I use Pinboard daily in some form or another. I also use the great “connector” service, IFTTT, daily to automate a host of little tasks like adding Instapaper highlights to a text file in Dropbox and many more.

In particular, I use a number of IFTTT recipes that include Pinboard in various little workflows that make my life easier and now it seems that is going to come to an end in just a week or two. I received this alarming email from IFTTT:

IFTTT v Pinboard

I rushed over to the Pinboard blog to see what Pinboard’s creator, Maciej Cegłowski, has to say about the matter. It turns out, he has quite a bit to say in his blog post titled “My Heroic and Lazy Stand Against IFTTT”. He cited two reasons for this little impasse:

Because many of you rely on IFTTT, and because this email makes it sound like I’m the asshole, I feel I should explain myself.

In a nutshell:

  1. IFTTT wants me to do their job for them for free
  2. They have really squirrely terms of service

It’s entirely IFTTT’s decision to drop support for Pinboard (along with a bunch of other sites). They are the ones who are going to flip the switch on working code on April 4, and they could just as easily flip the switch back on (or even write an IFTTT recipe that does it for them). Weigh their claims about Pinboard being a beloved service accordingly.

I understand his concerns and I agree with him that he shouldn’t have to reinvent the wheel at his cost to satisfy IFTTT’s requirements to remain connected to the service. Surely IFTTT could have come up with a more developer-friendly way to migrate to their new platform and help developers make the transition at a lower cost?

I would also have reservations about the contract they want developers to agree to as part of their transition to the new platform. Requiring developers to agree to the sorts of terms Cegłowski quote seems pretty unreasonable given what the clauses would seem to be saying.

At the same time, I’m caught between these two providers I rely on for various tasks. I don’t like the approach IFTTT seems to be taking but I love the service they provide. It literally makes my life easier in so many ways. I have also been using Pinboard for a while now as my personal bookmarking service and I even pay for the archival service. It is a simple and effective service.

This IFTTT v Pinboard impasse between the two companies just hurts people like me who either have to switch to some IFTTT competitor to address the soon-to-be introduced gaps in my workflows or just abandon those workflows altogether. The effect of that is to diminish the value of both services for me, just enough to leave me with that sick, disappointed feeling you get in times like these.

I hope this situation is resolved in some form or another but, if it isn’t … well, that just sucks.

Postscript:

IFTTT v Pinboard Redux – Contracts and Condescension

Paul
Enthusiast, writer, strategist and photographer. Inbound Marketing Specialist. Passionate about my wife, Gina and #proudDad. Allergic to stupid

6 Comments

    1. Firstly, I understand that he is doing this solo and don’t expect him to spend what could translate into obscene amounts of money to meet IFTTT’s demands. I’m not suggesting that.

      And, no, Pinboard is not the party caught in the middle of this. I’m a user of both services and rely on both in varying degrees. Like other users, I’m caught in the middle of the impasse.

      Bottom line is that it is just a lousy situation and I hope it’s resolved.

  1. When I wrote about the IFTTT v Pinboard standoff yesterday, I didn’t spend much time on the contract stuff in my article. Here are a few more thoughts about just how objectionable those contract clauses are and why I believe we are the ones caught in the middle of this mess.

What do you think?

%d bloggers like this: