752 results found
-
Twitch Connect - app ids shared in api At the moment I have not found any way to get users app id (in my case Riot Account ID) which would allow me to authenticate user using Twitch API and at the same time make sure that user owns this Riot Account. Currently Riot does not support their own way of authentication for third-party developers, therefore Twitch would be great in this case if they shared app ids connected to the Twitch accounts.
2 votes -
Mute does not work mute parameter does not work on mobile it is always muted just like autoplay
2 votes -
Change description of broadcaster_id in create clip The description of the broadcaster_id inside of the Create Clip endpoint is very confusing because it states that this is the id of the stream but it really is the id of the broadcaster as the name suggests.
2 votes -
Make it easier to leave reviews and allow Viewers to leave reviews Add a link to the settings menu on extensions to allow users to easily find the feedback form.
https://cdn.discordapp.com/attachments/588760082854969488/697095376993517568/unknown.png
2 votes -
Wording on refreshing a token is confusing https://dev.twitch.tv/docs/authentication#refreshing-access-tokens
"
How to Refresh
To refresh a token, you need an access token/refresh token pair coming from a body. For example:
"You need only the "refresh token" and "client secret"
You can lose the access token, and still get a new token if you have a refresh_token
2 votes -
Helper: viewer is misleading as the viewer object is populated on all views not just the channel page https://dev.twitch.tv/docs/extensions/reference#helper-viewer
The Twitch.ext.viewer object is a collection of info about the twitch viewer that is watching the channel page where your extension is activated. It will only be populated if the viewer is logged in, and only after the `onAuthorized` callback has been called. Accessing its properties will otherwise return `null`.Should be
The Twitch.ext.viewer object is a collection of info about the twitch user that is watching the extension view.Or something, as the
viewerhelper object exists on all views!2 votes -
Get Broadcaster Subscriptions docs example incomplete The Get Broadcast Subscriptions docs https://dev.twitch.tv/docs/api/reference#get-broadcaster-subscriptions was updated to include gifterid and giftername fields, but neither of these were added to the example.
Also, the example is erroneous because it shows the same user id for both broadcaster and subscriber, but they represent different usernames, which is impossible.
2 votes -
Document error responses https://dev.twitch.tv/docs/authentication/getting-tokens-oauth#oauth-client-credentials-flow
There's no information about error response and it doesn't seem to be fully compatible with RFC 6749 which means I can't find info about possible errors easily.
2 votes -
Helper: Actions - don't work in the rig From: https://github.com/twitchdev/issues/issues/56
Brief description
Documentation describes that there are functions such as
followChannelandrequestIdSharebut the documentation doesn't mention that these functions don't work in the rig (at time of writing)https://dev.twitch.tv/docs/extensions/reference#helper-actions
Additional context or questions
https://discordapp.com/channels/504015559252377601/523676096277905419/676767529666084864
2 votes -
onPositionChanged still in docs From: https://github.com/twitchdev/issues/issues/36
Brief description
https://dev.twitch.tv/docs/extensions/reference#helper-extensions
The JS helper/callback function
onPositionChangedis still documented but is no longer relevant post video component redesignExpected documentation
Section Should be removed
2 votes -
mixpanel support in Twitch extension It would be nice to provide mixpanel support too for analytics for some cases.
2 votes -
Add GET https://api.twitch.tv/extensions/<client ID> as a documented endpoint If you call GET https://api.twitch.tv/extensions/<client ID> you get a JSON back with the information about the extension. This is currently undocumented, but it would be a real useful took for discoverability and management, but being undocumented, it wouldn't be wise to use in a production environment. If this endpoint is planned to be kept, can it be added to the documentation for our use?
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 -
2 votes
-
How to link out on a mobile extension Twitch documentation does not state how to handle opening a new window on a mobile extension.
2 votes -
Allow pubsub whispers in Developer Rig The Twitch Developer Rig should support pubsub whispers. It current supports normal broadcasts, but not whispers to target a specific user's frontend.
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 -
iOS Player Object I want to a way to embed the Twitch player natively inside an iOS app. The existing web embed is not as efficient or usable as a native player could be.
2 votes -
Add Optional OAuth Scope Selection to Authorize Page In order to give the end user more control, applications may be developed to have dynamic scopes, which currently is on the third-party developer's side to manage, such as providing a list of checkboxes to determine which permissions to grant.
I suggest adding a parameter to <id.twitch.tv/oauth2/authorize> to turn the listed permissions into checkboxes, and only the checked permissions returned in the scope list that accompanies the resulting token. This will make the user's interaction with the permissions feel more seamless, as well as prevent "backouts" when the user is presented with a list of access permissions they can't "un-choose".1 vote -
No deja No me deja iniciar cesión en mi play
1 vote
- Don't see your idea?