Live data from Hacker News

My Heroic and Lazy Stand Against IFTTT

blog.pinboard.in

81–90 of 223 posts

Re: My Heroic and Lazy Stand Against IFTTT

#81
post #49

Earlier quoted context omitted.

The RSS feed for saved posts is https://www.reddit.com/user/{ { username }}/saved/.rss

Thank you! I have RSS feeds set to private by default, so I assumed this wouldn't work. However, I did discover "Private RSS feeds" in the reddit preferences. I can likely feed these into Zapier.

You can also use .json (for almost every Reddit URL, actually!)

Re: My Heroic and Lazy Stand Against IFTTT

#82

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

On one hand, you can justify the work as a part of making a more reliable platform without per-service shims, but presumably you could have asked the services to adopt a better open API rather than IFTTT-specific integration. But why did you ignore all the commentary on your TOS? Are you endorsing those terms as the company you want to be?

Our API is not yet open, but we very much want it to be soon. I stand behind our TOS and I agree that we can make it clearer.

Re: My Heroic and Lazy Stand Against IFTTT

#83
post #58

Earlier quoted context omitted.

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

If you are a self-respecting programmer, you should ask yourself if someone has done a better job writing the same tool than you intend to do.

You have been handed down free libraries for RSS and Facebook containing thousands of lines of high quality code. If you can't put the few lines of glue code together and are willing to sacrifice your privacy and random legal restrictions to yet another service just for this little convenience, then... well if you don't respect yourself I'm not going to respect you either.

Re: My Heroic and Lazy Stand Against IFTTT

#84

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

> 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 better.

I've never used IFTTT, but my understanding is that this is the biggest value IFTTT provides - tying together a set of normally incompatible services. If you're now pushing this work onto the services themselves what is the value add that IFTTT provides? And wouldn't the internet be better off if those same sites adopted a shared, open API that could be used by anyone instead?

Re: My Heroic and Lazy Stand Against IFTTT

#85
post #74

Earlier quoted context omitted.

The things you are saying here sound like your attitude is in the right place, but did you actually read the TOS your legal team sent out?

Yes I did. Agree that we could make some improvements

As the CEO, if you think you could have made some improvements, then I wonder how this contract got sent out to valued partners? Can you share with us your plan for fixing this state of affairs going forward?

Re: My Heroic and Lazy Stand Against IFTTT

#86

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

Nobody is even answering our emails/applications for an IFTTT channel so I'm going to shamelessly hook in here and ask: who do small companies (that's what startups are, right?) have to bribe to get bigger companies to even look down at us and exchange an email or two ?

And PLEASE don't tell me to "just fill out the form at http://ifttt.com/platform", tired of that already. We have hundreds of thousands of active users of an IoT service and you're just ignoring us.

PS: I'm grossed out by the fact that I had to resort to a HN comment to try to get someone's attention. Go ahead and downvote to the abyss.

Re: My Heroic and Lazy Stand Against IFTTT

#87
post #86

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

Nobody is even answering our emails/applications for an IFTTT channel so I'm going to shamelessly hook in here and ask: who do small companies (that's what startups are, right?) have to bribe to get bigger companies to even look down at us and exchange an email or two ? And PLEASE don't tell me to "just fill out the form at http://ifttt.com/platform" , tired of that already. We have hundreds of thousands of active us…

Our apologies! We are smaller than you think :) Send me an email at my first name at ifttt.com

Re: My Heroic and Lazy Stand Against IFTTT

#88
post #47

Earlier quoted context omitted.

If they actually succeed at that, it's gonna be a laughing season. Every time a company does something and becomes widely successful, their methods are then recommended on business trainings, startup conferences, etc. So if IFTTT actually manages to subdue many services this way, you can expect other startups to think they can build business out of a) hooking up to your service without your knowledge, and b) telling…

Isn't that the Yelp business model? They're notorious for calling up businesses (mainly restaurants) and then offering the business a way to pay to remove negative comments on Yelp (there was a case where some were entered by a Yelp employee!) It's essentially the "protection/promotion" model.

No, the Yelp business model is to sell ads.

Re: My Heroic and Lazy Stand Against IFTTT

#89

Earlier quoted context omitted.

Having spent countless hours working with third party apis that are poorly documented and business critical I can understand how unexpected changes can be frustrating. But asking people to do things your way with no incentive is even more frustrating for everyone. It comes off as you not respecting their time or the product and apis they have already built.

We very much respect Pinboard's time and are willing to give them just about as much of it as they need. Am willing to spend our time as well! We are looking to improve all of these integrations over time, beyond what their API can support and the best way for Pinboard to do this is to own that integration completely.

OK, but considering that people don't work for free to help others make money do you think it's reasonable to ask maciej or anyone else to do what you're asking them to? You say "it's the best way if they own the integration" as if owning it and the headaches it entails helps developers at all. Why not go for the suboptimal way and maintain it yourself, like you have been all these years?

I get that your service looks bad when integrations break but you could make a different contract requiring developers to give you a heads up in advance of any API changes and then you do the work of keeping the integrations working.

Re: My Heroic and Lazy Stand Against IFTTT

#90

Earlier quoted context omitted.

On one hand, you can justify the work as a part of making a more reliable platform without per-service shims, but presumably you could have asked the services to adopt a better open API rather than IFTTT-specific integration. But why did you ignore all the commentary on your TOS? Are you endorsing those terms as the company you want to be?

Our API is not yet open, but we very much want it to be soon. I stand behind our TOS and I agree that we can make it clearer.

>I stand behind our TOS and I agree that we can make it clearer.

It's already very clear.

Having read what was posted of the Terms of Service document, the document is saying that IFTTT shall own all rights, title, and interest in my content... You stand behind that?

Post reply on HN