What new features do you think you need to implement to comply with GDPR?
`id, name, email_address`
You could simply blank out everything apart from `id`.
Regarding logs, it might be worth thinking about whether you actually need them to contain personally identifying information (e.g. IP addresses, usernames) - if not, just don't log them.
If not, then why do you expect the EU to go after the equivalent site with a few thousand users?
Does this apply? [1]
[1] http://fortune.com/2017/07/21/five-year-old-fine-lemonade-st...
* the fine has been cancelled and the council has apologised
* this is such a rare occurrence to be worth news reports
I'm going to say it validates the point.
> why do you expect the EU to go after the equivalent site with a few thousand users
You are saying that they DO that, but then will (probably) apologize afterwards. Some website owners consider that an unacceptable risk.
There's a huge chunk of the web that is filled with niche web tools, mostly made as a hobby, running for free. I myself own 2-3 such sites. Now, I'm forced to spend my hobby time adding a bunch of new features on a site that already loses money? I'm sorry but the couple thousand people that depend on this tool will have to find someplace else I guess.
HN sure loves to worry about AMP killing the internet, well to me this is far more dangerous. Can't wait for larger troll companies bullying small devs with lawsuits and killing all their competition using GDPR.