Mara's Join/Part suggestion

[StarlitGhost]

Mara had some ideas we might want to do later:

I guess the neatest solution would be to have a joined channel store with an "inviter" that also has the right to part the bot from the channel, alongside the admins of course.

Having the channel ops also able to do so would be good. Maybe another access level.

[HubbeKing]

Well we are storing user ranks in the channel objects, so a AccessLevel.CHANOPS would be relatively simple. Just have _allowedToUse check if admin or chanop then True.

[Heufneutje]

I don't really see the point in giving specific part access to chanops. That's what the KICK command is for...

[HubbeKing]

Keeping track of the inviter is gonna be a bit tricky, though. The join module just instructs the core to send a JOIN at the moment, and I can't think of a way to get the message.user from that module to the core's JOIN parsing thingamabob.

[HubbeKing]

Perhaps if we make the join module return an IRCResponse, and if a JOIN message comes to the bot before a timer runs out, add the response.user to the new IRCChannel object as a channel.inviter?

[StarlitGhost]

I was thinking the join module would set the inviter itself, as it has the information it needs right there in the message.
Then part would just check that.

[StarlitGhost]

Still, it would require a little core modification to add an inviter to the channel class.

[ElementalAlchemist]

It could also be a core modification to add arbitrary data to the channel class in case it's useful for other modules (so they don't have to do weird hacks to track it in their own classes when it doesn't make sense to).

[Heufneutje]

Looking at this now and knowing what @matthewcox is working on, I think this should be doable with actions.