978 results found

1. Stream video player embed should not autoplay without user consent

   Problem:
   As livestream video embed is included on the website it will autoplay without the consent of a user to be counted as a viewer within a stream, various broadcasters abuse this logic by creating silent 1px embeds on third-party domains (wikis, product pages & similar). Not only that unnaturally inflates the viewcount numbers of the streamers in question but as well it hurts statistics and the community of the categories in which said broadcasters streams, in addiction this incredibly hurts users with limited network bandwidth while they try to use said websites where embed is included cause they do not wish to have their data used on the media they have not consented to, which in effect can ruin a twitch reputation as a platform when said users would try to investigate their bandwidth usage.

   Possible solution steps:
   - Paused livestream video player within embed should not count to live viewer count (possibly already done, but better to mention)
   - Disable autoplay from the embeds displaying video of the live stream
   - Deprecate the autoplay property from the query string parameters on Iframe src
   - Function "play()" from Synchronous JavaScript Playback API should not execute or not be defined until user interacts with an embedded player by themself.

   What it solves:
   - Removes bad actors who use embed functionality to unnaturally inflate their numbers
   - Protects users with limited bandwidth
   - Makes sure that EU GDPR laws are maintained
   - Protects Twitch reputation for current and future advertisers

   Problem:
   As livestream video embed is included on the website it will autoplay without the consent of a user to be counted as a viewer within a stream, various broadcasters abuse this logic by creating silent 1px embeds on third-party domains (wikis, product pages & similar). Not only that unnaturally inflates the viewcount numbers of the streamers in question but as well it hurts statistics and the community of the categories in which said broadcasters streams, in addiction this incredibly hurts users with limited network bandwidth while they try to use said websites where embed is included cause they do… more

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Embeds  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Allow 'In Development' versions to be deleted or re-numbered

   Sometimes you can end up with an extension where you have multiple versions under 'In Development', but ultimately you can only release one version.

   Unlike the current active version, in-development versions aren't deprecated when a new version is released, so you can end up with old in-development versions that you can't do anything with (assuming you want to stick to some form of a convention for the version numbers).

   It'd be great if the dashboard allowed you to delete/deprecate in-development versions, so you can clear out the extra versions, or allowed you to change the version number for in-development versions, so that these extra versions could be re-used while sticking to a numbering convention for releases.

   Sometimes you can end up with an extension where you have multiple versions under 'In Development', but ultimately you can only release one version.

   Unlike the current active version, in-development versions aren't deprecated when a new version is released, so you can end up with old in-development versions that you can't do anything with (assuming you want to stick to some form of a convention for the version numbers).

   It'd be great if the dashboard allowed you to delete/deprecate in-development versions, so you can clear out the extra versions, or allowed you to change the version number for in-development versions,… more

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Extensions  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. An iOS Embeds UI update

   Ever since the embed updates back in 2020, the mobile embed experience has been sub-par. The suggested way to embed on iOS was to embed on your website, then load the website in a web view in your app. This was so that we could pass along the parent parameter. However it results in a number of issues that I'd like to suggest solutions for.

   First, the issues:

   1. The UI of the player is unusable. If you load your own website embed, then it is far too small to use. If you simply load the pop out player's URL, then the elements are too big and overlap each other and block UI elements from being useful.

   2. Embedding in the way described above means that there are desktop controls (for example the keyboard shortcuts in the settings menu).

   3. Web browsers mostly prevent starting a stream unmuted. This is true even in an iOS WKWebView.

   Possible solutions:

   1. A parameter like mobile=true or something similar to let the player know to lay itself out in a way that is mobile friendly.

   2. Twitch or the community (probably me) can create an SDK to allow embedding natively. It might be able to use an app or user access token for the Twitch API in replacement of the parent property on web.

   3. Twitch can expose a stream URL through the Twitch API, which can require an app or user access token. Stream URLs are very easily accessible anyways, it'd be nice to have a Twitch approved way to access them. This would allow us to create our own player, and the developer agreement could require things like follow/sub buttons be displayed alongside it.

   These are just a few possible solutions. I know that Twitch wants to maintain a high level of quality for its users and developers, and this is a great opportunity to do so!

   Feel free to hit me with any questions or poke holes in my solutions.

   Ever since the embed updates back in 2020, the mobile embed experience has been sub-par. The suggested way to embed on iOS was to embed on your website, then load the website in a web view in your app. This was so that we could pass along the parent parameter. However it results in a number of issues that I'd like to suggest solutions for.

   First, the issues:

   1. The UI of the player is unusable. If you load your own website embed, then it is far too small to use. If you simply load the pop out player's URL, then… more

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Embeds  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Allow us to sort clips by time

   This already exists with the videos endpoint. Clips already have a created_at value so sorting by it should be easy to implement. You could actually reduce API calls if you allowed sorting by date.

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Provide "Shared Bans" information to third Parties

   With more Information on the "Shared Bans" feature now being available, it would be nice to have information about them available to third Parties, specifically in 2 Locations:

   1. When a user from a shared List joins and is marked as restricted or flagged, this should be returned on IRC - it probably already is, but the relevant tags should be documented and usable for third parties providing chat integrations / moderator tooling
   2. An API endpoint to GET which streamers a mutual sharing has been made with or a way to query a user's "flagging" status in a channel to allow restrictions on said user in third party products (Like community game servers, Chatting Platforms, Websites, etc)

   With more Information on the "Shared Bans" feature now being available, it would be nice to have information about them available to third Parties, specifically in 2 Locations:

   1. When a user from a shared List joins and is marked as restricted or flagged, this should be returned on IRC - it probably already is, but the relevant tags should be documented and usable for third parties providing chat integrations / moderator tooling
   2. An API endpoint to GET which streamers a mutual sharing has been made with or a way to query a user's "flagging" status in a channel to allow… more
   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Get Broadcaster Subscriptions with additional subscription informations

   It would be very nice to have additional information on the subscription of a specific user, for example date of the subscription, how many consecutive months the user have been subscribed and the total months that the user was subscribed.
   This could be easily added in the "Get Broadcaster Subscriptions" response so that for a specific broadcaster you can have the list of subscribers and for each one you can select the ones with streaks or total months to perform special actions with them

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Create endpoint to return list of all emote sets

   In V5, it is possible to get all emotes that existed on the platform via both
   "get-all-chat-emoticons"
   and
   "get-chat-emoticons-by-set" (when no sets are provided)

   This currently has no equivalence in Helix, and also has no listed migration path.

   This request is to create an endpoint that returns the list of all emote sets (and ideally their last update time) such as "get-all-emote-sets". This would allow a user to then get all emotes via the "helix get-emote-sets" endpoint that currently exists.

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Add image_format or is_animated field to helix Emote endpoints

   With the addition of animated emotes there is no way to tell from the emote API responses of GetChannelEmotes and GetEmoteSets if a new emote ( id starting with "emotesv2_") is a normal emote or an animated gif emote without downloading it and checking the file contents.

   Would be nice to have either a "format" field that tells you "png" or "gif", or at least a "is_animated" bool field for each emote.

   Use cases: Whenever you wanna show emote stats or emote info for a channel (like in a chat clients or stats website or emote panel) you often wanna count and display animated sets separately but currently the only way to tell is to actually download the /v2/ files and check the type.

   With the addition of animated emotes there is no way to tell from the emote API responses of GetChannelEmotes and GetEmoteSets if a new emote ( id starting with "emotesv2_") is a normal emote or an animated gif emote without downloading it and checking the file contents.

   Would be nice to have either a "format" field that tells you "png" or "gif", or at least a "is_animated" bool field for each emote.

   Use cases: Whenever you wanna show emote stats or emote info for a channel (like in a chat clients or stats website or emote panel) you often wanna… more

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   Investigating  ·  AdminJon Bulava (Developer Relations, Twitch) responded

   We will be updating the documentation to make it clearer that the image in the payload will always be a static image. We are also planning to document the URL schema for the CDN to retrieve the animated version.

9. Extend Automod Status

   Please extend

   https://dev.twitch.tv/docs/api/reference#check-automod-status

   To provide as much information as the new PubSub Topic for automod-queue.<moderator_id>.<channel_id> does

   https://dev.twitch.tv/docs/pubsub#topics

   Currently the API jsut does pass/fail
   But PubSub provides content/text/frames/reasoning.

   This endpoint may be used by third party tools such as tip alerts or extensions to determine if a message passes review or not.

   And if it is to be held and presented in a dashboard for moderation staff to review would be useful to include the additional information/reasoning for the block.

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Deferred  ·  0 comments  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Add occured_at timestamps to Clips API

    Add a occured_at timestamp that tells you when the content in the clip was actually streamed.

    Clips API objects have a created_at timestamp which is when the user made the clip but this can be months or years off from when the content in a clip actually happened if a clip was made from a VOD which makes created_at useless for a lot of use cases.

    Even for clips from livestreams this is an issue as users can cut clips from a 2 minute (90 secs?) window so the actual content of two clips with the exact same created_at timestamps can be completely different, which is surprisingly common in streams of fast paced games.

    occured_at can sometimes be calculated manually with the VODs created_at timestamp (from /helix/video) + the clips vod_offset (from Kraken clips API, helix doesn't have vod_offset) as long as the vod is still alive. Once a vod expires (or is deleted for channels with permanent VODs) it's not possible to calculate that timestamp for a clip anymore.

    Use cases:
    * Displaying clips in any form of time based ordering or filtering
    For example nobody wants to see a clip from two months ago when filtering for clips from the last week just because it was made three days ago from an old VOD
    * Deduplicating clips with the same content
    * Finding clips that happened right before or after a clip

    Basically for almost anything you'd use created_at for occured_at would probably be better, having to do all of that with created_at gives a terrible user experience as the results will be off from what a user wants or expects.

    Add a occured_at timestamp that tells you when the content in the clip was actually streamed.

    Clips API objects have a created_at timestamp which is when the user made the clip but this can be months or years off from when the content in a clip actually happened if a clip was made from a VOD which makes created_at useless for a lot of use cases.

    Even for clips from livestreams this is an issue as users can cut clips from a 2 minute (90 secs?) window so the actual content of two clips with the exact same created_at timestamps… more

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Mature flag in get channels and be modifable via patch channels

    Similar to

    https://twitch.uservoice.com/forums/310213-developers/suggestions/38375011-mature-flag-on-get-streams-endpoint

    But for the Get Channel information endpoint

    We should also be able to modify the flag via the Set Channel Information endpoint

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Cheer emote placement

    Please update eventsub to provide emotes used and placement of the emotes in the message similar to chat message does in order to allow us to easily reconstruct a cheer message to look like it did in chat

    similar to

    https://twitch.uservoice.com/forums/310213-developers/suggestions/40871443-pubsub-cheer-emote-placement

    Example

    The "emotes" tag from https://dev.twitch.tv/docs/irc/tags#privmsg-twitch-tags

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  EventSub  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. More detail on obtaining OAuth and OIDC tokens

    You provide information on how to remove a token, how to refresh a token, and how to define scopes for tokens, but you don't actually have any information on how to request a token, nor any sample code on that or applying token scopes. Given that this step is fundamental to any interaction with the Twitch API, this seems like a fairly major omission.

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Planned  ·  2 comments  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Add verified and known bot information to Helix API

    Currently the only way to fetch this information is via a semi-undocumented endpoint. Given Twitch's past record on these endpoints, I don't want to rely on them as by my experience they have a tendency to suddenly disappear. For this reason, I'm asking for this information to be added to the Helix API.

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Document API and IRC tags for replies

    Web chat users got access to the new "replies" feature, where you can mark your message to be a reply of another message.

    My suggestion is to add official documentation on how third parties can use this feature (for sending messages and for parsing received messages to be a reply)

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Investigating  ·  2 comments  ·  Documentation  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. PubSub Topics: no moderator topic examples/documentation

    https://dev.twitch.tv/docs/pubsub

    Has no examples or documentation for payloads for chatmoderatoractions

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Planned  ·  0 comments  ·  Documentation  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Fix TMI JS example with Promise handling

    https://dev.twitch.tv/docs/irc#overview

    Row:
    client.connect();

    Should be replaced with:
    client.connect().catch((err) => {console.log('Connection error!', err)});
    or smth like that.

    Let's show users how to write good code, and show them, that all Promises should be handled. Unhandled promise rejections is bad!

    Tmi.js Library also have connect example which contain promise handling

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Planned  ·  0 comments  ·  Documentation  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. msg-id tags page outdated/incorrect

    From: https://github.com/twitchdev/issues/issues/68

    Docs location: https://dev.twitch.tv/docs/irc/msg-id

    bad_ban_global_mod & bad_timeout_global_mod are gone for as far as i know (ref: https://blog.twitch.tv/en/2018/12/13/thank-you-global-moderators-4d44cfccf22/)

    Missing notices for vip events (vip_success, unvip_success, no_vips, bad_vip_grantee_banned, bad_vip_grantee_already_vip, usage_vip & bad_unvip_grantee_not_vip Might have missed some.

    First line says "These tags apply to both the" and than only names one thing.

    usage_untimeout has "/raid <username>" in the message.

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Documentation  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Twitch Drops

    Well the idea is that the twitch drop works a little different than it's today, because it's so frustrating to see a friend that watches just 10 minutes of stream getting a item that you looked around 5 hours and open multiple streams to get the same item and it don't drop for you, I think the drop could at least consider the time that the person watch because like it works now and thatn situation happens is sorrowfull for some people

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    5 comments  ·  Drops  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Add total count to streams endpoint

    Now it is not possible to get the number of streams in a certain section without sending a large number of requests to the API.

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close