Optional ReadonlycarouselThe carousel's children from the grid answer; absent on a media that is no carousel.
ReadonlymediaReadonlypositionReadonlyrowOptional ReadonlyauthorId?: stringOptional Readonlycarousel?: { children: readonly string[]; size?: number; slide?: number }A carousel's children (and count), as the grid answer carried them: what the comments sheet derives its carousel_media_id from.
Optional ReadonlydashManifest?: stringReadonlymediaId: stringThe media's container id (<pk>_<authorPk>); id stays the handle's own key.
ReadonlymediaType: 0 | 1 | 2 | 8Readonlyposition: numberOptional ReadonlytakenAt?: numberOptional ReadonlytrackingToken?: stringOptional ReadonlyvideoDuration?: numberReadonlystartingThe starting_clips_media_id the item's like carries: the pk of the clip
the contextual feed was entered from, the feed's own fact
(host.facts.firstMediaId). The app carries the field on the button
like of the entered item itself, where the entry clip and the liked item
are one media, so choosing the entry clip for a later item rests on the
field's name, not on the app's behavior; the double-tap like carries no
such field and is not modelled.
Optional ReadonlytrackingThe grid answer's organic_tracking_token on the media: the repost note's tracking_token.
What a carousel of the posts feed acts with: its media state and its own row, which a swipe replaces.