FileContent setting card bounds the same for every file type

Based on its display, AudioContent should really have a min-height of 3, but it looks like FileContent sets it to 6. Would it make sense to rewrite FileContent to have different bounds for different file types? It seems trivial to write that logic within FileContent.tsx, but seems better to set those properties in each [mime-type]Content.tsx file. How would I go about doing this? Sorry still confused on how data is flowing between FileContent and AudioContent.

[pvh]

I mean, could we make the comments an arbitrary type, like a ThreadContent, TextContent, ImageContent, etc.

(PS: if you haven’t read ARCHITECTURE.md it might fast-forward your understanding of how the system works behind the scenes.)

[pvh]

I would feel like hell yes. Time-coded comments should obviously be stored in the document somehow… arbitrary Content? Is that too crazy?

To broadcast listening position, you can send a “Presence” which broadcasts your userid, deviceid, and an arbitrary extra JSON encodable type to your peers. In BoardCard, you broadcast your selection color to your peers. This code is a little weird, I know, but look at usePresence in https://github.com/automerge/pushpin/blob/73193adc907b3c7c109b5f14453f9a838469f02b/src/renderer/components/content-types/board/BoardCard.tsx