Conversation

Notices

1. Embed this notice
   Tim Chambers (tchambers@indieweb.social)'s status on Wednesday, 13-Nov-2024 05:59:05 JST Tim Chambers

   This deserves a lot of attention:
   https://mastodon.social/@subclub/113471254847412752

   • Embed this notice
     Tim Chambers (tchambers@indieweb.social)'s status on Wednesday, 13-Nov-2024 11:47:27 JST Tim Chambers

     in reply to

     • Pelle Wessman

     @voxpelli I dig the idea of premium for pay only RSS…works for podcasts bet it could work for news and other content.

   • Embed this notice
     Pelle Wessman (voxpelli@mastodon.social)'s status on Wednesday, 13-Nov-2024 11:47:28 JST Pelle Wessman

     in reply to

     @tchambers Why? Not sure paywalls solve much? (And that comes from someone who long promoted the rel-payment microformat and built web extensions etc supporting it)

   • Embed this notice
     Tim Chambers (tchambers@indieweb.social)'s status on Wednesday, 13-Nov-2024 21:35:59 JST Tim Chambers

     in reply to

     • Pelle Wessman
     • Bart Decrem
     • sub.club

     @voxpelli ask @bart about their implementation… @subclub

   • Embed this notice
     Pelle Wessman (voxpelli@mastodon.social)'s status on Wednesday, 13-Nov-2024 21:36:00 JST Pelle Wessman

     in reply to

     @tchambers How do they make that work? If I pay and get a unique RSS url, then I can share that RSS url with you?

     There needs to be a way to authenticate oneself from within the podcast client so that one can add it as one of X allowed clients for one’s subscription

     (This is why we never launched paid podcasts when I worked at a newspaper ≈5 years ago)

     What standards are they proposing for all this?

   • Embed this notice
     Pelle Wessman (voxpelli@mastodon.social)'s status on Wednesday, 13-Nov-2024 21:36:00 JST Pelle Wessman

     in reply to

     @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?