GNU Thales - Tasks: task #3325, keep track of bans and Xlines
You are not allowed to post comments on this tracker with your current authentication level.
task #3325: keep track of bans and Xlines
Submitter: | Lucas Nussbaum <lnu> | ||
Submitted: | Thu 17 Jun 2004 02:07:57 PM UTC | ||
Category: | Thales | Should Start On: | Thu 17 Jun 2004 12:00:00 AM UTC |
Should be Finished on: | Fri 17 Sep 2004 12:00:00 AM UTC | Priority: | 1 - Later |
Status: | None | Privacy: | Public |
Assigned to: | None | Percent Complete: | 0% |
Open/Closed: | Open | Effort: | 0.00 |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
CC list is empty
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
Powered by Savane 3.13-d3ae.
Corresponding source code
also, I have a
new idea. Can thales store all server bans as well as channel bans? I
think this would be great! You can store a bunch of hostnames in 1
column, and the type of ban in a different set of columns. For example,
if *@lamers.de were banned from the server (gzline in this case), then
the gzline column would read 'Y'. Also, you can use this if people are
banned from the server, and want to know a more detailed explination on
why. For example, if a user goes to the site, the site can check the
REMOTE_ADDR and compare it to the ban, if they match, they can be taken
to a page on why they were banned. Thanks for the great program!