News for hackers. Stuff that matters.
Re:Improving compression at scale with Zstandard by koolba on Wednesday December 19, 2018 @05:30PM (#18720475)
> And the zstd binary itself includes a dictionary trainer (zstd --train). Building a pipeline for handling compression dictionaries can therefore be reduced to being a matter of gluing these building blocks together in relatively straightforward ways.

What happens if your user data trained dictionary ends up storing user data and you receive a GPDR destruction request?

Re:Improving compression at scale with Zstandard by bowmessage on Wednesday December 19, 2018 @05:33PM (#18720505)
standard GDPR cop out disclaimer that's something about needing to keep the data for technical reasons

I wish I knew more about it, but that's what I keep hearing.

Re:Improving compression at scale with Zstandard by karavelov on Wednesday December 19, 2018 @05:44PM (#18720588)
The dictionary data in not personally identifiable, so no need to do anything. At least this is my understanding of GDRP, I am not a loyer.
Re:Improving compression at scale with Zstandard by Legogris on Thursday December 20, 2018 @03:41AM (#18723363)
It would not be covered by GDPR, just like e.g. private emails containing PII about a third party are not in scope from perspective of the e-mail provider.