I'll implement a general 'delete this ip' option, that way a user can eliminate exactely the entries he wants to remove.
This affects the statistics generated from the raw hists table, long term data will not be touched because e.g. there is no way (trying to find a mysql query based on hits data which returns visits depending on a time delta) to evaluate how many visits (hits can be fetched from database) a certain ip caused at 2007/11/5.
This data could be corrected:
- hits overview list
- general hits counter
- time based hits counter (month, week, day, year)
- post hit counter
- all clients, robots, search, pages, feed data
On the other hand - depending on how long you store data in the raw hits table - after activating the blocker cookie you would just have to wait this amount of hours/days/weeks until you get 'clean' data.