Samuel
@samuel.fm
what do you mean?
1 1I'm most likely missing something but I would have expected the embedded video to be within embed -> video (just like images in the other example). Instead right now all properties of the video struct are just one level up right within embed.
2 1at a guess, I think images are like that because it’s an array
2 1there’s no reason the properties of the video can’t be at the top level. is that causing you issues?
1 1a little, yeah. It's because embed is polymorphic and I parse its (nested) content based on the $type within embed
1 1I thought I saw the same for record. Let me find an example
1 1oh, curious. @divy.zone is there a reason for this? should videos be different?
1I think this is just the difference between a PostView response from the AppView and a Post record with an embedded video but I may be wrong. The PostView includes appview-specific stuff i.e. links to our CDN and such.
1 3hm, I think both embed examples are from the AppView layer. I didn't look into the "record" subtree
1 1Oh I guess the difference is in the embed.video#view vs embed.images#view?
Yeah in that case we didn't wanna add it to a list cause there can only be one video per post.
1 4But what about external am record. Those also get nested cf. bsky.app/profile/skee...
1 1oh idk in that case, maybe @divy.zone has some opinions on it though?
I'm not really sure what use the nesting has
1