You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An idea discussed in IRC was adding links to articles that allow a user to:
Mark post as read
Like post
Bookmark post
This would require a couple of things:
If the user wants to enable Micropub actions, they have to "Set up Micropub via IndieAuth". When configuring the Kindle notification type, there would be a Web Sign In form allowing IndieAuth flow to retrieve a Micropub token.
When a post is being sent to Kindle, it could include hyperlinks back to the microsub notifier to a url like: /actions/{JWT}
The JSON Web Token would be configured on the server so you know someone isn't trying to hijack the url endpoint. The JSON Web Token would contain:
This allows for the server to know that the only way this request came to be is a person received the Kindle article, clicked the link which activated the URL with the JSON Web Token in it's path. This seems like enough obscurity and security to authorize the action included in the JSON Web Token to be sent to the Micropub/sub server on behalf of the account listed in the token.
The text was updated successfully, but these errors were encountered:
An idea discussed in IRC was adding links to articles that allow a user to:
This would require a couple of things:
If the user wants to enable Micropub actions, they have to "Set up Micropub via IndieAuth". When configuring the Kindle notification type, there would be a Web Sign In form allowing IndieAuth flow to retrieve a Micropub token.
When a post is being sent to Kindle, it could include hyperlinks back to the microsub notifier to a url like: /actions/{JWT}
The JSON Web Token would be configured on the server so you know someone isn't trying to hijack the url endpoint. The JSON Web Token would contain:
This allows for the server to know that the only way this request came to be is a person received the Kindle article, clicked the link which activated the URL with the JSON Web Token in it's path. This seems like enough obscurity and security to authorize the action included in the JSON Web Token to be sent to the Micropub/sub server on behalf of the account listed in the token.
The text was updated successfully, but these errors were encountered: