Giving broadcasters control; concurrent join limits for IRC and EventSub

But if I create 5 clients with 100 channels connected to each one it should work, right?

The announcement doesn’t specify how multiple connections are handled, but the limitations would be somewhat pointless if they could be circumvented by simply making more connections.

If you need to join a large number of channels, the appropriate way to scale is to have the broadcaster grant your app the required permissions or make your bot a mod, and if you’re unable/unwilling to get those permissions then you may have a use case Twitch doesn’t wish to support which is why the point of this topic is to give broadcasters more control.

2 Likes

Got this in my email? Says im a chatbot? Which im not? Im so confused😂

The basically don’t worry about it as it doesn’t apply to you.

At some point you/someone requested verified chat bot on the account in question. Or were assigned it.

But if you are a normal website user and got this email it’s safe to ignore it, since you are not operating a chat bot.

Hello.
I’m normal user not chat box but i like to sit on many chats in the same time and yesterday i got that msg
dadadad
I get that msg that chat pop up idk how to name it but i get it normally on browser version (Firefox)
I just don’t know what to do to have normal twitch experience i get like couple days ago

With this update, you can be in up to 100 chats concurrently. Channels where you are a mod do not count against this limit. So, in practice you can be in 100 chats + all chats you mod for concurrently. If you are getting an error, you’ll need to leave a chat before you can join another. Simply close the chat you are no longer using, and open another in a new browser.

But i don’t want to choose at what streamer i want to be and what to not :confused:
That change was primarly for chat bots and i’m verify user with verify email and phone number so why i get that limit too :confused:
Now i see that to avoid it i need to use my second account (linked to main account) and with that going around i can extend limit to another 100 chats. But I don’t want to combine and going with two accounts to do the same as before update. I need to ask twitch to be verified bot to just watch?
Can you extend that limit for verify users?

Even verified bots only temporarily have an increased limit, that will soon be phased out over the next month or so at which point even they have the same limit of 100 channels where the broadcaster hasn’t either modded them or given the required scopes to a bot to connect to their channel.

For actual users, being in 100 channels, that you’re not a mod for, all at the same time is far beyond what the vast majority of users do, and it’s unrealistic to be active in that many channels at the same time so the solution for users such as yourself would be to join the channels you are going to be active it, and when you want to be active elsewhere you leave the channels you’re not active in any more and join the new ones.

@SzymenL0K0

I’m normal user not chat box but i like to sit on many chats in the same time and yesterday i got that msg

With this update, you can be in up to 100 chats concurrently.

Actually, the limit is 150, 100 via API + 50 for the website (plus your own channel + channels you are a moderator in). Connecting to a channel via multiple clients or the website only counts as one of those 150. If you make a connection to one of the options where you have not exhausted your limit, and then connect to the channel on the other, you can connect. You can then close the connection on the one you don’t need and stay joined to the chat on the one you want for a total of 150 connections.
Of course, that’s still not nearly enough and easily exhausted as well. Sometimes, the website doesn’t disconnect a chat session. Browser extensions like BTTV, FFZ, 7tv and similar may open additional connections for their functionality, too (which they then also do not close properly).

@jbulava

Non-moderation chatbots that are in more than 100 channels concurrently

Migrate your application to EventSub Webhooks or Conduits. Begin gathering the required channel:bot scope from the channels where your bot operates today.

I need some clarification on this. If a user authorizes an application with the channel:bot scope, does that mean all users using the application to connect to chat are authorized to connect to that user’s channel from then on?
Is including that scope with all other scopes for each client_id in use sufficient to make it work like before?
Are you trying to force me to only use a single client_id instead of a client_id per application from now on? (this will make it easier to have that scope on the most channels)
If I make the user follow an authorization grant flow to get this active authorization, does it matter what token type they request and when that token expires?
If the user changes their password (which will deauthorize all apps and removes them from the authorized apps list in the channel settings so you can’t even see what was previously authorized :woman_facepalming:) will I (and all other users of the application) be kicked from their channel if I am (or they are) currently connected?
Is there a method with which I can gain active user-based authorization that does not involve making my user a channel moderator?
What is the expected turnaround time to gain verified status to be exempt from the limitation while I try myself at the gargantuan task of nagging all the users whose channels I want to be able to connect to in hopes of gaining their active authorization? (by the way, I don’t want to have to bother them with this!)
Is there any chance for you to course correct and remove the limitation at all?
Is there a paid option (planned or unplanned) with which a user can be exempt from the limitation?

