701 results found
-
Update the page This page seems extremely out of date and the example deep links given don't work on tvOS.
2 votes -
Post a link to GitHub repo of full source code of tutorial "Check: If you want to see the completed code at this stage, its available on the Step 1 branch."
There are no links to the source code. It would be extremely helpful to have a link to GitHub repo with full set of code in this tutorial, to see how it all goes together.
2 votes -
Add overlay info to the player embed state We really need a way to determine what overlays display to the user so we can handle them gracefully. For example, we have no way of knowing when the mature overlay displays and this negatively affects our channel discovery UX.
2 votes -
Asymmetric JWT Signing Can we have the option for asymmetric JWT signing? I want to validate JWTs sent by twitch on publicly accessible software.
2 votes -
first extension how-to details Build your first Extension
Here’s an extension that just says ‘Hello, world!’where do i store this? how do i connect this with the twitch extension config page?
2 votes -
mixpanel support in Twitch extension It would be nice to provide mixpanel support too for analytics for some cases.
2 votes -
Insight into percentage of users that interacted with extension Looking for a metric that helps determine what percentage of viewers tried out the extension. A developer can track the viewer count on their own, but they cannot guarantee that the extension loaded for each user. A metric is desired to calculate that X% of users interacted with the extension, not just a raw value of unique interactions.
2 votes -
subscriptions revshare model bits revshare is obviously not enough to build a sustainable small/medium business on twitch extensions atm (except 1-2 examples out of hundreds). reasons behind as I see them - extensions are for small streamers mostly. middle/big ones are not that into extensions as a product category. thus even being featured 24/7 doesn't provide enough viewers to actually get $1000-5000 dev payout for most of devs. not to mention retention aspect.
moreover streamers are not that eager for bits. their current meta is to grow subs.
so the idea is to provide devs with ability to work with subscriptions and get…
2 votes -
Captions / transcript API for VOD Let extensions read the captions or transcript of a broadcaster’s live stream and VODs, with the broadcaster’s permission through a new scope. This would open up tools that help creators work with their own content: searching their past streams, accessibility, and editing workflows. Today every developer has to process stream audio separately to get the same thing.
1 vote -
Send out 'watchtime' on the API As we know, Twitch uses 'watchtime' (or similar variable) to check and give/earn viewers Channel Points, Watch Streak, Drops, Badges, to see if a viewer ACTUALLY viewing a LIVE stream and also give the channel a +1 Viewer Count.
Right now, we, the streamers, can only check, with the API, if they are in CHAT.. And they can be in the chat with the LIVE stream off/paused. Meaning: not watching. (like how the 'Community' button works over the stream's Chat, to see who's there)
We need access to the 'watchtime' too, so we can give those who ACTUALLY watches, our…1 vote -
Add Tag to Streamer by user visible only to the user who added it Allow users to add short tag to streamer accounts such as team name(s) and display tag in the followed channels list (left side of the screen) maybe near the viewer count for online stream entries. This would help viewers interested to know when a team they support is online.
1 vote -
API for channel allowed/authorized terms There are ways to list/add/remove blocked terms in the API, but nothing exists for allowed/authorized terms (unless I missed it)
I think that would make sense to add these endpoints
1 vote -
[Bug?] Multiple embeds play simultaneously We have an issue where multiple Twitch embeds on the same page plays simultaneously. I don't know if it is related to the way we embed, but I haven't found an issue describing it, so here goes.
Steps to reproduce:
1) Start an Incognito browser session (to ensure that there's no persisted Twitch user-preferences)
2) Open a HLTV news page with multiple Twitch embeds, e.g. https://www.hltv.org/news/44617/iem-atlanta-2026-quarter-finals-as-they-happened
3) All the Twitch embeds should be displaying a warning about mature content and a "Start watching" button. I.e. they do not display Twitch player buttons or a preview of the first clip frame.…1 vote -
Allow chatters to listen and get more information about redeems. Allow usage of channel.channelpointsautomaticrewardredemption.add to chatters, and add new endpoints to get information about channel redeems/rewards without broadcaster token.
We can already see this information in the rewards/awards menu and in chat. It doesn't expose any information that shouldn't already be publicly accessible.
The only redeems/rewards we can receive as a normal chatter is with text input, but almost everyone can agree that access to redeems/rewards without text input being redeemed is going to be useful.
1 vote -
Allow users to adjust the recommended channels tab or adjust it yourselves Here is an example. User has a bad experience with a streamer, gets a little upset, unfollows them, only to have said streamers' name come up in their recommended list (which they can't adjust) and which ends up upsetting them even more that they leave or want to leave the site. I'm giving you a real life example of how some people are leaving the site because of design choices. Twitch is much smaller than other platforms so not having extra customization hurts it more than them.
So I'm asking for you to either make sure when someone unfollows a…
1 vote -
The example and API confusion "cannot create a subscription for a user that does not exist"
Consider replacing whole manual with Node.js/browser-only libraries that work out of the box.
It is not a nice sign if ChatGPT can't figure this out and makes lots of meaningful assumptions that simply do not apply to logic of this API.
PS: Was trying to make a bot that simply plays sounds/reads messages aloud via web source in OBS. I assumed I could do this by just making a bot and sending a link to a streamer which they would add to their OBS. But, oh boy, the security/complexity…
1 vote -
curl examples are incorrect, uses ' instead of " Make sure you use " instead of ' in curl requests. Here's an example of what will happen otherwise:
console
$ curl -i -X GET 'http://localhost:8080/mock/users?id=29405430' -H 'Client-Id: ***' -H 'Authorization: Bearer ***'
curl: (3) URL rejected: Port number was not a decimal number between 0 and 65535
curl: (3) URL rejected: Bad hostname
curl: (6) Could not resolve host: Bearer
curl: (3) URL rejected: Bad hostname
1 vote -
Specifications regarding the Extensions Guidelines and Policies - Section 6 I have a few questions regarding the "Extensions Guidelines and Policies - Section 6 Bits in Extension". In my opinion, it contains some unclear points, specifically:
6.2.2 "Bits may not be used within your Extension: To allow an end user to use Bits to play a specific musical track or audio-visual work. (e.g. a jukebox-like functionality)"
This is already done by a variety of extensions, e.g. Sound Alerts. You pay for bits to play a specific sound ("audio-visual work"). Therefore, I would like to know why it is allowed in their case and consequently, this might need some more specification.…
1 vote -
Fix syntax the Authentication Manager class has tons of errors.
start -> Start
This function only runs once so if its waiting for an AI response, it will never actually work, make an example with a proper workflow that uses Update to check for the actual api responses properly. since this only runs once, it will just not do anything.
Application.OpenURL("{UserAuthInfo.Uri}{UserAuthInfo.UserCode}"); is incorrect in 2 ways. 1: uri HAS the usercode baked in, and 2, this just won't work. remove the quotes and just put UserAuthInfo.uri.
Theres probably more here that needs to be done but thats all i got so far.
1 vote -
Delete "Do not need to maintain a client secret." on "Device code grant flow" "Device code grant flow" actually needs secret id for token refresh flow. We do have to maintain secret. You may want to delete the point "Do not need to maintain a client secret." to prevent misunderstanding
1 vote
- Don't see your idea?