JOIN/PART changes, temporary and future

Thanks a lot, I feel really stupid for not thinking about this one by myself, I was stuck on another idea :sweat:

As much as you’re already going to say no, can you please bring back Join/Part without membership? This makes things way too complicated for normal IRC users, and makes it even more of a hassle for bot developers, especially those people who are just learning themselves. I don’t really even see why this is necessary after E3 is over.

1 Like

Agreed. I need more time to cope with the deprecation of JOIN/PART please.
You also promised several weeks of advanced notice before you done this.

We DID give you several weeks of advanced notice…

When it is again activated the JOIN / PART? Ate even via CAP MEMBERSHIP? Because until then, even this off, right?

Everything you need is in the new IRCv3 stuff.

There are plenty of ways to deal with join/part without join/part as join/part has never been reliable on Twitch anyway.

There shouldn’t be any reason to be using join/part. Unless you are running a greeter script and no body likes those…

I personally don’t have a problem with join/part being removed as I wasn’t using it myself. I polled the channel list from the other API as per here: Users list in IRC clients missing for me?

No Join/Part till after E3. And then you need to request the relevant CAP as @SeeingBlue linked above

The problem is, my bot only works if it’s mod in a channel, and is op doesn’t really work. >.>

So does that mean that if I don’t do anything, the userlist for my channel on MIRC won’t ever work properly again? And if that’s the case, what is the MEMBERSHIP capability and how would I even begin to go about requesting it?

At that hinted when the servers come back to send the JOIN / PART of information we have to use a CAP MEMBERSHIP: and thus receive the same information before. My doubt is precisely whether this information together with the mIRC for example, will work perfectly as before, only to call the join / part on the remote within the mIRC.

I switched to CAPs in my mIRC like a week ago and I can confirm that it works just like it used to when using


then the command that we used before in mIRC’s remote only calling: on *: JOIN: #: for example, for the bot to perform a function when it detects that someone enters the chat, work the same way, the only thing differentIt is that we have to perform before the CAP MEMBERSHIP?

that’s correct.
In addition, if you also request and and can do fancy stuff like adding a subscriber or turbo tag to usernames.

Ok, thank you for taking this doubt. I will be awaiting for the normalization of IRC servers about it to request via CAP Membership.

I recommend using the chatters api endpoint:{ChannelName}/chatters

I’m still going to complain :stuck_out_tongue:
Is there not a more centralized or organized method for communicating with developers. Sifting through these threads and post for important information seems crude. Can we sign up for a dev newsletter or something?

1 Like

How can I go to read this data from within the mIRC? I am beginner with IRC Script …

I am also new at IRC and was wondering if there is a temporary fix we can do for now to get a viewer list back.

From my experience with justin/twitch api all i can say its a really joke. Over two years they broken more than 5 times my app. Funny is that they made changes like just chnaging name from “title” to “status”
and if i compare what i could two years ago and now… now i can get less info than back then :stuck_out_tongue: (unless you care about this awesome emoicons)) Dont understand for who is this api

1 Like

I switched to reading this URL for situation like this.
change ‘twitch’ to your channel name.