Use different hashing algorithm/uuid for fingerprints

[Kugelschieber]

So that the fingerprint cannot be unhashed again.

This is not an issue as long as you (the user) don't decrypt the hashes and no one gets access to your database. Consumer IPs usually change after a while, as ISPs use IP pools for their customers.

[Kugelschieber]

Not worth the effort, because:

1. no untrusted person should get access to your database
2. fingerprints are dropped when processed
3. decrypting MD5 hashes, even if they are weak, takes effort and they only contain the IP and User-Agent of a visitor, which is toleratable