The bmannconsulting.com website
bmann.ca
1---
2tags:
3 - ATProtocol
4 - premiumcontent
5---
6[[Bluesky]] already has built in support for [[Bluesky#Custom Feeds|custom feeds]]. Could this be used to create premium content feeds?
7
8This could look like subscribers-only content, but available and readable directly within Bluesky or any [[ATProtocol]] that supports custom feeds.
9
10This is most relevant for a kind of ATProtocol-based "subscribe to my blog or newsletter" integration -- [[Substack]] or [[Ghost]] being two common paid subscriber platforms.
11
12I'll use Ghost as my example.
13
14- The "My Cool Ghost Site" has both free and paid memberships; some content is available to all members -- sent via email, in RSS, and posted to the blog
15- Paid members get access to premium content -- they get it sent via email and/or can login to the Ghost blog to read it
16- assuming Ghost / a custom plugin has a feature to link your Ghost membership with your Bluesky login
17- The plugin would also generate endpoints for a Bluesky compatible custom feed
18- The algorithm is pretty simple here -- if the currently logged in user is a paid member, show them free and premium content; else, only show free content
19
20Right now all content is public on Bluesky, so you could still fetch the content / navigate to it. In fact, can you generate posts in a custom feed??? Or does it first have to be posted to an account, so that it could be included?
21
22Maybe something with blocks? Have a free Bluesky account, `@my-cool-ghost-site.com`, and a premium one, `@members.my-cool-ghost-site.com`. When someone adds the custom feed, if they aren't a paid member, block them.
23
24Blocking everyone on Bluesky (pre-emptively!) except for subscribers is not really a great method. This is probably another area where a Lexicon that supports premium content could be used.
25
26And, this might just be way easier to implement by adding [[Open Frames for Bluesky]].