Earlier quoted context omitted.
The author noted in the comments that nobody signs it, it's a passive "By using our developer site you agree.." agreement.
Are those even enforceable?
Generally, yes.
My Heroic and Lazy Stand Against IFTTT
191–200 of 223 posts
Re: My Heroic and Lazy Stand Against IFTTT
#192It seems like more and more companies' business model simply involves setting up a "toll booth" on the internet.
Re: My Heroic and Lazy Stand Against IFTTT
#193HN meta: I'm sort of disappointed that this has been getting downvoted. Obviously, what Linden is saying in this case is probably not helping his business case. It's clear to me that he either does not understand why Maciej doesn't want to implement a private API, or does not wish to understand it. On the other hand, neither of those things are grounds for a downvote, I think. A downvote says "this content shouldn't…
A downvote says "this content shouldn't be on HN" Ehh, I'm not sure that's generally accepted. A few years back pg himself did say downvotes could be used for showing simple disagreement, and many people seem to agree even today.
downvoting just because you disagree is stupid.
Re: My Heroic and Lazy Stand Against IFTTT
#194> 11. Compatibility. Each Licensee Channel must maintain 100% compatibility with the Developer Tool and the Service including changes provided to you by IFTTT, which shall be implemented in each Channel promptly thereafter. > 17.This Agreement is personal to Licensee and may not be assigned or transferred for any reason [...]. IFTTT expressly reserves the right to assign this Agreement and to delegate any of its obli…
> Any developer signing this agreement is nuts. ... or didn't read the TOS more likely.
Which I used to think qualified as nuts.
Re: My Heroic and Lazy Stand Against IFTTT
#195I am the CEO over at IFTTT. I apologize for any misunderstanding our communications today have caused. I built the Pinboard Channel on IFTTT and have maintained it for years. I am also a paying customer of Pinboard! I’ve built for hundreds of platforms and any changes to those platforms by default suck. At IFTTT, we've been on the receiving end of platform changes too many times to count. I want to make sure we do it…
Sorry but you don't get it.
Re: My Heroic and Lazy Stand Against IFTTT
#196Earlier quoted context omitted.
Maciej is a fabulous writer with a deft mix of wry, self-deprecating wit and precise expressions. If you aren't familiar with his writing, you'd likely enjoy "Dabblers and Blowhards" http://www.idlewords.com/2005/04/dabblers_and_blowhards.htm
This one is just gut-wrenching to read: http://idlewords.com/2012/09/no_evidence_of_disease.htm And this, of course, is a modern classic: http://idlewords.com/talks/website_obesity.htm
Thank you for sharing the first one. Gut-wrenching, and yet ... I cannot stop reading (other than to post this).
Re: My Heroic and Lazy Stand Against IFTTT
#197[deleted]
Re: My Heroic and Lazy Stand Against IFTTT
#198> 11. Compatibility. Each Licensee Channel must maintain 100% compatibility with the Developer Tool and the Service including changes provided to you by IFTTT, which shall be implemented in each Channel promptly thereafter. > 17.This Agreement is personal to Licensee and may not be assigned or transferred for any reason [...]. IFTTT expressly reserves the right to assign this Agreement and to delegate any of its obli…
> Any developer signing this agreement is nuts. ... or didn't read the TOS more likely.
If you're running a business and not reading the legal agreements your business is signing up for, you're nuts ;)
Re: My Heroic and Lazy Stand Against IFTTT
#199Earlier 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…
Funny you should say that: if there is a plugin infrastructure, I'd expect it to be running for at least a few versions of Excel with proper deprecation notice.
Re: My Heroic and Lazy Stand Against IFTTT
#200I am the CEO over at IFTTT. I apologize for any misunderstanding our communications today have caused. I built the Pinboard Channel on IFTTT and have maintained it for years. I am also a paying customer of Pinboard! I’ve built for hundreds of platforms and any changes to those platforms by default suck. At IFTTT, we've been on the receiving end of platform changes too many times to count. I want to make sure we do it…
It's awfully early to gamble that integration with IFTTT will pay off for the partners. You'd be better off providing and maintaining the integration code, and even paying the partners, until you've established IFTTT integration as a must-have feature for any new service. When Pinboard's customers demand IFTTT integration, you'll have the leverage to push a proprietary API. An even better approach might be to work with your competitors to create an open standard for integration, one that you all benefit from.