'My Heroic and Lazy Stand Against IFTTT' (pinboard.in)
Like many of you, I use IFTTT. It's one of the handiest tools on the internet to get your work done. Want a text alert for weather? Want a notification on your Android smartphone whenever someone you follow publishes a blog post? IFTTT can do all sorts of such things. It is able to do so because it works with different companies and utilizes APIs of their services. Many of these companies are happy to have IFTTT trying to enhance the experience of their customers. Many don't necessarily want -- or can allow -- IFTTT to do that. Pinboard, a social bookmarking website, falls in the latter category. Maciej Ceglowski, CEO of Pinboard in a blog post explained why that is the case: Imagine if your sewer pipe started demanding that you make major changes in your diet. Now imagine that it got a lawyer and started asking you to sign things. You would feel surprised. This is the position I find myself in today with IFTTT, a form of Internet plumbing that has been connecting peaceably to my backend for the past five years, but which has recently started sending scary emails. [...] Because many of you rely on IFTTT, and because [their request] 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. In the blog post, Ceglowski further explains his concerns with IFTTT. He says IFTTT wants ownership of all right, title, and interest. "Pinboard is in some ways already a direct competitor to IFTTT. The site offers built-in Twitter integration, analogous to IFTTT's twitter-Pinboard recipe. I don't know what rights I would be assigning here, but this is not the way I want to find out." You should read the blog post, it's very insightful and sheds light on things that many of us might not have considered otherwise. Jason Snell has offered his take on this as well, he writes: If IFTTT sticks with this philosophy, it will rapidly become a lot less useful and interesting as a service.
Goodwill can be hard to get back. Tread lightly IFTTT.
This acronym is mentioned no less then 12 times in the summary. And yet I still have no fucking clue what it is or what it does.
Perhaps someone here could enlighten me?
You know, reading that, it's hard not to think IFTTT (which I've never heard of) are being the dicks here ... YOU wrote a tool which scrapes content from other sites, and now YOU want THEM to conform to your API, as well as preventing 3rd parties from using your shit? And possibly give YOU rights to THEIR content and retain the right to change the license? Good luck with that.
This sounds like an illegal squatter suing the property owner to upgrade the plumbing and fix the leaky roof.
What, exactly, is IFTTT offering in return other than to say "in order to allow our users to access your site with our stuff, you have to agree to the following". Why would anybody accept random terms and conditions by a third party who merely redistributes your own stuff is a mystery to me.
Sorry, this sounds like a bit of bullshit shakedown, and expecting someone to take steps to support your stuff ... my answer would be to ignore them as well.
Everything about this sounds like childish, petulant and over-reaching behavior in which the 3rd party service is asserting some form of control over the original service so the 3rd party can retain their users. What makes you think the original service owes you a damned thing?
Two words: Fuck that.
Lost at C:>. Found at C.
Just one question...
What the bloody hell is IFTTT?
Like many of you, I use IFTTT.
I think you've overestimated.
systemd is Roko's Basilisk.