Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

My Heroic and Lazy Stand Against IFTTT

blog.pinboard.in

Post reply on HN
Print view View original

51–60 of 223 posts

Re: My Heroic and Lazy Stand Against IFTTT

#51

Post by andrewfong »

msbarnett wrote: post #9

> 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…

Not saying this is good contract writing, but some relevant context would be what the penalty for breaking these clauses are. If the penalty for not maintaining compatability, as stipulated in the contract, is simply "we turn off IFTTT integration with your app", then that seems reasonable. Ditto for the non-assignment clause.

Now if the penalty is three dogs and a pony, then nuts to that.

Re: My Heroic and Lazy Stand Against IFTTT

#52

Post by nickspacek »

I have to admit I use IFTTT to take an RSS feed from our kid's elementary school and post the entries to a Facebook Fan Page. The idea being to avoid having to teach my wife to use an RSS reader, now she (and another hundred or so people) get the school news without leaving Facebook.

I feel conflicted in some ways but pragmatism wins. Anyone know a non-IFTTT way to set this up?

Re: My Heroic and Lazy Stand Against IFTTT

#53

Post by andrewfong »

AnkhMorporkian wrote: post #48
voltagex_ wrote: post #35

I'd spend money on a Yahoo Pipes + IFTTT solution with some kind of guarantee they're not going to vanish overnight. You know, like a Pinboard.in style company. I think we need to clone Maciej.

What we need is a common interchange protocol, not a specific service.

Like RSS, iCal, IMAP, and so forth? Or are you thinking of something else?

Re: My Heroic and Lazy Stand Against IFTTT

#54

Post by 9935c101ab17a66 »

dmerrick wrote: post #25

Depending on when the channel was introduced, the backend implementation of a channel can vary wildly. Some were written in Node, others in Ruby, some where written internally, others were written by the service owners. When IFTTT released the developer platform, they were solving two needs: 1) creating a consistent channel infrastructure, and 2) providing a tool for developers to write channels so they don't have to…

And to also compel them to sign an onerous developer agreement after you tell them they have to do work they previously didn't have to.

Re: My Heroic and Lazy Stand Against IFTTT

#55

Post by voltagex_ »

AnkhMorporkian wrote: post #48
voltagex_ wrote: post #35

I'd spend money on a Yahoo Pipes + IFTTT solution with some kind of guarantee they're not going to vanish overnight. You know, like a Pinboard.in style company. I think we need to clone Maciej.

What we need is a common interchange protocol, not a specific service.

I don't think you're going to get it. It's the same issue with instant messaging now. There's a business incentive not to allow interoperability.

Common interchange of what, though? IFTTT's utility came through connecting disparate services - Reddit to Pinboard, Twitter to Facebook and so on.

Re: My Heroic and Lazy Stand Against IFTTT

#56

Post by toomuchtodo »

voltagex_ wrote: post #55
AnkhMorporkian wrote: post #48

Earlier quoted context omitted.

What we need is a common interchange protocol, not a specific service.

I don't think you're going to get it. It's the same issue with instant messaging now. There's a business incentive not to allow interoperability. Common interchange of what, though? IFTTT's utility came through connecting disparate services - Reddit to Pinboard, Twitter to Facebook and so on.

> Common interchange of what, though?

Common interchange of schemeless data. Take data from here, put there.

Pushing JSON blobs around, essentially.

Re: My Heroic and Lazy Stand Against IFTTT

#57

Post by voltagex_ »

toomuchtodo wrote: post #56
voltagex_ wrote: post #55

Earlier quoted context omitted.

I don't think you're going to get it. It's the same issue with instant messaging now. There's a business incentive not to allow interoperability. Common interchange of what, though? IFTTT's utility came through connecting disparate services - Reddit to Pinboard, Twitter to Facebook and so on.

> Common interchange of what, though? Common interchange of schemeless data. Take data from here, put there. Pushing JSON blobs around, essentially.

Isn't that what HTTP POST/PUT is for? GET for pull?

Re: My Heroic and Lazy Stand Against IFTTT

#58

Post by guelo »

nickspacek wrote: post #52

I have to admit I use IFTTT to take an RSS feed from our kid's elementary school and post the entries to a Facebook Fan Page. The idea being to avoid having to teach my wife to use an RSS reader, now she (and another hundred or so people) get the school news without leaving Facebook. I feel conflicted in some ways but pragmatism wins. Anyone know a non-IFTTT way to set this up?

If you're a self respecting programmer you should write the 10 line script your self.

Re: My Heroic and Lazy Stand Against IFTTT

#59

Post by 8ig8 »

msbarnett wrote: post #9

> 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…

Full TOS here for anyone interested...

http://pastebin.com/UM6pHEVV

Re: My Heroic and Lazy Stand Against IFTTT

#60

Post by thedufer »

idlewords wrote: post #8
williamscales wrote: post #2

Something is wrong with your cert

Some other people are saying they've seen Chrome complain, but I can't reproduce it. Please send email (support@pinboard.in) if you can figure out what's up.

It only happens on Android Chrome. SSLLabs reports a bunch of stuff, but it seems like the issue matches http://stackoverflow.com/questions/27892873/ssl-cert-err-cer.... Hopefully a quick fix.
Post reply on HN