zzstoatzz.io
+6
-8
.github/workflows/status-maintenance.yml
+6
-8
.github/workflows/status-maintenance.yml
···
102
102
- docs/deployment/overview.md if it exists
103
103
- Fetch https://atproto.com/guides/overview to understand ATProto primitives
104
104
- Fetch https://atproto.com/guides/lexicon to understand NSIDs and lexicons
105
+
- fetch and read: https://overreacted.io/open-social/ to understand the vision of open social
105
106
106
107
this context helps you explain things accurately, and accessibly without over-simplifying.
107
108
···
117
118
118
119
INAUGURAL EPISODE (first time):
119
120
- introduce what plyr.fm is: decentralized music streaming on ATProto
120
-
- explain the core value prop: your music data lives in your PDS, portable between apps
121
+
- explain the core value prop: your music data lives in your PDS, portable between apps (open social)
121
122
- cover the technical foundation that's been built (summarize from STATUS.md)
122
123
- set expectations: this is an early-stage project, rough edges exist
123
-
- tone: "here's what we're building and why it matters"
124
+
- tone: "here's what is being built and why it could matter"
125
+
- work chronologically from beginning to end, don't heavily bias towards nascent or recent work
124
126
125
127
SUBSEQUENT EPISODES:
126
128
- focus on what actually shipped since last episode
127
129
- use git history to determine timing ("last week" vs "earlier this month")
128
130
- don't re-explain the whole project - listeners already know
129
-
- tone: "here's what changed"
131
+
- tone: "here's what changed since last time"
130
132
131
133
### tone requirements (CRITICAL)
132
134
···
136
138
- don't over-use superlatives ("amazing", "incredible", "exciting")
137
139
- explain technical concepts through analogy, not hypey jargon
138
140
139
-
BAD example:
140
-
"Host: Wow, they've done an incredible job building this decentralized music platform!"
141
-
"Cohost: Absolutely! The ATProto integration is amazing!"
142
-
143
141
avoid excessive phrasing:
144
142
- "exciting", "amazing", "incredible", "impressive", "great job"
145
143
- "the team has done", "they've really", "fantastic work"
···
147
145
148
146
pronunciation: "plyr.fm" is pronounced "player FM" (not "plir" or spelled out)
149
147
150
-
target length: 2-3 minutes spoken (~300-400 words)
148
+
target length: 2-3 minutes spoken (~300-400 words) (it should be 4-5 if its the first episode)
151
149
152
150
### generate audio
153
151