Translate Ideas and Comments
Choose language:
There was an error during translation

Settings and activity

  1. 290 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    19 comments  ·  Developers » API  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We wanted to provide further context regarding this request as it is the most upvoted suggestion. There are several great use cases for providing the offset of Clips (including those above), but there are also ways in which it can be used negatively. For that reason, our initial decision was to no longer provide this information. With your feedback provided here, we are actively evaluating how to balance enabling good use of this information for creators while negating its potential for abuse. The status will be updated when we can share more information.

    An error occurred while saving the comment
    querySelectorAll commented  · 

    Since you guys didn't share details on how it can be used negatively we can't suggest solutions as a community. The only one I can think of is people recreating entire parts of vods from channels with lots of clips but one could just easily download the content live by scrapping the content.

    Also, please consider the negative parts of not including it. E.g.: More people web-scrapping content for the offset or making twice as many clip requests (one for the clip and another for the graphql api) for getting it.

    Anyway, I hope you guys can find a way to mitigate the negative parts while still letting us to know when they ocurred. It really has good use cases.

    Looking forward to this.

    An error occurred while saving the comment
    querySelectorAll commented  · 

    We need this, right now with the state of helix there is no way to link clips to their corresponding VODs. Clip API is virtually useless without context. Even the clip viewer on Twitch needs this to get the link to the video and the chat messages of the corresponding timestamp.

    Please, reconsider bringing this feature back. This is so basic that the removal of this feature could lead to increase rates of web scrapping, with negative repercussions for all of us.

    Edit to add my use case: I need to get the clips in a time range in the order that occurred in the stream and remove the duplicated ones

    querySelectorAll supported this idea  · 
  2. 92 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  Developers » API  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    querySelectorAll supported this idea  · 
  3. 7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Developers » API  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    querySelectorAll commented  · 

    Please, I don't understand how this is not a feature yet. You guys even needed this for building the official clip viewer for the "Watch full video" link or retrieving the chat (basic features).

    occurred_at or something like that is x100 times more useful than created_at so please provide both.

    At least bring vod_offset back but something permanent like occurred_at is better for consistency in our apps (e.g. filtering).

    Thanks for your work!

    querySelectorAll supported this idea  ·