Settings and activity
19 results found
-
7 votes
BOLL7708
supported this idea
·
-
4 votes
An error occurred while saving the comment BOLL7708
supported this idea
·
-
6 votesBOLL7708
supported this idea
·
-
8 votesBOLL7708
supported this idea
·
-
10 votesBOLL7708
supported this idea
·
-
15 votesBOLL7708
supported this idea
·
-
61 votes
An error occurred while saving the comment BOLL7708
commented
My use case is that I've made a streaming suite/bot, and I want to promote people streaming with it. I can make the bot automatically (opt in) attach a tag indicating that the bot is in use, and now I want to list streams using this tag through an API endpoint so I can post notifications to a Discord channel.
BOLL7708
supported this idea
·
-
3 votes
An error occurred while saving the comment BOLL7708
commented
I'll describe what I want to make with this. My streaming suite allows for screenshots to be captured, and it is quite time sensitive and during things like boss fights it gets spammed. There are other things like mod actions to kill what is said on TTS if it's a bad message, also time sensitive.
Due to this, I would love to make an extension that allows for buttons that trigger events the suite could listen to with low latency. Right now I would have to roll my own backend, then poll it frequently to get any new activations the extension has submitted.
If we could submit activations over EventSub instead, it is simply a matter of subscribing to another subscription to get those events, with a low latency, and no need to host a separate server or roll that backend. It is also lower latency in two ways, there is no polling as we have direct Websocket (or webhook) messages, and there is no additional step using channel points like when using rewards. Or typing out a chat command, which also spams the chat if it's frequently used.
BOLL7708
shared this idea
·
-
9 votes
An error occurred while saving the comment BOLL7708
commented
If nothing else, the ability to detect the user access level in the extension, so buttons/features can be turned on/off. I'm not sure if this is already possible, but I can see some use for this yes.
BOLL7708
supported this idea
·
-
186 votesBOLL7708
supported this idea
·
-
2 votesBOLL7708
shared this idea
·
-
1 vote
An error occurred while saving the comment BOLL7708
commented
It makes sense for privacy reasons for sure, it would absolutely wreck solutions that keep track of data depending on existing IDs though, as noted. 🤔 Even allowing a grace period in which we can convert one ID into the other might negate the immediate benefits of doing this. 🤨 I would probably be very unhappy if this change was done with no recourse to re-associate data.
-
3 votesBOLL7708
shared this idea
·
-
15 votesBOLL7708
supported this idea
·
-
16 votesBOLL7708
supported this idea
·
-
1 voteBOLL7708
shared this idea
·
-
12 votesBOLL7708
shared this idea
·
-
75 votes
An error occurred while saving the comment BOLL7708
commented
It would be nice to just be able to do an on screen notification when a community challenge has been finished or even contributed to! 😮
I'm always a bit peeved that I can't see which people contributed to a challenge after the fact, so if I could listen in to this and keep my own records that would be great.
BOLL7708
supported this idea
·
-
411 votes
An error occurred while saving the comment BOLL7708
commented
The thing is, this existed in the past, it's how I found many of the people I follow today. Then it was inexplicably removed. Twitch says categories are imported from the Giant Bomb wiki, but I guess Just Chatting etc are custom categories directly on Twitch? Regardless what it was before, we need it as a custom category directly on Twitch now. I can see how it is a chicken and egg problem, VR streamers aren't very big, why give them a category, but then if nobody can find them, how are they supposed to grow? I wonder if there are more gaming genres with this problem.
BOLL7708
supported this idea
·
Uhoh, I have plans to make an extension that will only be usable with a bot I'm making, which might be fine, but I didn't know it was troublesome to get an extension out there.
Guess I should look into the validation process, but if nothing else, if a _channel_ could whitelist the extension instead of viewers, that would probably be enough for me.