Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: account bans #1676

Open
vanosg opened this issue Aug 18, 2024 · 2 comments
Open

Feature Request: account bans #1676

vanosg opened this issue Aug 18, 2024 · 2 comments

Comments

@vanosg
Copy link
Member

vanosg commented Aug 18, 2024

While Eggdrop doesn't have extbans in its future, perhaps we could modify a similar internal Eggdrop functionality to ban users based on their account.

Use case 1: .+accountban badaccount monitors joins/registrations and, if a user is seen logged into that account, Eggdrop issues a traditional !@hostmask.com ban for the hostmask attached to that account. From there it is managed like any other temporary channel hostmask ban. Depending on the implementation, this would require a new section of the userfile to store account bans (or, where/how else?)

Use case 2: .+ban $baduser (or pick another prefix) modifies the existing ban system to store the accountname in the ban section of the userfile. These accounts are skipped by the hostmask banning system, but then used to check joining/registering accountnames against.

Or something else. Add thoughts and comments below

@carlin0
Copy link

carlin0 commented Aug 19, 2024

It should also be provided whether the ban is global or referred to only one channel

@DasBrain
Copy link
Contributor

In theory it should already be possible to create a user, add the account to that user and give them the +k (autokick) flag.

I need to test this at some point with a willing participant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants