203 results found
-
Wrong selection in "HTTPS on localhost: the easy way" part, there is too much of the selection in "We recommend using Google Chrome. In the browser, enable the flag allow insecure localhost. To enable this flag, navigate to: chrome://flags/#allow-insecure-localhost and restarting your browser." sencetnce, for me, "allow insecure localhost. T" is secelted, but i think it should be "allow insecure localhost" only
1 voteAdded to this week's updates. Thanks!
-
Twitch is best platform As we all know that twitch is one of the best platforms for gamers. I want to embed it with my website https://routerinsider.com/best-router-under-150/ so that every person can get benefit from it. How can I embed it?
1 vote -
Add the Twitch CDN to the new default CSP for Extensions A Twitch Extension may choose to show profile images user or emotes of a channel.
At any given moment Twitch could change the CDN for those images from "static-cdn.jtvnw.net" to something else.
Under the new CSP policy, Extension developers need to define those URL's
But the current CSP doesn't include the Twitch CDN for image content in the default CSP.So a developer adds
static-cdn.jtvnw.netto their supported content domains.
If Twitch changes this, then the extension developer has to deploy an update including the new URL/domain in their CSP listThe default CSP should include Twitch CDN's by default…
9 votesLast week the domain was added to the img-src directive so developers do not have to specify this in their own allowlists.
-
Please revert the EventSub documentation format changes You changed the EventSub documentation between last night (Nov 16, 2021) and today (Nov 17, 2021). The new documentation is very confusing. Specifically speaking:
- The Subscription Types documentation links on the left side are out of order and like-kind events are not next to each other. For example, "Redemption Status Update" should be next to "Channel Points redeem reward".
- The Subscription Types are poor named, and it's a little difficult to figure out which Subscription Type goes to which event.
- The URL to go straight to the section in the Subscription Types is different from the type supplied in an…
1 vote -
Require Authentication for the Get Chatters Endpoint Currently, this endpoint: https://tmi.twitch.tv/group/user/<CHANNEL>/chatters
Can be used freely without any authentication or scope.
This is definitely being abused with the hate raids. It's been abused by malicious actors for a long time now. Why has this endpoint been created in such a way that there is zero barrier for a malicious actor to obtain user data?
Even the Get Polls endpoint (https://dev.twitch.tv/docs/api/reference#get-polls) requires both authentication and a scope!
How has that Get Chatters endpoint not yet been removed an replaced with a secure Helix endpoint, as stated here: https://twitch.uservoice.com/forums/310213-developers/suggestions/39145294-chatters-viewers-helix-api-endpoint
This is not ok.
13 votesThe Twitch API Chatters endpoint is generally available now.
-
Fixing an error There's an error in Section "Using cURL to get the information".
curl command needs param -X if you want to specify the method, for example GET in this case:
curl -X GET "<url>"...1 vote -
1 vote
-
dimensionn There's a typo under mobile guidelines:
"dimensionn"1 vote -
Expose VOD seek events I'd like to be able to know when a user seeks in a VOD that is embedded on my site. Ideally the event would contain the before/after timestamps so I can know the delta. Thanks!
1 vote -
Add the date/time of the ban to the moderationg/banned Similar to https://twitch.uservoice.com/forums/310213/suggestions/38203978
But include the date/time of when the ban record is for.
So for example
{ "user_id": "SomeID", "user_login": "SOMElogin", "user_name": "SOMEdisplay", "expires_at": "", "reason": "", "moderator_id": "15185913", "moderator_login": "barrycarlyon", "moderator_name": "BarryCarlyon" }I have no idea when this ban happened.
UseCase: For considering unbans when reviewing data in an external tool, the date/time of the ban will be considered to determine if the user who is banned has "served" their time or not
6 votes -
broken example example doesn't work "error":"Unauthorized","status":401,"message":"OAuth token is missing"}curl: (3) URL using bad/illegal format or missing URL
2 votes -
broken link the register your app link is broken
it's https://dev.twitch.tv/dashboard/apps/create
but should be
https://dev.twitch.tv/console/apps/create1 vote -
Bans/Banned events who did it Similar to https://twitch.uservoice.com/forums/310213-developers/suggestions/42562003-bans-who-did-the-action
But extended to the Helix API.
It would be useful to add who did a given "Ban Event" to the Get Banned Events for "service restart catchup" when using eventsub.
And useful to add it to the main "get banned users" for determining as a moderator using a tool the history or a user and to check with that moderator why that user was banned, but can't since the API doesnt' report who did it.
3 votes -
1 vote
-
Allow access to the "Get Channel Chat Badges" endpoint using an App Access Token All of the new emote and badge endpoints can be accessed using an App Access Token except for /chat/badges which needs a User OAuth Token.
I don't see why this endpoint needs a user token since the badges can be viewed publicly on the subs page and It doesn't reveal any private info about a user.3 votesThank you for reporting this issue. This endpoint now supports access with an App Access Token.
-
missing scopes Scope list says it's comprehensive, but it does not include user:read:email which is listed in some other docs.
1 vote -
Get the authenticated user's emotes (equivalent to existing Kraken endpoint) This Kraken endpoint provides the emotes a user has access to: https://dev.twitch.tv/docs/v5/reference/users#get-user-emotes
A similar functionality would be nice for the new API as well. It should contain all emotes a user has access to, for example Global Emotes, Subemotes, Bit Emotes, Emotes unlocked by Channel Points and so on (the Kraken endpoint is unfortunately missing some types of emotes).
The emotes returned would be for the authenticated user, with an appropriate scope required.
176 votesThis endpoint is available as of today in open beta.
-
Typo in extension.bits_transaction.create text The section title under the payload section of the
extension.bits_transaction.createevent is "Channel Hype Train End Notification Example" when it should read "Extension Bits Transaction Notification Example"1 vote -
1 vote
-
Extend clips API to return the offset/start point to request the offset of a clip being added to the API
Use cases include
- Deduplication of Clips submitted to a clips submission thing
- Recreate the clip from a copy of the vod.
- Using the offset to easily spot "hype" points of a stream for channel editors making highlights to focus on that point aka "heatmaps of popular stream time points"
- From CSharpFritz: Show clips in the order that they naturally occurred, and not the time that they were created
295 votesWe have completed the necessary work mentioned in our previous update to provide the VOD offset for Clips. The Get Clips API endpoint now includes "vod_offset" and further information about the field can be found in the API reference: https://dev.twitch.tv/docs/api/reference#get-clips
- Don't see your idea?