<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[For the #ActivityPubAPI, we need a profile of OAuth to use for accessing the actor&#x27;s data.]]></title><description><![CDATA[<p>For the <a href="https://cosocial.ca/tags/ActivityPubAPI" rel="tag">#<span>ActivityPubAPI</span></a>, we need a profile of OAuth to use for accessing the actor's data. There's a suggested flow here: </p><p><a href="https://github.com/swicg/activitypub-api/blob/main/OAuth%202.0%20for%20ActivityPub%20Activity%20Diagram.png" rel="nofollow noopener"><span>https://</span><span>github.com/swicg/activitypub-a</span><span>pi/blob/main/OAuth%202.0%20for%20ActivityPub%20Activity%20Diagram.png</span></a></p><p>There's an example client here:</p><p><a href="https://swicg.github.io/activitypub-api/examples/oauth/index.html" rel="nofollow noopener"><span>https://</span><span>swicg.github.io/activitypub-ap</span><span>i/examples/oauth/index.html</span></a></p><p>It tries discovery via RFC 8414 or getting the endpoints straight from the actor.</p><p>It then provisions a client ID using CIMD, FEP d8c2, or DCR (in that order).</p><p>It then tries to do an authorization code flow.</p><p>I'm interested in seeing it tested with more ActivityPub API servers.</p><p><a href="https://cosocial.ca/tags/ActivityPub" rel="tag">#<span>ActivityPub</span></a></p>]]></description><link>https://bb.devnull.land/topic/0a7b3827-d610-4123-99f1-29a7791b442c/for-the-activitypubapi-we-need-a-profile-of-oauth-to-use-for-accessing-the-actor-s-data.</link><generator>RSS for Node</generator><lastBuildDate>Sun, 17 May 2026 22:29:07 GMT</lastBuildDate><atom:link href="https://bb.devnull.land/topic/0a7b3827-d610-4123-99f1-29a7791b442c.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 17 May 2026 20:01:03 GMT</pubDate><ttl>60</ttl></channel></rss>