Permissions based on IRC ops

Bug #727027 reported by marcog
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ibid
New
Wishlist
Unassigned

Bug Description

Ibid should check the ops status of users and allow assigning a permission to all users with a certain op level or higher. This would prevent the need for maintaining two permission lists: chanserv and the bot.

marcog (marco-gallotta)
description: updated
Revision history for this message
John Peasley (firehawke) wrote :

The situation that requires this sort of option is a bit odd, it's almost a 180 from standard IRC conditions.

Justin.TV uses IRC as its chat backend, however, anonymous connections are not accepted. Any user that connects will have a username like <email address hidden> -- this example user of joesmith is authenticated already by the Justin.TV chat system using Justin.TV login credentials, and you can't use /nick to change to another name. Additionally, upon joining a channel, users are automatically given voice or ops depending on their administrative status on the channel, and you cannot just give "temporary" ops-- you have to give an according administrative spot.

This means that unlike a regular IRC channel, the user is 100% vetted by the server. Having a second userlist on the bot with individual permissions is redundant in this particular case and would be wasted effort in keeping it in sync with the JTV-side information.

As far as I'm aware, no existing IRC bot out there can handle this kind of situation gracefully.

Revision history for this message
Max Rabkin (max-rabkin) wrote :

I would say you don't only want this in the Justin.TV situation (although it would be useful to consider everybody on such a network to be authenticated).

One issue with this is that a lot of bots run in multiple channels, and permissions apply to all channels currently.

tags: added: irc permissions
Revision history for this message
Stefano Rivera (stefanor) wrote :

I'd say for now, you should hack the authentication code in ibid/auth.py to do what you want.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.