162 results found
-
Add additional examples. Add examples of popular 3rd party libraries.
The current example is very specific and only targets one language. Many community driven libraries are continuously developing and mainting IRC capablities in languages such as; Python, JS/TS, C# and more.
It would be nice in general to see more support for these libraries and even giving some sort of verfication to popular libraries that are maintained and meet quality standards.
2 votes -
graph syntax not built on deploy The graphs on this page don't look right. The graph syntax is displaying, not the graph itself.
%% Extensions Overview Diagram graph LR Twitch --> | - postMessage - | Extension Extension --> | - postMessage - | Twitch Extension --> | - HTTP - | APIs Extension --> | - HTTP - | EBS[Extension Backend] Identity --> Twitch Chat --> Twitch Memes --> Twitch4 votes -
Organize this better, fill in the blanks Who wrote this? The author frequently jumps from point A to point Q.
1 vote -
Put a link to the tutorial here Where's the link to the tutorial?
2 votes -
Fix AutoMod status doc - example curl request The example curl request here:
https://dev.twitch.tv/docs/api/reference#check-automod-status
Doesn't work.1) It needs a broadcasterid query param
2) It needs the content-type header (application/json)
3) I get a 500 error using the provided "userid"s in the post body, using other user_ids worksI spent more time than I care to admit figuring this out, so it seems like fixing this will probably hep somebody out in the future.
If these three things are fixed the call succeeds.
2 votes -
Move GitHub repository to official Twitch organization Please host the example code in an official Twitch organization on GitHub such as:
https://github.com/TwitchDev
https://github.com/twitchtv8 votes -
See scopes Would be nice to see an example with more than one scope. If I separate them with a space, I only gain access to the first one in the list.
1 vote -
Wrong User I think at the very bottom of this page you meant to write User C because that's what that paragraph is talking about.
2 votes -
If I need Extensions Onboarding, link to it. You have error messages that tell me I can't do [insert a variety of things here] until I have completed something like "Extensions Monetization Onboarding." The error message fails heuristics because it doesn't let me fix the problem. It says I need to do something but doesn't give me a link or way to do it. That seems like a huge mistake, but with the forums FULL of people complaining that they can't find it either, I'm wondering if it's a dark pattern and done on purpose.
If there is a workflow that requires me to move through certain steps,…
2 votes -
Sample code in the Status section is mac only. Sample code for windows users would be awesome!
2 votes -
Data Retention for Banned Events and Moderator Events Both
https://dev.twitch.tv/docs/api/reference#get-banned-events
https://dev.twitch.tv/docs/api/reference#get-moderator-events
Only hold only "data" for a finite time period.
The documentation does not note the time period that data is retained and returned for.
Hypetrains does not it's 5 days.
6 votes -
PubSub Documentation Formatting In the subscription fields definition, both cumulativemonths and streakmonths are listed as strings when they are very clearly integers.
Further, it would help greatly with readability if the fields were listed in the order they appear in the supplied JSON snippets.
1 vote -
Add a copy link icon to each section header Since the docs are so long, and each header has an ID you can link to, you should put a link icon that copies the link to clipboard for each header for easy sharing.
3 votes -
Incorrect documentation for Predictions The Predictions documentation has incorrect information listed for how the Top Predictors are defined. The documentation says the list contains a two-level class called "user" and all properties are below that (EX: "user.id"). However in reality, there is just one class that contains all the information and the "user" part is appended in front of a few relevant properties (EX: "user_id"). Screenshot below for comparision:
1 vote -
Expand on V5 to Helix mappings the V5 scope 'user_read' is not listed here. In the migration document it suggests that that is equivalent to the helix scope user:read:email. Is that correct?
Is there a V5 scope that matches the new helix user:read:broadcast
3 votes -
Add documentation about how the Chat Filters feature is implemented. Could you please add documentation about how the chat filters feature in web chat is implemented? Other chat client could really benefit from filtering those messages or highlighting them for moderators as suspicious behavior.
To pin point the exact feature I provided screenshots from the official web browser chat:
- in action: https://i.imgur.com/CfzMx0z.png
- and the associated settings: https://i.imgur.com/8dYADBk.png10 votes -
The documentation doesn't express how to properly authenticate a chatbot without human intervention This page suggests "OAuth Authorization code flow" but i don't believe this is correct because for a chatbot to be effective you would need the access token to never expire or the process to handle expiry and refresh to be event driven. Having a robot/non-existing user login seems misleading or wrong.
3 votes -
Pubsub Docs: benefit_end_month This evening I received a resub over pubsub for 3 months in advance. Rather than the documented "multimonthduration" field, that was set to 0 and a new "benefitendmonth" field was returned. This can be used to calculate the number of months, but I can't find any mention of it in the developer docs.
1 vote -
User banned extensions unload So it seems that when a user is banned or timed out, extensions unload/are unavailable to those users.
This is not documented.
It should be documented somewhere
5 votes -
Publish Official Typescript Typing's for all Data Models It would be very easy to build and design for if there were official typing for all data endpoints. The data between all the different API's for the same data isn't consistent, and with event sub, since it no longer relies on the underlying Helix endpoint, that data can now be different too. This will also mitigate typos on the docs which causes huge headaches when trying to code for API responses and the data not working, or missing fields. The typing can specify which fields are required and which are optional, so when designing your app, you can easily…
3 votes
- Don't see your idea?