fm.freemix.track.comment
A comment on a FreeMix track. Authored by the commenter's DID, stored in the commenter's PDS. Track-level only — no stem targets. May be timestamped to a waveform position or apply to the whole track. Replies carry BOTH the track ref and the parent-comment ref so a reply survives parent deletion by flattening to a top-level track comment.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | track.freemix.fm |
| Indexed |
Record
record · key tidProperties
maxLength: 100
replyParent
string · at-uriOPTIONAL. AT URI of the parent comment when this is a reply. ABSENT = top-level. Depth is enforced at the API/client layer (v1 = depth-1), NOT by this lexicon — schema stays permissive so the depth cap can be raised later without a migration. On parent deletion, the write-path drops replyParent/replyParentCid and the reply flattens to a top-level comment on `track`.
maxLength: 3000
replyParentCid
string · cidOPTIONAL. CID of the parent comment record. Present only alongside replyParent; dropped together on flatten.
maxLength: 200
Comment body. Protocol max; API may enforce tighter without a migration.
maxLength: 3000maxGraphemes: 1000
timeOffset
integerOPTIONAL. Seconds from the start of the track this comment is anchored to. ABSENT = whole-track comment. Never defaulted to 0 — absence is semantically distinct from a comment at 0:00.
minimum: 0
AT URI of the fm.freemix.track this comment is on. Required on EVERY comment, replies included — a reply references the track independently of its parent so it can flatten to top-level if the parent is deleted. Track-level only; stem targets are out of scope for v1.
maxLength: 3000
CID of the track record at comment time — pins which version the comment (and its timeOffset) was anchored to.
maxLength: 200
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
A comment on a post or another comment
-
pub.oysters.comment
recordA comment in a post's discussion, or a reply to another comment.
-
Record containing a comment on a VOD.
-
A comment on a deck, card, or note.
-
A text comment on an AT-Proto entity. Users can comment on records, users, PDSes, or lexicons to provide feedback, ask questions, or share insights.