My Heroic and Lazy Stand Against IFTTT
blog.pinboard.in
My Heroic and Lazy Stand Against IFTTT
1–10 of 223 posts
Re: My Heroic and Lazy Stand Against IFTTT
#2Something is wrong with your cert
Re: My Heroic and Lazy Stand Against IFTTT
#3Something is wrong with your cert
Looks valid to me.
Re: My Heroic and Lazy Stand Against IFTTT
#4Well, that's stupid of them.
Re: My Heroic and Lazy Stand Against IFTTT
#5Something is wrong with your cert
[deleted]
Re: My Heroic and Lazy Stand Against IFTTT
#6I went through the IFTTT integration process a while back. I created a platform for indexing street art and made a service that can return nearby street art, when given a lat/lon point.
When I first got contacted about the IFTTT channel, I was excited. After realizing how much of my application endpoint I was going to need to rewrite, it became a task I kept putting on the back burner.
In my mind, the process of integration is being done well. It just requires a lot of lift for individuals who are the only developer on a project that already feels like it has a never ending list of tasks.
Re: My Heroic and Lazy Stand Against IFTTT
#7Something is wrong with your cert
[deleted]
Re: My Heroic and Lazy Stand Against IFTTT
#8Something 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.
Re: My Heroic and Lazy Stand Against IFTTT
#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 obligations hereunder.
Any developer signing this agreement is nuts.
Re: My Heroic and Lazy Stand Against IFTTT
#10Something 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.
Incorrect certificate chain. When you moved to SHA2 certs, you failed to change the intermediates to the "Gandi Standard SSL CA 2" ones.