Good questions!

For the IndieAuth token, which is created at /wp-admin/users.php?page=indieauth_user_token one only needs to give it a title and the “create” scope?

I created a single token with every permission, as I am reusing this token across all of my IFTTT services. The way I created it was to use GimmeAToken much in the same way that Jan-Lukas did. Funny how we both went for that. But I believe that creating a token via the link you provided is probably the way to go in the future.

For the “then” portion that uses IFTTT.com’s Webhooks service are the following correct?
The URL is (when used with WordPress) of the form: https://example.com/wp-json/micropub/1.0/endpoint
The Method is: POST
The Content Type I’m guessing based on the Body field you’ve included is: application/x-www-form-urlencoded

Yes, this is all correct.

It looks like part of the trouble of this PESOS set up is that you’re too reliant in the long run of relying on Pocket (or other services) being around in the long term. If Pocket disappears, then really, so does most of your bookmark, which ideally should point to the canonical URL of the content you’re bookmarking. Of course perhaps IFTTT may not give you that URL in many cases. It looks to me like the URL you’re bookmarking would make a more appropriate syndication link URL.

I agree wholeheartedly. I’m going to do a bit more digging to see if I can decouple with pocket a bit more when I have time. I’ll be sure to send you a webmention if I find anything fruitful in that search!