There are some comments on our HN post about this tool that are concerned that we don't address the elephant in the room: that this tool is really not a good solution if you intend to make the resulting data public. There is countless research to show that de-anonymising data is completely possible with increasingly less effort because there are almost always unique "fingerprints" leftover in anonymised data.
We should add something to the README that:
Addresses these issues, and talks about when you should use this tool.
Makes sure that we point users to tools more appropriate to the job if you want to make resulting data public.
Makes sure that even those tools are caveated with links to the research showing their is no silver bullet to prevent de-anonymisation.
There are some comments on our HN post about this tool that are concerned that we don't address the elephant in the room: that this tool is really not a good solution if you intend to make the resulting data public. There is countless research to show that de-anonymising data is completely possible with increasingly less effort because there are almost always unique "fingerprints" leftover in anonymised data.
We should add something to the README that: