976 results found
-
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.
3 votes -
Add parameter for dark mode with chat Add parameter to enable dark mode for chat please.
14 votes -
Date/Version on docs In the dev docs, can you add an "Updated" field with the date of when the page was last updated, or what versions the doc works with? Trying as a newbie now, there's some stale info in here.
2 votes -
Extension popout "by default" From: https://github.com/twitchdev/issues/issues/72
Brief description
By default, pop-out control is enabled for panel Extensions and for extension “live configuration views” (see the Live Config Path setting on the Asset Hosting tab in the Extensions manager).
https://dev.twitch.tv/docs/extensions/required-technical-background
The documentation suggests that extension developers can disable pop-outs. Which is not the case
3 votes -
User/Channel ID needs to be a string From: https://github.com/twitchdev/issues/issues/70
Brief description
The documentation for creating signing JWT's don't explicitly state that
user_id/channel_idin JWT's need to be an explicit string literalhttps://dev.twitch.tv/docs/extensions/building/#signing-the-jwt
https://dev.twitch.tv/docs/extensions/reference#send-extension-pubsub-messageExpected documentation
Where: exp is the Unix epoch timestamp when the payload will expire. Be sure to provide a buffer, to allow potential positive time drift. user_id is the Twitch user ID that owns the extension, where the user ID is cast as a string literal. role is set to external.3 votes -
HTTP Response codes unclear From: https://github.com/twitchdev/issues/issues/69
Brief descriptionSome endpoints return a 204 code no content.
But this is only highlighted in the example responses and not in the "main documentation"For example
https://dev.twitch.tv/docs/extensions/reference#send-extension-pubsub-message
https://dev.twitch.tv/docs/extensions/reference#send-extension-chat-messageEach endpoint documented could be extended to include usual HTTP response codes.
Expected documentation
The expected response code for success when theres no body response
Common non 2xx codes for the endpoints4 votes -
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_modare 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_vipMight 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 -
Webhooks topic(s) don't note required oAuth From: https://github.com/twitchdev/issues/issues/59
Brief description
Mod Change and Channel ban Change events don't note the required oAuth scope needed for the topic
https://dev.twitch.tv/docs/api/webhooks-reference#topic-moderator-change-events
https://dev.twitch.tv/docs/api/webhooks-reference#topic-channel-ban-change-eventsExpected documentation
Add, (similar to
Topic: User Changed)Authentication User Access Token must have the `moderation:read` for the user in questionAdditional context or questions
5 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
3 votes -
Information about config service unclear From: https://github.com/twitchdev/issues/issues/55
Brief description
https://dev.twitch.tv/docs/extensions/building#using-the-configuration-service
Doesn't mention the key bit of information regarding the size limit of 5kb
Additional context or questions
It's important to note here as people will start designing an extension and then discover the sizing limit late into construction of an extension. For clarity the limit should be noted here also
3 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
3 votes -
PubSub Docs don't mention Token Type From: https://github.com/twitchdev/issues/issues/25
Brief description
https://dev.twitch.tv/docs/pubsub#topics
PubSub documentation mentions the requirement to use an oAuth token, but doesn't directly specify which type of token, nor the requirement for the UserID of the token to match the UserID of the topic.
Authentication All topics require an OAuth token, but only some topics have a specific required scope (noted in the table below). Available Topics All topics require an OAuth token, but only some topics have a specific required scope (noted in the table).Expected documentation
…Authentication All topics require a User Access OAuth token, where the UserID of the token matches the9 votes -
Webhooks (Un)Subscribe Parameters From: https://github.com/twitchdev/issues/issues/14
Brief description
https://dev.twitch.tv/docs/api/webhooks-reference
the
hub.topicsection is out of date, in the JSON Body ParametersExpected documentation
Just changed it to something like "refer to later in this docs for the available topics"
4 votes -
Get Broadcaster Subscriptions Events From: https://github.com/twitchdev/issues/issues/8
Brief description
The subscription events API is documented as a Webhook topic. but not as a API Endpointhttps://dev.twitch.tv/docs/api/webhooks-reference#topic-subscription-events
It used to be in the documentation but is missing
Expected documentation
https://dev.twitch.tv/docs/api/reference#get-broadcaster-subscriptionsBut for
https://dev.twitch.tv/docs/api/reference#get-broadcaster-subscriptions-events8 votes -
mixpanel support in Twitch extension It would be nice to provide mixpanel support too for analytics for some cases.
2 votes -
An extension should be allowed to play a clip or highlight/other non live Twitch short Content For extensions that center around Clips it would be nice to be able to play that clip in the extension rather than having the viewer leave the extension/Twitch streamer to go and view said clip.
5 votes -
Create embeddable follow button would love a follow button that works like Twitter Follow/Tweet button. To avoid the need to oAuth-loop it and users would prefer that rather than granting access to their account for developers to throw a follow at any channel.
17 votes -
Add PKCE Support to the OAuth2.0 Authorization Code Flow I am currently developing a native Android application for Twitch and want to make use of the OAuth2.0 API. Since the Twitch Authorization Server doesn't seem to support the PKCE (Proof Key for Code Exchange), i will have to put my client secret into my native application, which isn't secure at all, because the app can easily be decompiled.
This is a requirement for all native apps, as stated by the IETF in RFC 7636 (https://tools.ietf.org/html/rfc7636).
I hope to see this implemented soon, because this poses a huge security risk for all native apps and their developers.
49 votes -
oAuth dialog jumps to the bottom of the page If you have a not very tall browser.
And you request, a fair chunk of the oAuth scopes.When you redirect the user to Twitch.
The Accept/Deny link page auto jumps down to the bottom of the page.
This means the first few/most "dangerous" scopes as well as the application name/logo and whom you are logged in as are above the fold of the page.
Basically "suggesting" to the user not to read all the scopes and just go accept/deny.
The auto jump to bottom of the page should be removed.
5 votes -
1 vote
- Don't see your idea?