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

11–20 of 223 posts

Re: My Heroic and Lazy Stand Against IFTTT

#11

Post by hyperhopper »

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…

I'm surprised that a majority must have signed already, for them to actually make the switch.

Hopefully this costs them a lot of buisiness and they have to revert.

Re: My Heroic and Lazy Stand Against IFTTT

#12

Post by gergles »

Thank you for the recommendations for replacement services. I emailed you about this - and I'm glad you publicly responded, because I smelled something weird in the way the IFTTT email was worded. Very disappointed to hear it was what appears to be pretty shady on their part.

Re: My Heroic and Lazy Stand Against IFTTT

#13

Post by chris_wot »

Isn't this similar to the shit Twitter pulled on developers?

It's funny - nowadays people don't go along with stupidity like this. They just call the bluff of the business doing the strong arming and drop their support for their platform.

Seriously, if IFTTT want to force people do craploads of work for no real payoff, best of luck to them. I do hope most folks won't play along though. And those license terms? Yeah, best of luck with that. I wouldn't use them either!

Re: My Heroic and Lazy Stand Against IFTTT

#14

Post by darkhorn »

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.

https://www.ssllabs.com/ssltest/analyze.html?d=blog.pinboard... Google Chrome on Android ERR_CERT_AUTHORITY_INVALID You are using obsolute chiper.

Re: My Heroic and Lazy Stand Against IFTTT

#17

Post by JoshTriplett »

I hadn't seen Botize before. In structure and capabilities, it looks a lot more promising to me than either IFTTT or Zapier (for instance, it supports maintaining lists and adding/selecting data from them), except that half the site seems to be localized to Spanish and doesn't seem to have an option anywhere to change the site language.

Re: My Heroic and Lazy Stand Against IFTTT

#18

Post by djrogers »

seanalltogether wrote: post #16

Can someone elaborate more on the "Working for Free" section? I'm not well versed in IFTTT, but shouldn't I as the owner of a website that wants to offer a recipe be responsible for the details that recipe? This is all very unclear without specific examples.

This isn't about offering recipes, this is about IFTTT requiring sites to write support for a new API (notice, it's not write to a new API, they have to build this new PI in to their site) so others can write IFTTT recipes.

Re: My Heroic and Lazy Stand Against IFTTT

#19

Post by dljsjr »

seanalltogether wrote: post #16

Can someone elaborate more on the "Working for Free" section? I'm not well versed in IFTTT, but shouldn't I as the owner of a website that wants to offer a recipe be responsible for the details that recipe? This is all very unclear without specific examples.

I believe, and I could be wrong here, that previously IFTTT simply consumed public APIs to cobble things together. They are now asking services that want to be IFTTT-able to expose an API that IFTTT defines. IFTTT will still be hitting endpoints on the developer's product's site, but the endpoints are defined by IFTTT and not public.

Re: My Heroic and Lazy Stand Against IFTTT

#20

Post by idlewords »

JoshTriplett wrote: post #17

I hadn't seen Botize before. In structure and capabilities, it looks a lot more promising to me than either IFTTT or Zapier (for instance, it supports maintaining lists and adding/selecting data from them), except that half the site seems to be localized to Spanish and doesn't seem to have an option anywhere to change the site language.

I think it's just some fellow in Spain who's about to have a really busy week.
Post reply on HN