@tchambers RSS readers, podcast players, read it later services etc all need some kind of standardized OpenID Connect based flow to authorize access to content and/or some DRM style encryption to ensure the content can only be consumed by authorized clients
For ActivityPub I guess they make use of the follow request feature for access control? But for good UX they would probably want clients to be able to show that it’s paid for content in some way?