4 ms·

> You want to launch something online and collect user data? Be responsible with it. You imply I should "be responsible" in return for the value I'm getting fr

by cbeach 8y ago

> You want to launch something online and collect user data? Be responsible with it. You imply I should "be responsible" in return for the value I'm getting from the user data? If so, you're wrong about the value part. I don't see any value in data from users - I see it as a dangerous liability and something I'd rather was not stored on my servers. I code in order to provide a service, which I do because it's satisfying to use my skill to build something I'm proud of, and something that helps other people out. I do not code to collect user data. And, by the way, I am responsible with user data - probably more so than many large organisations with the legal capacity to defend against GDPR claims.

madeofpalk 8y ago
I'll stop the implications and be explicit: the moment you consciously put a form out on the internet and invite users to enter there personal information, and you store it, you must be responsible for it. Not "in return" for anything - you collected the data, so it's your responsibility. In the same way that if a chef who, for the love of their art, opens a street food stall and sells food, they are responsible for the food they're handing out. They have to make sure that they're following safe and healthy food preparation guidelines.
- cbeach 8y ago
  Perhaps you could stop the implications that I'm being irresponsible with data, or that I plan to be. The GDPR is a flawed, ambiguous law that will not turn all website creators into responsible actors overnight. Instead, the GDPR will just create more fodder for vexatious claims - more opportunities for a minority of unscrupulous lawyers to monetise the pain of creators.
  - madeofpalk 8y ago
    But there's already 'ambiguous laws' (laws have to be ambiguous btw if they want to remain relevant) that you could be fined over! I don't really get the new problem with GDPR specifically. > Perhaps you could stop the implications that I'm being irresponsible with data, or that I plan to be. Look, I don't think that you're irresponsible with data. In the same way that food safety regulations don't imply that restaurants are being unhygienic. Honestly, my gut feeling here is that these were just some minor side projects that you were rather ambivalent about before anyway and you decided that GDPR was enough to 'pull the plug' on a bunch of side projects that were already on life support.

by cbeach 8y ago

madeofpalk 8y ago

I'll stop the implications and be explicit: the moment you consciously put a form out on the internet and invite users to enter there personal information, and you store it, you must be responsible for it. Not "in return" for anything - you collected the data, so it's your responsibility. In the same way that if a chef who, for the love of their art, opens a street food stall and sells food, they are responsible for the food they're handing out. They have to make sure that they're following safe and healthy food preparation guidelines.

cbeach 8y ago
Perhaps you could stop the implications that I'm being irresponsible with data, or that I plan to be. The GDPR is a flawed, ambiguous law that will not turn all website creators into responsible actors overnight. Instead, the GDPR will just create more fodder for vexatious claims - more opportunities for a minority of unscrupulous lawyers to monetise the pain of creators.
- madeofpalk 8y ago
  But there's already 'ambiguous laws' (laws have to be ambiguous btw if they want to remain relevant) that you could be fined over! I don't really get the new problem with GDPR specifically. > Perhaps you could stop the implications that I'm being irresponsible with data, or that I plan to be. Look, I don't think that you're irresponsible with data. In the same way that food safety regulations don't imply that restaurants are being unhygienic. Honestly, my gut feeling here is that these were just some minor side projects that you were rather ambivalent about before anyway and you decided that GDPR was enough to 'pull the plug' on a bunch of side projects that were already on life support.