32 results found
-
Bans topic sends for timeouts and bans but doesn't differentiate The bans topic will send an event for someone getting banned or timed'out from the channel.
The bans topic doesn't tell you if it was a ban or a timeout.
- Timeout's either need to be a seperate topic (not preferred)
- The payload extended to include a time parameter, so timeouts can be differetiance (preferred)
(Webhooks have the same problem ironically)
6 votes -
Provide Who and Reason in channel.ban Summary:
In chat for the broadcaster and mods, when someone is banned the reason and responsible user is provided. Adding the user's identifiers and the message that was used when banning. Assuming there is a timeout equivalent planned or made this likely would need to be added there for consistency as well.Reasoning:
This allows for up to date reasonings for why someone was banned without having to request this info separately.Related Topics:
- channel.ban
- channel.unban6 votes -
golden kappa hype train mention It would be great to mention in the eventsub notification that its a golden kappa hype train so we can customize an alert to go off on stream
4 votesGolden Kappa and Treasure Hype Trains are available via the new Hype Train events:
https://dev.twitch.tv/docs/eventsub/eventsub-reference/#hype-train-begin-event
-
VIP add/remove event Adding new subscription types for the VIP add and remove event (Like existing add and remove moderator events)
It would be great to be able to create an interaction in stream when the streamer (Or a moderator or any other automated system thanks to the API) adds a VIP.
4 votes -
Add mod/unmod events and adding/removing editors Mostly for broadcaster tools which have some kind of permission system that allows mods (and now editors) specific access to features. This would remove the need for checking if the user is still a mod/editor.
4 votes -
Ability to increase subscriptions limits We run a Discord bot on ~9M Discord servers. It announces streams in Discord servers.
We are subscribed to 1M+ twitch channels using webhooks and managed to get there by taking advantage of the rate-limit bump form you guys provided back then. But it seems like you guys stopped doing that.
Since we hit the limit of subs, we had to change the way we do it and loop over live streams using the API - which is suboptimal since we miss some streams and the announcements are delayed.4 votesWe recently updated our subscription limit logic in EventSub so that limits scale as your application grows. See https://dev.twitch.tv/docs/eventsub#subscription-limits for more information.
-
Add support for Treasure Hype Train With a new Hype Train type added (Treasure Hype Train). It would be nice to have it in the event sub. (Maybe replace 'isgoldenkappatrain: true/false' with 'traintype: "basic"/"golden_kappa"/"treasure"'?)
Except if the Treasure Hype Train is meant to be temporary of course.
2 votesThis has been added into the Hype Train Begin event
-
EventSub receive whispers EventSub recently got a few new chat-related subscription topics, most notably receiving chat messages, as described here: https://discuss.dev.twitch.com/t/available-today-twitch-chat-on-eventsub-an-api-for-sending-chat-and-the-conduit-transport-method-for-eventsub.
Our chat bot, and I imagine other peoples' bots might as well, is reacting to incoming whispers. To be able to migrate off of IRC it would be necessary to also add a new subscription topic for receiving whispers.2 votesThis has since been added: https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types/#userwhispermessage
-
"notificaiton’s" small typo on second paragraph There is a small mistake in the second paragraph "The Twitch-Eventsub-Message-Type request header contains the notificaiton’s type."
Note that notification is spelled wrongly
2 votes -
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 -
Improve Doc "Create a subscription" for EventSub In https://dev.twitch.tv/docs/eventsub step "5. Return the value of challenge from the callback verification request to complete the verification process. Your response must be a raw string. If your server is using a web framework, be careful that your web framework isn’t modifying the response in an incompatible way. For example, some web frameworks default to converting responses into JSON objects.
pogchamp-kappa-360noscope-vohiyo"It is not understandable where need to send challenge variable, on what api endpoint? Please maybe add a curl example
1 voteWe’ve updated the documentation, so this issue may be resolved.
-
add started_at to stream.online Its basically just for caching the date for things like uptime saves resources on our end (not having to make the call to Helix/streams) and the 36 extra bytes don't feel like the end of the world.
1 vote
- Don't see your idea?