Also, the quoted endpoint does generate a fair few HTTP 502 and 503 responses. I usually retry when that happens.
My problem is that I also need the list, even when the broadcaster is not online, and not logged in.
How about instead of suggesting all kinds of nonsense workarounds, someone actually looks into this and fixes it. Right now mod status is constantly being added/removedā¦ about every minute.
When connecting via an IRC client, this happensā¦
[22:31] * jtv gives channel operator status to deezjavu
[22:31] * jtv gives channel operator status to peccyz
[22:32] * jtv removes channel operator status from deezjavu
[22:32] * jtv removes channel operator status from peccyz
[22:41] * jtv gives channel operator status to deezjavu
[22:42] * jtv gives channel operator status to peccyz
[22:42] * jtv removes channel operator status from deezjavu
The IRC client uses the following command when connecting:
raw CAP REQ :twitch.tv/membership
As also mentioned, users actually in chat (can see them sending messages) are missing from the user listā¦ then show up again, etcā¦
This started happening a few days ago.
1 Like
The spurious JOIN/PART messages seem to be getting worse by the day. Iām even getting PART messages for the streamer every 5-10 minutes while theyāre actually streaming. Many of our viewers use chatty and can even see how the user list has gotten very unstable. Itās getting to the point where JOIN/PART is almost completely useless.
As Fugi says, never rely on JOIN/PART. Let alone at channels of above 1000 chatters, JOIN/PART are not emitted anyway. So do not rely on them, ever.
JOIN/PART has always been this wayā¦
Sure there are valid reasons for knowing who is or is not in a channel, but I have never relied on JOIN/PART myself as itās never been āreliableā
On the subject of Chatty, even that userlist will not work for channels post 1000 users, and Twitch doesnāt have to help or support third party programs.
@MikeyDK the end point that @trumpi27 mentions works all the time regardless of the channel online/offline status. I follow what @trumpi27 does and ignore bad responses and smooth accordinglyā¦
On the subject of Mod status, as @MattiSony says issue /mods and parse the NOTICE response, you will need the COMMANDS CAP for this.
If you are suppling the main bot for the channel on a 1 on 1 level, it should be fairly safe to assume the bot is modded, since surely you will have put in a shutdown command or additional ways for the channel owner to control/stop/restart the bot so the issue of āis the bot moddedā is not a issue (personally speaking)
I am not sure how I would determine if the response is good or bad.
This is the response I would like to see
{
"_links": {},
"chatter_count": 2,
"chatters": {
"moderators": [
"mikeydk",
"nightbot"
],
"staff": [],
"admins": [],
"global_mods": [],
"viewers": []
}
}
Where nightbot is in (I dont care about if it is shown as mod or not, that is not needed for my application)
But when I am not in the channel, I get a response like this
{
"_links": {},
"chatter_count": 1,
"chatters": {
"moderators": [
"nightbot"
],
"staff": [],
"admins": [],
"global_mods": [],
"viewers": []
}
}
which is still fine and valid, and if nightbot leave, I get a response like this
{
"_links": {},
"chatter_count": 0,
"chatters": {
"moderators": [],
"staff": [],
"admins": [],
"global_mods": [],
"viewers": []
}
}
but with that last response, nightbot can still be in the channel, but not shown.
Not sure how I should validate the reponses when they are like this.
My point is it used to be somewhat reliable and now itās just bad. Just getting it back to where it was would be a huge improvement. Also, how else do you determine whoās in the channel? Only other way I know is with a tmi call thatās not even officially supported from what I understand.
Just noticed you referred to that link. Either way, itās not a good idea to have a feature thatās basically broken.
HeyGuys,
We have made some improvements last night to the backend service that triggers these messages. Iāve verified myself that these are no longer flapping JOIN/PARTs or MODE messages. If you still are getting unexpected behavior, weād like to know about it. Thanks!
4 Likes
Looks like it worked! Havenāt had anyone randomly drop out so far. 
Iām still having this issue, and Iāve been having it all day. My bot keeps greeting people who are already in the chat and looking at my logs confirms my bot has been receiving JOIN messages from people who are already in chat.
It looks like it only happened for a couple hours on my bot then it has stopped ā¦
[05:23] * Parts:
[05:24] * Joins:
[06:00] * Joins:
[06:02] * Parts:
[08:50] * Parts:
[08:51] * Joins:
After that i have not see it do it again ā¦ but will keep eye on itā¦
Mate thanks so much!
Same oroblem here ā¦ i wonder why that appearedā¦ it was working perfectly a few weeks agoā¦ (and i am a small streamer)
Seems to be much more stable for me now. Thanks a bunch!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.