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

Developers

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. For /moderation/banned and /moderation/banned/events.

    67 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

    Under Consideration  ·  1 comment  ·  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)
  2. In the channel settings, you may specify a "profile accent color" to represent your brand.
    Right now, this isn't exposed in the API at all.

    62 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

    2 comments  ·  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)
  3. When a "gift bomb"

    there is no way to gather all the gifts into one event.
    Each gift in a bomb should have a ID to link it to the header event.

    IRC sends a header saying "x is giving out y subs to the community"
    But the USERNOTICE events, don't say they belong to that event.

    Please provide a way to group the events, something as simple as a "parentid" in the child gifts subs, that'll link to a "childid" in the header event.

    This header and extra ID's need to be provided on the PubSub event…

    56 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  ·  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)
  4. Please provide a Helix endpoint for inbound and outbound host status/information

    and by extension a webhook

    53 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

    4 comments  ·  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)
  5. 52 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

    0 comments  ·  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)
  6. For managing Bans without having to create an IRC connection and to remove the issue of running into the global message limit when banning large numbers of users or cleaning out a large banlist

    47 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  ·  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)
  7. The chat_moderator_actions topic in the PubSub documentation appears to only work with a broadcaster OAuth token. This prevents third-party modding tools that don't use some kind of centralized system from accessing information that is vital for effective modding (such as which mod performed an action, actions that aren't otherwise visible like unbans and viewing and approving messages filtered by AutoMod).

    With a centralized system the broadcaster could provide a token somehow that the moderators don't need to have access to directly, however with purely clientside tools this is not feasible. I'm also not sure why moderators should not have access…

    47 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

    3 comments  ·  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)
  8. Please provide an API to allow developers to create update and fetch the new "profile block" at the top of panels.

    IE the new Social links section and the new bio/description block

    44 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

    6 comments  ·  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)
  9. Provide an API for third parties to control soundtrack

    Including but not limited to

    • Play/Pause
    • Volume control
    • Playlist entries in "now playing"
    • Current song that is playing
    • Play head position in the current song
    • playlist play head position
    38 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

    2 comments  ·  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)
  10. Extend the Videos API via a "metadata" endpoint, that provides additional data about the video.

    Including but not limited to

    • Category changes during the video
    • Offsets are relative to the source video that the video is from. So for a highlight it would report the video it was cut from and include where in the origin file the highlight is cut from.

    For Example: https://api.twitch.tv/helix/videos/metadata?id=1234
    Metadata would support up to 100 (or 50) id's at once like Get Videos

    Returns examples

    A video of type archive
    {
    "data": [
    {
    "id": "1234",
    "duration": 18000,
    "chapters": [
    {
    "offset": 0,
    "game…

    37 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

    0 comments  ·  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)
  11. The idea is simple: Add the same phone & email verification options to the ability to actually follow a channel, and thus also giving account age requirements to be able to follow a channel. This will allow small streamers being targeted by hate raid Bot attacks to simply prevent the bot attacks easily, instead of being driven off the platform.

    36 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

    5 comments  ·  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)
  12. We third party dev's often build tools that assist with moderation actions/services for broadcasters.

    We tell Moderators to enable 2FA, but we have no way to check it.

    It would be useful to block Logins to our tool if 2FA is not enabled. But 2FA data is not surfaced in the API and there's no way to require a User to be 2FA during the login/oAuth loop.

    I'd like to see the users endpoint(s) provide 2FA status.
    I expect this to be behind the user read or openID scopes.

    openID allows email verified. Why not 2fa status (for example)

    Worth…

    33 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  ·  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)
  13. In a similar fashion as

    https://twitch.uservoice.com/forums/310213-developers/suggestions/39228784-extend-clips-api-to-provide-the-mp4-url-so-editors

    The Videos API should be extended to provide the (original) VOD to authenticated users where that user is an Editor or better of the channel.

    As in unmuted.

    For the purpose of backing up/taking a copy of the Twitch stream and/or taking that content (that the streamer owns) for use on other platforms.

    Editors can already do this via the Video Dashboard, so the API should support this also

    29 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

    3 comments  ·  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)
  14. Please provide an API to

    • Create
    • Replace
    • Update
    • Delete

    For the new announcements feature.

    Additionally this should work with a broadcasters token or a moderators token

    Usecase: much easier to automate and manage announcemtns externally.

    We could for example auto update the "message of the day" and/or change the message based on timers or external factors.

    We could also use it for the "Death Counter" of the game the streamer is playing on Stream

    28 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

    2 comments  ·  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)
  15. The v5 endpoint contains the follower's account creation date, the new endpoint (https://dev.twitch.tv/docs/api/reference#get-users-follows) does not.

    Knowing when a follower created their account is very useful to moderators monitoring recent follows to keep an eye on potentially problematic users (new account could mean a previously banned user returning) or to detect mass follows from bots (which often have a similar account creation date). Monitoring recent follows is especially useful in follow-only chat mode.

    While it is possible to get the account creation date from the "Get Users" endpoint (https://dev.twitch.tv/docs/api/reference#get-users) and then merge it with the follower data,…

    28 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

    0 comments  ·  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)
  16. "The v5 endpoint searched for the channel title and category. Use “Search Channels” to match channel name or title." on https://dev.twitch.tv/docs/api/migration is wrong because the new API does not matches the title! There is no replacement for title searching!

    28 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

    Investigating  ·  4 comments  ·  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)
  17. With the removal of the Follow Create endpoint.

    A "non moderation bot" can no longer be automatically added to a channel.
    The owner of the bot would have to "login" to the account and manually follow the channel(s) the bot joins.

    A "non moderation" bot doesn't run moderation commands, so giving it "mod" wouldn't make sense. (Which would bypass the follow requirement)

    Please provide a way to "authorise adding a bot to a channel" that will auto follow the bot to the channel. For this purpose

    This could be similar to how Discord does bots, where to add a bot…

    27 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

    Investigating  ·  9 comments  ·  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)
  18. Add support to access/query and maybe even create/edit/delete community challenges.

    For example to unlock a big "something" in a game, when the community goal has been reached.

    26 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

    3 comments  ·  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)
  19. Moderators are able to add a reason/description whenever they ban people in chat (/ban [username] reason)

    This information is currently only available in the "not allowed to use" GraphQL-api, but should also be added to the documentet endpoints; /moderation/banned and /moderation/banned/events

    (Ban-reason is different from moderator-comments.)

    26 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

    2 comments  ·  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)
  20. For the purposes of GDPR it would be useful to have the following webhooks:

    • When a Streamer installs an extension
    • When a streamer activates an extension
    • When a streamer deactivates an extension
    • When a streamer uninstalls an extension.

    The most important one is the uninstall, it allows us the third party to be notified of an uninstalled.

    The Shopify platform has this with the rule that a third party should, automatically delete all Store (and that stores customer data) 30 days after that hook triggers.

    We need/should do the same, delete any broadcaster, or broadcaster viewer (and subscribers) data 30…

    25 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  ·  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)
  • Don't see your idea?