Where the design community meets.
Saying that IFTTT does nothing for Pinboard is disingenuous. The relationship greatly benefits smaller platforms like Pinboard, because IFTTT has such a large userbase.
I agree with the points me makes about the T&C, they're far-reaching and should be reeled in, but the fact is that IFTTT no longer needs/wants to get data from Pinboard if it requires them committing development time.
In my opinion, Pinboard stands to gain more from being on IFTTT than vise versa, and if IFTTT is requiring platforms to have API's that follow a certain model, that's their decision and it's up to the owner of the service to determine if it's worth their time to build it.
If it isn't, then it isn't and you certainly don't have to, but expecting IFTTT to make decisions against their best interest is unreasonable at best.
It sounds like you may be talking partly about interests of Pinboard users and not the interest of Pinboard, the business. Not that they aren’t closely connected, but if he invests $10,000 (for the sake of argument) of development time and server costs in IFTTT, is he likely to get more than that back in user subscriptions? Maybe – but I doubt it. And what if it's $20,000? He’s serious when he talks about being lazy, but the implication is that writing custom code, even for a really useful feature, costs him significant time and server resources.
Just like IFTTT’s interest is in getting people to make APIs work with them, Pinboard’s interest is in keeping existing customers and getting new subscribers. It is possible that IFTTT support doesn’t really figure into Pinboard’s bottom line at all. He isn’t asking them to do something against their interest – they’re asking him to do something against his interest. In this article, he credited them for doing hard work in the first place in creating a connecting API, but he’s not suggesting that they should keep it going forever. In fact, he is critical of their business model and would likely suggest that they don’t keep it going. Pinboard even offers IFTTT-like Twitter archiving integration that most users probably don’t even know about.
As a long-term Pinboard user and a long-time regular IFTTT user, I can say that I get value out of the Pinboard API every day, but I can take or leave IFTTT support. After all, Pinboard still has an API.
I completely agree, but I believe that Pinboard would have a much better chance of recouping their investment in terms of new users from IFTTT than vise versa.
If IFTTT invested their time to support Pinboard, would they recoup the costs in terms of new users who signed up solely because of the Pinboard integration? Very unlikely.
I don't think they're asking him to do something against his interest as much as they're saying they're not going to do something against theirs, and that hopefully Pinboard believes that it is in their best interest to integrate with them.
Otherwise it's a mutual decision that neither party benefits enough from the integration of one another to dedicate time to it, and we have the situation we're currently in.
I just feel like painting IFTTT as the "bad guy" is inaccurate and reactionary. For the users, it's unfortunate that it won't work anymore. But if neither IFTTT or Pinboard believes that it's worth their time, you cannot fault them for not doing it.
This will of course change if either platform sees a drop in user base as a result of this decision, which in a simplistic view, is how the market is supposed to work.
Very reasonable. I agree that IFTTT is not the bad guy. They will suffer for shutting down channels though – and Pinboard is one of many.
Maciej gets passionate about these matters, and he likes to pick fights with perceived competitors and antagonists, particularly if they are venture capital funded.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.