You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Instagram posts with a mix of photos and videos are not handled well, the videos are just dropped. This is mostly due to the fact that there is no clear way to represent this in Microformats, since there is no way to express ordering between photo and video values.
I've been thinking about this one the last few days, and I wonder whether it would make sense to store the canonical url of the post into the video property. We'd have to document that clients can't directly use a video player, but are responsible to fetch the URL themselves and parse it, optionally using a call back to the microsub server, as the 'preview' call probably shall return the actual video url.
That would solve it without the microsub server having to do a lot of round trips when importing an instagram feed, although, in the end, that might end up to be more performant.
Currently Instagram posts with a mix of photos and videos are not handled well, the videos are just dropped. This is mostly due to the fact that there is no clear way to represent this in Microformats, since there is no way to express ordering between
photo
andvideo
values.Here is an example post with a mix of photos and videos: https://www.instagram.com/p/BZWmpecjBwN/
The text was updated successfully, but these errors were encountered: