Johan Bové

Had a really bad experience trying to get the V-Tech "Download Manager" for their Magic Book 3D to work on Windows 10 - the application window did not resize and I had to put the screen size to a ridiculous 480x640 pixels to be able to get to some point where I could actually use the buttons in the application.

Somehow it detected the 3D Magibook on USB, but then, after waiting for the app to "load", and I was able to see the books to add the media of, the USB connection all of sudden disappeared and I was stuck again. I tried four times to get through the process to no avail.

Luckily I have a Macbook from work. I am not really supposed to use it for private applications, but in this case I was a little desperate. So I installed the "Download Manager" for Mac on it and had to mess a bit with disk access for it work, but was happy to see that all worked well on the Mac version of the application. First of all, a "firmware upgrade" window popped up and I had to go through the whole process.

I am suspecting that this firmware issue is the cause of the Windows problems. After the firmware upgrade, I was able to get the media for the new book we got our son, using the Mac app. But haven't tried with the Windows 10 version of the app.

Disappointing that the experience with the application on Windows 10 is so bad. So I wrote the customer service about it. Let's see what happens next.

Pretty proud that I was able to replace the camera modules in my #FairPhone 3 with the latest camera upgrades.

It is really awesome how Fairphone made a truly up-gradable phone possible and they made it really easy to take apart the phone.

The process does require steady hands and some nerve to execute. Detaching the screen from the frame was exciting. You need to get everything to "click" and not "break".

Everything came apart as planned and taking out the old modules and putting in the new was no issue. I did forget to take away one of the blueish protective covers of the front-facing camera module, after I had put the phone back together. So I had the exercise of taking apart the phone twice.

Followed the instructions from Fairphone themselves

The old modules are on their way to IFixit in Stuttgart Germany for refurbishment or recycling.

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://gimme-a-token.5eb.nl/, and the integration with Pocket, Deezer and others worked, but I revoked all access tokens and today it no longer works to create a new token on my Known instance running version 1.2.2.

This post is about trying to solve this issue.

Got the endpoints of my server using:
https://indieweb-endpoints.cc/search?url=https%3A%2F%2Fsocial.johanbove.info

After entering all the fields in "Gimme A Token" and going through the process to get the access token, I end up on https://social.johanbove.info/indieauth/token with the message "Client mismatch". And I'm not sure where to go next.

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://gist.github.com/jgmac1106/3d4df34f99f9a2bd34d47262f26bf508

Update 2020-06-29 19:00

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.

Update 2020-06-29 23:20

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://monocle.p3k.io site error message and I can log in in one flow without having to retry.

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.

Tested using this URL: https://quickthoughts.jgregorymcverry.com/2019/10/01/girlziplocked-good-values-and-turn-key-service

Requests

Request 1 URL

https://social.johanbove.info/like/callback/?url=https%3A%2F%2Fquickthoughts.jgregorymcverry.com%2F2...

Response 1 payload

{
    "title": "URL to page title callback",
    "value": "",
    "messages": []
}

Request 2 URL

https://social.johanbove.info/service/web/unfurl/?url=https%3A%2F%2Fquickthoughts.jgregorymcverry.co...

Response 2 payload

{
    "exception": {
        "class": "RuntimeException",
        "message": "Url https:\/\/quickthoughts.jgregorymcverry.com\/2019\/10\/01\/girlziplocked-good-values-and-turn-key-service could not be unfurled",
        "file": "\/...\/social\/Idno\/Pages\/Service\/Web\/UrlUnfurl.php",
        "line": 69
    },
    "title": "Exception",
    "messages": []
}

Screenshots

Just yesterday we solved an issue with a #JavaScript library dependency by installing the "next" version of the module.

I didn't know #NPM allows you to install "tagged" versions of modules.

Found all documentation about npm-dist-tag here.

An example:

$ npm install thirdPartyLibrary@next