Display-name not reliable

[livewhiletrue]

I’ve noticed on several occasions that the display-name value is omitted.

2015-05-21 18:33:00.9959755 +0200 CEST:
@color=#D2691E;display-name=;emotes=;subscriber=0;turbo=0;user-type=;user_type= :arek4026!arek4026@arek4026.tmi.twitch.tv PRIVMSG #monstercat :hello
    
2015-05-21 18:37:50.7925509 +0200 CEST:
@color=#FF0000;display-name=;emotes=;subscriber=0;turbo=0;user-type=;user_type= :deadspace2fan!deadspace2fan@deadspace2fan.tmi.twitch.tv PRIVMSG #monstercat :mcat
    
2015-05-21 18:37:55.1608008 +0200 CEST:
@color=#FF0000;display-name=;emotes=35063:0-3;subscriber=0;turbo=0;user-type=;user_type= :deadspace2fan!deadspace2fan@deadspace2fan.tmi.twitch.tv PRIVMSG #monstercat :mcaT

Notice how it affects specific users, not random messages. To retrieve it one would have to deconstruct the hostmask again. Is this a bug or is the display-name expected to be cached, just like color?

[tduva]

It’s probably users that don’t have the display name customized that don’t show up. I don’t think the display name tag is supposed to be used as primary source for the name, just for display purposes, if it is there. If it’s not there, just use the all lowercase name and capitalize the first letter, which I think is the default behaviour (or keep it all lowercase, whatever you prefer for your application).

[livewhiletrue]

Oh, I just thought Twitch saved us the “trouble” of extracting the nickname Thank you