Extend clips API to return the offset/start point
to request the offset of a clip being added to the API
Use cases include
- Deduplication of Clips submitted to a clips submission thing
- Recreate the clip from a copy of the vod.
- Using the offset to easily spot "hype" points of a stream for channel editors making highlights to focus on that point aka "heatmaps of popular stream time points"
- From CSharpFritz: Show clips in the order that they naturally occurred, and not the time that they were created
Please allow me to gratefully exhort Twitch to add this feature to the Helix API. I'm experimenting with ways to synthesize multiple-angle RP situations to try to make the RP experience more accessible and easier to create. If the current API is deprecated before this feature is added, my efforts will be pretty well stymied.
The way this works with the Kraken API is not without its quirks, but even so, it is vital to a whole catalogue of roughly synchronous use cases that don't require absolute precision. The application I'm building to enhance role-playing streamers' and audience members' experiences really won't be possible to maintain without this feature (or implementing some sideways and expensive way of simulating it), and there's a whole swath of unexplored territory beyond which will be much more difficult to explore without it. Thank you very much for your consideration.
The importance of being able to fully associate clips and videos to one another for applications not being supported yet is worrying. The use cases for this endpoint is one that is very much needed and with the functionality already being supported in v5 it doesn't make sense why it can't be supported in Helix.
With the announcement of the upcoming shutdown of the v5 API, I'm appalled that something this essential still hasn't been implemented. To give you an idea of how important it is, *Twitch itself* REQUIRES this information in order to have the "Watch Full Video" link on clip pages.
Without this information, my service (StreamXRef) won't be able to use clips as a cross-reference point since there would be no way to know when in the video the clip occurred.
My use case for this is that I would like to be able to show clips in the order that they naturally occurred, and not the time that they were created
This is the only missing piece of data that holds us back from migrating away from the old api.
We're using it for clip deduplication and to recreate urls.