Web developer and Studio Lead at Deloitte Digital in Düsseldorf, Germany.
In a further move to simplify my digital life I cancelled my IFTTT account. Wasn't really using it for anything really useful. It was fun for a while. But today I no longer need it.
One of those nuisances with IFTTT is that even-though they obviously are for a more tech-savvy audience, their error handling and messages are frustratingly "sparse" and generic. You actually have to dig into the network tab and check XHR requests to figure out what exactly is failing. This should not be necessary.
Not sure what happened but IFTTT just triggered most of my Deezer likes again... Yay, IOT.
Now that I actually started to pay for IFTTT Pro, it is time for making better use of it. So let's get it on with the applets and services!
2 min read
Trying to obtain an Access Token for IndiePub with IndieAuth to be used in IFTTT requests so I can link other Web Services with my site.
I was able before to get a token using https://
This post is about trying to solve this issue.
Got the endpoints of my server using:
https://
After entering all the fields in "Gimme A Token" and going through the process to get the access token, I end up on https://
What is causing this "client mismatch"? Did Known get safer or is "gimme-a-token" broken?
Going to reach out to Seb and Marcus in the next days.
Found that Greg had a similar issue with Monocle some months ago: https://
So I can rule out that "Gimme-A-Token" is broken.
Thanks to the greate people on the #knownchat IRC channel (thanks Aaron, Greg and sknebel) I have a pointer towards htaccess and http/https redirecting. Looking into that now.
It seems that for a correct IndieAuth authentication, I had to add a hard-coded "me" url in the head of the Known head.tpl.php file so the Known homepage would always have this link:
<!-- Hardcoded me url --> <link href="https://social.johanbove.info" rel="me" class="u-url">
This resolved the https://
But unfortunately I'm still getting "Client mismatch" errors with "Gimme a token" most of the time. I did manage to get once an actual token which I can now use again for IFTTT PESOS syndication.
Thanks for the super clear guidelines - as always very well explained. I was able to get PESOS from Pocket and Feedly working through IFTTT as well on my Known CMS site. IFTTT is sending POST requests to my micropub endpoint and Known is happily accepting the accesstoken, yet when I see the response of the action in IFTTT it always says "Failed". I've checked the response with POSTMAN and Known is responding with a status code 200 - as it should? - so it's okay for now, as it works; but was wondering why IFTTT is flagging the actions as failed?
Adding another PESOS IFTTT Webhook to my site. Saving Articles to Read Later on Feedly will now show up here too.