You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: