<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Powerpress on The Comfy Seat</title><link>https://beanbag.technicalissues.us/tags/powerpress/</link><description>Recent content in Powerpress on The Comfy Seat</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 12 Jul 2023 21:45:00 -0400</lastBuildDate><atom:link href="https://beanbag.technicalissues.us/tags/powerpress/index.xml" rel="self" type="application/rss+xml"/><item><title>PowerPress Authorization Flow</title><link>https://beanbag.technicalissues.us/powerpress-authorization-flow/</link><pubDate>Wed, 12 Jul 2023 21:45:00 -0400</pubDate><guid>https://beanbag.technicalissues.us/powerpress-authorization-flow/</guid><description>&lt;p&gt;There’s a proposal in the podcast namespace for an authorization tag and I think &lt;a href="https://wordpress.org/plugins/powerpress/"&gt;PowerPress&lt;/a&gt;, an existing &lt;a href="https://wordpress.org/"&gt;WordPress&lt;/a&gt; plugin that facilitates podcast hosting, can implement the same authorization flow as a podcast hosting provider. The proposed authorization flow is described to work something like this when a service wants to confirm a user owns a podcast:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Service reads an authorization url from the podcast’s rss feed&lt;/li&gt;
&lt;li&gt;Service generates a onetime token&lt;/li&gt;
&lt;li&gt;Service calls authorization url with token &amp;amp; rss feed as parameters&lt;/li&gt;
&lt;li&gt;Website hosting authorization url verifies it’s the home / host of the feed&lt;/li&gt;
&lt;li&gt;Website has user log in&lt;/li&gt;
&lt;li&gt;Website presents user a confirmation page&lt;/li&gt;
&lt;li&gt;If user confirms, website inserts the token into the &lt;code&gt;&amp;lt;podcast:txt&amp;gt;&lt;/code&gt; tag&lt;/li&gt;
&lt;li&gt;Website publishes updated rss feed&lt;/li&gt;
&lt;li&gt;If website supports it, it sends a podping to notify watchers of the updated feed&lt;/li&gt;
&lt;li&gt;Website sends a success response if the feed is updated and a failure response otherwise&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;User interaction is done at this point. The service still needs to see the updated feed, but that is beyond the bits I want to talk about here.&lt;/p&gt;</description></item></channel></rss>