[wp-trac] [WordPress Trac] #43545: Helper functions: Anonymizing data in a standardized way
WordPress Trac
noreply at wordpress.org
Fri Mar 23 13:28:43 UTC 2018
#43545: Helper functions: Anonymizing data in a standardized way
--------------------------------+------------------------------
Reporter: dejliglama | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Options, Meta APIs | Version: trunk
Severity: normal | Resolution:
Keywords: needs-patch gdpr | Focuses:
--------------------------------+------------------------------
Comment (by jesperher):
Replying to [comment:10 postphotos]:
>
> {{{
> case 'date':
> //should we ever make something to do this? -
can dates be personal?
> }}}
>
> Birthdates or the day when a user joins a service, for example, could
partly reveal identity as it filters a larger dataset into a smaller one.
>
> It reminds me of the great dialogue in the #gdpr-compliance Slack
channel about how user agents aren't exactly anonymous... Also,
[https://www.eff.org/deeplinks/2010/01/tracking-by-user-agent the EFF
wrote a great post a few years back] about what a user agent contains.
>
> My proposal would be to, on random submit for `time`, just return `0
UTC`/[https://en.wikipedia.org/wiki/Unix_time Thursday, January 1, 1970],
which should indicate, universally, that this date was redacted.
I think you are right on this one. I will make it so it returns 0 /
January 1, 1970, nomatter what the input is.
For the user agents - i dont see other solution right now, than just to
return an empty string.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/43545#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list