Changes between Initial Version and Version 1 of Ticket #14682, comment 55
- Timestamp:
- 09/21/2019 10:05:26 PM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #14682, comment 55
initial v1 3 3 > The actual issue, and the only sensible fix, is that the Gravatar ID generation code should be changed on the Gravatar website. Anything short of that and you'll still end up with opportunities to track users online. You can obfuscate things with some salting or some algorithm change but you cannot prevent it. And as already noted, even with perfectly adequate hashing on Gravatar's end, Google image search can potentially spoil the party. 4 4 5 Or then, change nothing (?) on Gravatar's end (it's a dumb cache at the end of the day) and advertise a new ID generation method for others to use on client websites. But keep in mind that WP is only dominant in the blog/CMS space. 5 Or then, change nothing (?) on Gravatar's end (it's a dumb cache at the end of the day) and advertise a new ID generation method for others to use on client websites. But keep in mind that WP is only dominant in the blog/CMS space. Change will be very slow.