On Mon, Jul 08, 2024 at 02:28:09PM -0500, Michael Catanzaro wrote: > timestamps. But we do need to audit and make sure that if timestamps > are stored anywhere else, we must reduce their granularity to > prevent them from being matched up with timestamps from other > records. It's probably more than sufficient to know that a metric For what it's worth, for DNF Countme, we decided that _weekly_ was sufficient. > 1. You might be able to guess that records are from the same user > based on the order of the rows in the database. I'm not sure what > will be the final solution for this. Randomizing the position of new > rows would surely avoid this problem, but could possibly have > performance impact at scale? I'm not sure. We'll need to do > something about this to keep our promise that it should not be > possible to correlate records. Do we need individual rows for each record, or just a row which includes a count of the number of such records? -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
