ips still listed in top visitors
thomas23@drupal.org - June 4, 2008 - 22:26
| Project: | IP anonymize |
| Version: | 6.x-1.0 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Jump to:
Description
Default settings are used (excapt it's enabled), i.e. that is keep ips 3 hours. Is there a table missing to be handled or am I interpreting something wrong?

#1
Is cron running? Cron is the mechanism that actually performs the anonymization.
#2
Thanks for that quick response!
Using poormanscron, and yes, it runs.
After having had a look at the table _accesslog and others, though, I guess it's been my misinterpretation. Are IPs, i.e. hostname row, anonymised by replacing them by "0"? If so most likely the IPs still listed in "top visitors" are the once from within the last 3 hours?
I expected them to be hashed in some why so they still are unique but just not IP addresses anymore. So if I'm right now, could we make this a sort of feature request bug instead :)? I do respect my visitors privacy (that's why I installed your great module in the firstplace) but am still interested in the number of visitors I get. MD5 would be sufficient for starters even though it's not really unique (but IPs aren't either, are they) and I propose it shouldn't be hard to implement -- even though I haven't done any module development so far. If I find time I'll have a look at the source and see what I can contribute.
Cheers.
Edit: md5 <-> unique
#3
This doesn't seem like a very useful feature to me, since it would be trivial to generate the md5 sums of all IP addresses, and then to convert the md5 sums back to IP addresses. So there would be no point in converting them to md5 sums in the first place. Since I actually want to irreversibly anonymize the IP addresses I am simply converting them to "0".
#4
Indeed, that's true, haven't thought that far. Nevertheless would it be usefull to distinguish between different IP accesses for statistical matters. Mmh, I guess the delema is that we want an algorithm that 1. doesn't compute different numbers for the same input and at the same time 2. makes them irreversible back to the original IP... I'll speak up if I think of something to overcome this paradox.
#5
#6
I don't think you'd be able to or even want to mix visitor statistics with this module.