Live data from Hacker News

My Heroic and Lazy Stand Against IFTTT

blog.pinboard.in

41–50 of 223 posts

Re: My Heroic and Lazy Stand Against IFTTT

#41
post #10

Earlier quoted context omitted.

Incorrect certificate chain. When you moved to SHA2 certs, you failed to change the intermediates to the "Gandi Standard SSL CA 2" ones.

1 s:/C=FR/ST=Paris/L=Paris/O=Gandi/CN=Gandi Standard SSL CA 2 i:/C=US/ST=New Jersey/L=Jersey City/O=The USERTRUST Network/CN=USERTrust RSA Certification Authority Nope...?

Yes, this is the correct intermediate.

Re: My Heroic and Lazy Stand Against IFTTT

#42

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.

Cert chain is incorrect basically and the browser is fetching intermediate certs to try to make it work.

Most of the issues Qualys points out on blog.pinboard.in are not present on pinboard.in itself, so I presume there's a difference in config there that would be a good place to start. They're also running on different versions of Debian (squeeze v. wheezy, which ship different OpenSSLs) which accounts for some of the variance.

Also, as Qualys notes, disable RC4 ciphers on pinboard.in and you're in pretty good shape.

Re: My Heroic and Lazy Stand Against IFTTT

#43
post #31

Earlier quoted context omitted.

Wouldn't you be performing this work because you believe it will facilitate the transfer of traffic to your site? Aren't you comitting to make changes as and when ifttt change their API so that you can continue to receive their calls? Sites/services can just walk away if they don't want the traffic. No one's obliged to pay or do anything they don't want to.

I think the subtlety that's not evident from these comments is that Maciej didn't solicit IFTTT integration to begin with. In fact, as I recall it, IFTTT did a hacky integration that misused Pinboard's authentication, and Maciej had to help them correct that. Later, after putting a bizarre legal agreement in front of him to sign, IFTTT announced that Pinboard would stop working on their service in a manner that made…

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 you you're supposed to become their customer now.

Re: My Heroic and Lazy Stand Against IFTTT

#44

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…

Shutting down legacy APIs may be a good idea, however the way they want to make the new API happen is completely bonkers.

Re: My Heroic and Lazy Stand Against IFTTT

#46
post #41

Earlier quoted context omitted.

1 s:/C=FR/ST=Paris/L=Paris/O=Gandi/CN=Gandi Standard SSL CA 2 i:/C=US/ST=New Jersey/L=Jersey City/O=The USERTRUST Network/CN=USERTrust RSA Certification Authority Nope...?

Yes, this is the correct intermediate.

Ah, his blog.pinboard.in and pinboard.in configs are different.

@idlewords: http://charlieharvey.org.uk/page/gandi_sha2_intermediate_cer...

Are you putting the chain certs in the SSLCertificateChainFile file, and not concating them to the SSLCertificateFile?

Re: My Heroic and Lazy Stand Against IFTTT

#47
post #31

Earlier quoted context omitted.

I think the subtlety that's not evident from these comments is that Maciej didn't solicit IFTTT integration to begin with. In fact, as I recall it, IFTTT did a hacky integration that misused Pinboard's authentication, and Maciej had to help them correct that. Later, after putting a bizarre legal agreement in front of him to sign, IFTTT announced that Pinboard would stop working on their service in a manner that made…

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.

Re: My Heroic and Lazy Stand Against IFTTT

#48

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.

Re: My Heroic and Lazy Stand Against IFTTT

#49

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.

Tried migrating my IFTTT recipes to Zapier and hit a roadblock on the very first one -- bookmarking posts I have saved in Reddit. Botize apparently has no Reddit integration. There's a definite opportunity here. I'd even pay more money for Pinboard (on top of the archival fee) for more Pinboard-specific integrations for things like this. It is too convenient.

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

Re: My Heroic and Lazy Stand Against IFTTT

#50
post #49

Earlier quoted context omitted.

Tried migrating my IFTTT recipes to Zapier and hit a roadblock on the very first one -- bookmarking posts I have saved in Reddit. Botize apparently has no Reddit integration. There's a definite opportunity here. I'd even pay more money for Pinboard (on top of the archival fee) for more Pinboard-specific integrations for things like this. It is too convenient.

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.
Post reply on HN