Read How to do PESOS from Pocket to Micropub by Jan-Lukas ElseJan-Lukas Else (jlelse.blog)
After thinking about it, I finally figured out how to PESOS from Pocket to my own site using IFTTT. The first step was to retrieve an IndieAuth access token using the tool Gimme a token. Then I created a IFTTT applet with the a new favorite item on Pocket as the trigger and a Webhook to execute. I f...
Following in Charlotte’s footsteps?

Published by

Chris Aldrich

I'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, IndieWeb, theoretical mathematics, and big history. I'm also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.

One thought on “”

  1. After thinking about it, I finally figured out how to PESOS from Pocket to my own site using IFTTT. I tried to do it in a similar way to how Charlotte Allen did this.The first step was to retrieve an IndieAuth access token using the tool Gimme a token. Then I created a IFTTT applet with the a new favorite item on Pocket as the trigger and a Webhook to execute. I filled out the details for the Webhook as follows:URL: The URL of the Micropub endpointMethod: POSTContent-Type: application/x-www-form-urlencodedBody: access_token=INDIEAUTHTOKEN&content=section: links&h=entry&category[]=Pocket&bookmark-of={{Url}}&name={{Title}}The part with “section: links” in the body is my custom way to sort posts into blog sections like posts, thoughts, links etc. Every post created via this hook lands in the links section.It’s a bit sad, that it isn’t possible to create a new “Recommended article” as trigger, because with this feature you can share a custom comment to the link. Favorites don’t have that.Update 1 (reply to Charlotte Allen’s question why the URL is not escaped): I tried escaping the parts as you did, with two or three “<”, but somehow that created a strange result. Then I tried it without and somehow it worked. Seems like when the body is sent as application/x-www-form-urlencoded, it doesn’t matter if it is encoded.Update 2 (reply to Chris Aldrich’s question): It is indeed based on Charlotte’s post.

    Syndicated copies:

Mentions

Leave a Reply

Your email address will not be published. Required fields are marked *

To respond to a post on this site using your own website, create your post making sure to include the (target) URL/permalink for my post in your response. Then enter the URL/permalink of your response in the (source) box and click the 'Ping me' button. Your response will appear (possibly after moderation) on my page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Learn More)