audio streaming app
plyr.fm
docs: add supporter-gated tracks section to artists page (#1051)
document the experimental ATProtoFans integration for track gating,
note the binary support limitation, and link to the permissioned
data proposal as the path toward artist-controlled gated storage.
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
authored by
Claude Opus 4.6
and committed by
GitHub
0e8b724f
8f47fcde
+24
docs/artists.md
+24
docs/artists.md
···
54
54
55
55
paste a plyr.fm track link into any oEmbed-compatible platform and it will render a player automatically.
56
56
57
+
## supporter-gated tracks
58
+
59
+
:::caution[experimental]
60
+
this feature is early and has limitations — see below.
61
+
:::
62
+
63
+
plyr.fm integrates with [ATProtoFans](https://atprotofans.com) to let artists gate tracks behind supporter status. when a listener tries to play a gated track, plyr.fm checks whether they support the artist — if they do, they get access; if not, the track is locked.
64
+
65
+
today this is a **binary check**: a listener either supports you or they don't. there are no tiers, amounts, or expiration windows — any active support relationship grants access to all your gated tracks.
66
+
67
+
### how it works
68
+
69
+
1. upload a track and toggle **supporter-gated** in the track editor
70
+
2. when a listener hits play, plyr.fm checks their support status via ATProtoFans
71
+
3. supporters get access; everyone else sees a lock
72
+
73
+
### what's next
74
+
75
+
because ATProto doesn't yet have a permissioned data primitive, gated audio currently lives in plyr.fm-managed storage rather than on your PDS. this is the one exception to the "your music, your data" promise — and we want to fix it.
76
+
77
+
the ATProto team is [exploring permissioned data](https://dholms.leaflet.pub/3mfrsbcn2gk2a) through concepts like **buckets** — named containers with access control lists that could let private blobs live on your own PDS. once that ships, gated tracks could move back to artist-controlled storage while still enforcing access rules at the protocol level.
78
+
79
+
we'd also like to support more expressive gating — tiers, time-limited early access, per-track pricing — as the ecosystem matures.
80
+
57
81
## your data
58
82
59
83
because tracks are ATProto records, you can: