Migrating to user-id's instead of usernames

[kinsi55]

As announced months before, Twitch now identifies users by a unique ID instead of their name.

Today, Twitch decided to make a breaking change before v3 API is EOL by allowing full username changes. https://blog.twitch.tv/the-hype-is-real-name-changes-are-here-c629c4697154?sf58352669=1#.7fb8dssk7

So to truly identify users you must now use the unique ID instead of the name, but tmi.js offers no possibility for that.

Apparently, user-id is missing for a lot of IRC messages, but maybe it should be pre-maturely implemented for every event(?)

https://discuss.dev.twitch.tv/t/username-changes-identifying-users/9373/20

[AlcaDesign]

tmi.js if giving you as much data as it receives. You have to supplement the rest.

[kinsi55]

Well, e.g. as you can see the subanniversary event has a user-id emitted by IRC

tmi.js/test/events.js

Line 189 in e680e2b

data: '@badges=staff/1,broadcaster/1,turbo/1;color=#008000;display-name=Schmoopiie;emotes=;mod=0;msg-id=resub;msg-param-months=6;room-id=20624989;subscriber=0;system-msg=Schmoopiie\shas\ssubscribed\sfor\s6\smonths!;login=schmoopiie;turbo=1;user-id=20624989;user-type=staff :tmi.twitch.tv USERNOTICE #schmoopiie :Great stream -- keep it up!',

There is no way to get that tough from the resub event
https://docs.tmijs.org/v1.1.2/Events.html#subscription

[AlcaDesign]

My ideal of this situation is that we change it so that every event emits an object instead. Then you just destruct for what you need:

client.on('subanniversary', ({ channel, message, userstate, months }) => {

});

Then it doesn't matter what our order of arguments are.

[kinsi55]

Sounds perfect to me. Futureproof and simple to adjust to