1. Are there any news about “name change notifications” in IRC for bots? We still don’t know when we should leave a room in IRC and join another one because a user changed his name. @xangold

  2. Loyalty bots really need the chatters endpoint to return the viewer ID, if the viewer changed his name, there would be no way for us to relate the old name and the new one. (For example, a user would lose all his “points” if he changed his name)

Perhaps what would be better would be to just change all of the IRC channel names to be the channel ID instead of the channel login name?

That’s a huge breaking change. It would be ideal for developers, but it would also break compatibility with normal IRC clients (and protocol) even more. Nicks cannot start with a number and some clients can’t handle ones that do.

I don’t think @JacobiCarter is talking about nicks, he’s talking about Channel Names. If channel names were ids instead of the streamer’s username, the bigger problem would be fixed. Only one room ever, no need to change rooms when a user changes their username. You were saying that nicks can’t start with a number, can channel names start with numbers? If they can, then the solution we were talking about is possible.

Oh yeah. That would be useful.

1 Like

Please no breaking changes…

All you need to do is send an event to the chat when a name-change occurs.

You can already detect if it’s the correct channel when joining it (via ROOMSTATE)

1 Like

What information in ROOMSTATE do you use for that? Or the mere fact there there is a ROOMSTATE?

Not sure how much extra load it would be for the system, but technically it’s possible to support both JOIN #username and JOIN &userid. That would keep backwards compatibility and avoid a quick fix that just ends up being another gotcha to deal with…

Seems like the id was added, but it’s not there anymore.
@broadcaster-lang=;emote-only=0;followers-only=-1;r9k=0;slow=0;subs-only=0 :tmi.twitch.tv ROOMSTATE #moocat

@xangold Bug?

1 Like

he added rood-id but only on change event

What do you mean change event? ROOMSTATE only happens when you initially join the channel, no?

@msg-id=subs_on :tmi.twitch.tv NOTICE #ee_man :This room is now in subscribers-only mode.
@room-id=27245045;subs-only=1 :tmi.twitch.tv ROOMSTATE #ee_man

Having this on join as well would be very useful.

I’d use the word ‘mandatory’

@xangold Any input on ROOMSTATE on-join not containing room-id?

Now that username changes have been a thing for a bit now I’m planning to update my database for any users that have changed username, the issue is there doesn’t seem to be an endpoint to check multiple users by ID at the same time right?

Just to make sure I’m doing it right, the only way current would be to use https://api.twitch.tv/kraken/users?login=username1,username2 for 100 users at a time, any users not included in the response I would then make a single api request using their ID and would have their new username in their response. From my understanding that should work (as long as I perform this update more frequently than a username could be changed and the old one released back to be reused by someone else) or is there a better way?

Any updates on room-id on ROOMSTATE messages on channel join?

1 Like

ResidentSleeper. This thread will be closed with no update, just like the last one.

I sent a tweet to “twitchdev” about this with no response either :confused:

room-id should be sending on ROOMSTATE now (in a few minutes, barring no errors) :deilluminati:

3 Likes

@xangold are you guys going to work on this or something similar at all? I know the chatters endpoint is not supported, but since you guys made this change to IDs instead of usernames it would make sense to at least update the endpoint. This is the only thing that makes possible the existence of most (if not all) loyalty bots.