videoinfo is a partial duplicate of imageinfo, which is just a really bad idea.
the only property it currently adds is "derivatives" (listing transcoded files).
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T132946 Deprecate videoinfo | |||
| Open | None | T89971 ApiQueryImageInfo is crufty, needs rewrite | |||
| Open | None | T132947 Make it possible for extensions to add additional info to the fileinfo/imageinfo response. | |||
| Declined | None | T134641 Make TextHandler use the timedtext videoinfo api for remoteDB sources | |||
| Open | None | T187759 API is returning 500 status code | |||
| Open | None | T201205 Bad metadata for a single file errors out the complete imageinfo prop request | |||
| Open | None | T235011 API query times out |
Event Timeline
Comment Actions
21:12 #wikimedia-tech: < Krinkle> thedj: Is this still something we want to do? https://phabricator.wikimedia.org/T132946
Yes, this part of imageinfo/videoinfo is still crufty. I think that @Anomie agrees, that no one is really happy with TMH extending ImageInfo and then calling that copy videoinfo. It's just that no one has proposed a better route yet, and is willing to deprecate this oft used endpoint.
And yes, i'm 10 days behind in IRC pings ;)