TWITCHCLIENT bugs

Chat and IRC
1

Alot of people have experienced, ill just drop it in here hoping for chat devs to see it asap - TC seems to be bugging out.
A connection with TWITCHCLIENT x enabled, regardless of the value of x, receive all HISTORYEND and HOSTTARGET messages any user joining each channel receives, instead of it just sending the info for the user that joined.
Screenshot from my IRC client: http://i.imgur.com/dwOIILj.png
This was reproduced by constantly leaving/rejoining the chat on a 2nd client (browser chat works aswell)

This gets pretty ridiculous for some channels, if alot of people joining, this can easily exceed 2k messages per minute. No rate limiting is applied to these messages, not even the “data received per connection”. This can pose a gigantic problem for certain applications, I guess. My bot, which is sitting in just approx 50 channels, was receiving over 25000 messages per minute when I first found this to be happening. I can only imagine this posing a stability issue to chat servers. I have not experienced any differences between server IPs, event/normal chat or the like, this seems to be a global issue.

Hope that info helps.

2

Thank you. We’ll be looking at this today.

1 Like
3

A fix was pushed out. Let me know if this is working as you expect. And thanks again for the report.

4

The messages stopped, so thats a good sign. I will obviously put anything I come across here.

5

Seems to be back with commands CAP, where it’s sending the raw HOSTTARGET every time the channel is joined by anyone:

648Ă—557 19.1 KB

Tested with telnet and browser using a few different combinations of TC4 and CAPs, all resulting in the additional HOSTTARGET on the connection above (using both TC4 and CAP REQ :twitch.tv/commands, but only doing so after commands CAP)

6

Just noting that I have had trouble reproducing, but succeeded by using 2 connections with the full TC4/caps package - browser chat did not work however, which is really weird.

Currently 2/3 requests to twitch urls are 502 or 503ing, so no testing is possible…

7

Thanks for the report. A fix should be live now.

8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.