Clear and concise answers to these questions would be much appreciated. Thanks. :slightly_smiling_face:

Sidenote:

We also plan to send email communication to potentially affected developers

I would posit, being able to tell who would be affected by this should have been rather easy by looking at channel join metrics, but I digress…

I was signed up to the developer newsletter, and I still got nothing. (That’s the Developer Product Updates and Developer Console options in the Notification Settings, by the way). What’s up with that? This is a pretty devastating change.

I’m halfway though reimplementing the chat side of my bot (which is an absolute nightmare given every aspect of the bot was written with processing IRC messages in mind), so I have some of the answers but not all. Not sure any staff will answer; I haven’t seen any discussion from anyone but community members besides the original post.

An app with channel:bot perm on a channel can join that channel using any account it has the user:bot on. Alternatively, it seems like an app can also join a channel without channel:bot so long as that channel has modded the account with user:bot via a conduit. This makes joining channels at least pretty easy as it’s the same flow for both. For servers, my little test app seemed to work well by just creating a conduit, connecting a websocket (no auth needed), then telling the conduit the session ID, and it was done. (webhooks worked fine too). The docs are very much out of date on the auth flow for app vs user when it comes to conduits.

I’m not sure what you mean by “each client ID”; aren’t client IDs synonymous with apps? Do you have more than one app?

Having one ID sounds normal; I have two (one for prod that everyone auths into, it’s “the app”, one for my local testing). Of course multiple apps means multiple auth for everything.

I assume we get kicked, yes, though I assume that having mod status prevents that (am not to the point where I can even test that)… See also the commentary above about how timing out the bot user also breaks the subscription. Not sure how to handle that as a naive implementation of “make the current subscription state match the expected” would continue to try to add said subscription and it just not work. Really feels like an oversight as it will make bot implementations very challenging.

Not clear to me if this is possible unless connecting as a specific user to IRC and staying under the 100 limit. That or the justinfan trick, which was also previously mentioned. Not going to be thrilled if this goes away as I often use anonymous chat access to look at channels that add my bot then use it to spam (I would rather not let them know I’m seeing what they’re doing).

Note that sending messages has always been possible without actually joining channels. You could send a PRIVMSG on IRC from any connection to any channel so long as it was for the right user, and with the new APIs, can also send an arbitrary message. I switched my bot to using the send chat message API without much fuss.

I would be utterly shocked if this would ever happen, given verified bots are getting kicked off in just a couple of days. The form says 5 business days, so even if you were to be verified, it wouldn’t matter.

If I used a chat application that used conduits would I be able to be in more than 100 chats at once? I currently use chatterino to keep track of who is currently live and see if anyone mentions me.
I haven’t followed many of the channels because I didn’t want to bury some of the older smaller channels I followed. If the 100 channel limit would still be in place is there any way for me to start following more channels and sort by who has been live longest?

Yes as to run conduits (or webhooks) requires authentication from the broadcaster to be present in the chats

Your use case is unlikely to result in broadcasters authenticating you to be present.

if you mean the current stream, sure just use the Get Streams API, diff current time with the start time from the API and then sort your list.

This API supports up to 100 channels at once per request for easy fetching and sorting

Hello, is this already in effect?
Because I still see bots in my channel like 00_ava that is sitting in 62k channels according to Twitch Insights site

Or are they somehow bypassing these limits?

Verified Bots currently have an exception to the limit, as documented in the original post.

The schedule also sets out when that exception for verified bots will also be removed.

Hmm, but Twitch docs says that verified bot status is rarely granted. Why would 00_ava be a verified bot? When you open that channel it says in their bio “Your average egirl :3”

Twitch does not disclose why someone may or may not have been granted Verified Bot status.

In general Twitch usually only grants verified bot status to multi-channel bots that need the limit increases due to their use making them approach the normal limits, and before the requests for the status were paused it was not difficult particularly difficult to obtain. There are exceptions to that though, and there are many users on Twitch whose personal account has verified bot status, but this is certainly not the norm.

1 Like