# Some minor chat bugs

**URL:** <https://discuss.dev.twitch.com/t/some-minor-chat-bugs/1109>\
**Category:** Chat and IRC\
**Created:** [October 1, 2014, 8:02pm UTC](https://discuss.dev.twitch.com/t/some-minor-chat-bugs/1109 "2014-10-01T20:02:26Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bufutda](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/bufutda/32/109_2.png) [@Bufutda](https://discuss.dev.twitch.com/u/Bufutda)\
**Post date:** [October 1, 2014, 8:02pm UTC](https://discuss.dev.twitch.com/t/some-minor-chat-bugs/1109/1 "2014-10-01T20:02:26Z")

</div>

- This is a fairly minor chat bug that’s been around for a long time.  
When `<` or `>` is entered in chat, they seem to be converted to  
their corresponding HTML entities `&lt;` and `&gt;`, before being  
searched for emote triggers. This causes the semicolon at the end of  
the entity to be parsed with the rest of the chat as a possible  
emote.

- A more pressing bug is the lack of a `TWITCHCLIENT` setting that  
includes `parts/joins`, userdata from `jtv`, and data from  
`twitchnotify`. I assume this would be under `TWITCHCLIENT 4`. This  
was said to have been ticked as a ‘low priority bug’ in april, 2014  
in [this thread.](https://discuss.dev.twitch.tv/t/twitchnotify-only-getting-sent-to-tc3/691/8)

---

<div class="post-metadata">

**Author:** ![brildum](https://avatars.discourse-cdn.com/v4/letter/b/f19dbf/32.png) [@brildum](https://discuss.dev.twitch.com/u/brildum)\
**Post date:** [October 1, 2014, 8:19pm UTC](https://discuss.dev.twitch.com/t/some-minor-chat-bugs/1109/2 "2014-10-01T20:19:54Z")

</div>

Thanks for the bug report. I’ve filed it with our QA team, but it probably won’t be fixed too soon.

This will get resolved automatically in the next month or so. We’re actively updating the way emoticons are handled by our clients so that they continue to work as the number of emoticons increases. Long story short, there are too many Twitch emoticons now for clients to deal with them on their own. The chat server will start parsing emoticons and notify clients regarding what text should be replaced in a message.

---

<div class="post-metadata">

**Author:** ![brildum](https://avatars.discourse-cdn.com/v4/letter/b/f19dbf/32.png) [@brildum](https://discuss.dev.twitch.com/u/brildum)\
**Post date:** [October 1, 2014, 8:39pm UTC](https://discuss.dev.twitch.com/t/some-minor-chat-bugs/1109/3 "2014-10-01T20:39:28Z")

</div>

> [@Bufutda](#):
>
> A more pressing bug is the lack of a TWITCHCLIENT setting that  
> includes parts/joins, userdata from jtv, and data from  
> twitchnotify. I assume this would be under TWITCHCLIENT 4. This  
> was said to have been ticked as a ‘low priority bug’ in april, 2014  
> in this thread.

I’ve added this to our queue with a note to start a thread announcing this change when it hits production. It will be done soonish™.

---

<div class="post-metadata">

**Author:** ![brildum](https://avatars.discourse-cdn.com/v4/letter/b/f19dbf/32.png) [@brildum](https://discuss.dev.twitch.com/u/brildum)\
**Post date:** [October 1, 2014, 9:27pm UTC](https://discuss.dev.twitch.com/t/some-minor-chat-bugs/1109/4 "2014-10-01T21:27:09Z")

</div>

I should add that this is to fix the bug that subscriber notifications don’t show up for previous TWITCHCLIENT versions (\< 3 and IRC clients). That will be fixed. I cannot say whether we will support JOIN/PARTS for newer TWITCHCLIENT versions, although I can see how that can be useful.

We’re currently in the process of re-thinking how we support and deprecate different client versions without causing headaches on the server or clients.

---

<div class="post-metadata">

**Author:** ![Bufutda](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/bufutda/32/109_2.png) [@Bufutda](https://discuss.dev.twitch.com/u/Bufutda)\
**Post date:** [October 1, 2014, 9:58pm UTC](https://discuss.dev.twitch.com/t/some-minor-chat-bugs/1109/5 "2014-10-01T21:58:26Z")

</div>

- Sometimes when you get logged out of twitch, you appear to be talking as a user named `me` or a user named `justinfan` with 6 seemingly random digits after it instead of being prompted to log in. These messages do not actually go through to the server, despite appearing to on the client side. If you are a moderator in the channel when this happens, the mod icons still appear.

![](https://discuss.dev.twitch.com/uploads/default/4/78423314e4953f06.png) ![](https://discuss.dev.twitch.com/uploads/default/5/e61f498e5687ebf8.png)

- As a mod, mod icons appear beside the broadcaster and fellow mods (including yourself) among everyone else in chat despite not being able to moderate fellow mods/broadcasters.  
As a broadcaster, the mod icons appear beside yourself despite not being able to time out yourself. This clutters and wastes chat space.

---

<div class="post-metadata">

**Author:** ![tduva\_](https://avatars.discourse-cdn.com/v4/letter/t/3bc359/32.png) [@tduva\_](https://discuss.dev.twitch.com/u/tduva_)\
**Post date:** [October 10, 2014, 2:25pm UTC](https://discuss.dev.twitch.com/t/some-minor-chat-bugs/1109/6 "2014-10-10T14:25:50Z")

</div>

I definately second the need for a TWITCHCLIENT with all information and joins/parts.

Also is there any chance for names in chat to be send correctly capitalized? The only way to achieve that now is to request the capitalization from the API, which means a request for every name. Of course I do this only very carefully (especially since it’s a clientside app), but it still seems like a bit of a waste to do that many requests.

Thanks for you work on chat and listening to feedback in any case. 🙂

---

<div class="post-metadata">

**Author:** ![tduva\_](https://avatars.discourse-cdn.com/v4/letter/t/3bc359/32.png) [@tduva\_](https://discuss.dev.twitch.com/u/tduva_)\
**Post date:** [October 26, 2014, 5:04am UTC](https://discuss.dev.twitch.com/t/some-minor-chat-bugs/1109/7 "2014-10-26T05:04:02Z")

</div>

> [@brildum](#):
>
> I should add that this is to fix the bug that subscriber notifications don’t show up for previous TWITCHCLIENT versions (\< 3 and IRC clients). That will be fixed.

I’ve been noticing those messages on TC1, so that seems to be fixed now. Great. 🙂

On a related note, I noticed that the “x is now hosting you for y viewers.” message also only appears on TC3. Would be really helpful to have that as well.

---

<div class="post-metadata">

**Author:** ![plalx](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/plalx/32/388_2.png) [@plalx](https://discuss.dev.twitch.com/u/plalx)\
**Post date:** [March 21, 2015, 8:51pm UTC](https://discuss.dev.twitch.com/t/some-minor-chat-bugs/1109/8 "2015-03-21T20:51:49Z")

</div>

Any news on this? Will the JOIN/PART messages be sent to TWITCHCLIENTs?