970 results found
-
Clarify read-only nature of IRC MODE command While you do a good job of stating that the IRC interface deviates from the RFC, as well as where and how it deviates from the RFC, it may be beneficial to specifically call out the deviation that the MODE command is server-generated (read only), instead of being a keyword that can be generated by a client.
In other words, my bot cannot issue its own "MODE #channel +o nickname" command via the IRC interface (like it can on IRC), it can only receive notifications from the server that the server has sett one of those modes. One sentence covering…
2 votesThanks for the head’s up!
-
Real-time viewer count pubsup topic This is great documentation. I'm asking if there will ever be a pubsub topic for sharing real-time viewercounts? I've noticed the get channel endpoint only updates every 15 minutes.
5 votes -
Enabling Drops This guy does not resemble reality. Part 4: Enabling Drops; Click Your Console ( Where is it, I clicked Your Dashboard); Click Drops ( Where is it? How am I suppose to find it?).
Not approvable3 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
3 votes -
The Validate requests endpoint omits the expiry from the example response URL
https://dev.twitch.tv/docs/authentication#validating-requests
{
"clientid": "<your client ID>",
"login": "<authorized user login>",
"scopes": [
"<requested scopes>"
],
"userid": "<authorized user ID>"
}should be
{
"clientid": "<your client ID>",
"login": "<authorized user login>",
"scopes": [
"<requested scopes>"
],
"userid": "<authorized user ID>",
"expires_in": timeInSeconds
}4 votes -
Please provide a API/Hook for when a broadcaster leaves an extension review When a caster leaves a review.
Currently we can only get these reviews manually via the console.
Please provide, one or more of:
- An API, to collect the spreadsheets like existing ext analytics
- An API, to collect the reviews,
- A webhook to collect reviews into our own system(s) in real time
14 votes -
Extension user content moderation The new mod view is great and all.
But it would be useful if extensions can add items to the Automod queue for moderators to moderate user submitted content (as per the new #7 guidelines for extension content moderation).
And said item have webhook/EBS powered accept/reject buttons or similar
16 votes -
Search is missing from the Embed landing page https://dev.twitch.tv/docs/embed
is missing the docs search function top left/first item in the nav
4 votes -
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 -
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
viewer
helper object exists on all views!3 votes -
Extension Pubsub Docs missing whisper targer. https://dev.twitch.tv/docs/extensions/reference/#send-extension-pubsub-message
The docs say Valid values: "broadcast", "global".
But, the target 'whisper-opaqueId' to send "per user" pusub message is missing.
14 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.
3 votes -
Fix ideas for Streams pagination Pagination on some Helix endpoints, such as Get Streams, is just bad, and can lead to endless looping. So here are some suggestions.
The goal of any solution would be for any dev paging through any Helix endpoint to have a clear and reliable indication of "there are no more results, you can stop pagination". And if for whatever reason that can't be indicated, the endpoint should safely return an empty data array rather than looping the user back to the start.
Currently, the final page of the Streams endpoint still contains a cursor (for use in before) so simply…
8 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.
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_id
in 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
- Don't see your idea?