When trying to run GDPR dump on a database with a lot of users, this will take a lot of time. This is because the relevant anonymisers use the Faker library with the option to keep usernames and email adresses unique. This, of course, is a requirement for Drupal. However, because Faker has no context, the only option it has to guarantee uniqueness, is to keep a record of values that have already been issued. This causes the process to become slower and slower. For a database with a few dozen users, this is not an issue. For a database with thousands of users, it quickly becomes one (note that the latter is more likely to have GDRP issues when an unsanitized database were to leak).
Given a development site with a handful of users:
Pass row data (or allow an anonymizer plugin to opt to receive it) and create a plugins for username and password sanitization using the new mechanisme, derived from the user ID.
Agree on solution.
Create merge request
Review
Merge
New anonymiser plugins will be available.
We will need a way to pass row context into anonymiser plugins.
None.
Active
3.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.