EventSub Chat Message Cheermote Fragment prefix is lowercase, but Twitch API returns Capitalized

API
1

I started using EventSub channel.chat.message subscription to listen to chat messages, and I noticed the fragment’s cheermote.prefix is lowercase. On the other hand, the prefixes returned from the /helix/bits/cheermotes endpoint are Capitalized.

While I can simply preprocess and convert both to the same case first before comparing, was wondering whether I was right in assuming they refer to the same thing, or whether it is how the prefix is intended to be used? Is there an obvious reason for mismatching cases in these two APIs which I missed?

Thanks!

2

Just one of those twitch things.

Most likely it’s a case of legacy/older data (probably) on the cheersmotes api.

Fairly sure when someone cheers they can mix and match whatever case they want in the chEeR and IRC/chat will use the lower case form regardless (without checking)

So it’s just the older cheermotes API spitting them back in shouting mode.

Not sure if bug or overlooked thang here. I just have always lower cased them and passed 'em to my detection regex with /i anyway

1 Like