5 ms·
If you have a side project that siphons personal information from people for no reason, then maybe the gdpr isn’t the problem...
by olliej 9y ago
If you have a side project that siphons personal information from people for no reason, then maybe the gdpr isn’t the problem...
- itake 9y agoI don't have time to build user exporting, user deletion, user notifications, amongst other required features on top of the already big backlog of fearures to do. I use third party tools to help worth logging and error tracking. Its just not worth my time to support gdpr on a website that makes no money.
- fwdpropaganda 9y agoDon't worry, people will build those tools open-source the same way that they've built other tools for other purposes. I'm sure if a Django library for doing all those things doesn't already exist, it will very soon. It will become a popular project too, because at some point it will become the default. I meant, respecting the law has been a thing for many years, you know? GDPR isn't really different.
- deleted 9y ago[deleted]
- matthewmacleod 9y ago“I don’t have time to label and expire all the food I prepare on top of serving meals to customers” “I don’t have time to do all those structural calculations on top of all the properties I have to build” “I don’t have time for all this silly human safety testing on top of all the drugs I have to develop” Your statement is equivalent to the above. If you are unwilling to meet a relatively straightforward level or privacy and security for your users’ data, then personally I’m really glad that you’re going to prevent users from accessing it.
- orand 9y agoNice ridiculous examples. Now for some ridiculous examples on the other end of the spectrum: "If you refuse to document every ingredient and possible allergic reaction when inviting friends over for dinner, then I'm really glad if you don't have any friends." "If you don't create structural and safety calculations for your kids' tree fort, then I'm really glad when your kids fall out." The point is, people need to be able to start small and then scale up if/when that makes sense. If everything has to start "big" (relatively speaking), then we will simply have fewer things, to the detriment of all.
- matthewmacleod 9y agoWhy are those examples ridiculous? They are all, like the GDPR, examples of regulation that says “demonstrate a basic level of care and attention when performing activities which may cause damage to users or customers”. GDPR provisions are not onerous, are easy to follow, and are what we should expect every company handling personal data to already be doing.
- orand 9y agoThe original parent examples were side projects that make no money. So while it seems reasonable to expect this of companies, GDPR also applies to nonprofits, charities, things you create just for your friends, some random thing you put on the internet when you're 15 years old and have no clue about GDPR, etc.
- huebnerob 9y agoYes, but my understanding is that you don't need to automate these features, so you would just do it all manually until your scale starts to make building tools worth it.
- andonisus 9y agoMaybe they don't want to spend time doing it manually...?
- rando444 9y agoThis is why I like the GDPR. If you can't be bothered to care about people's personal information, then maybe you don't need it in the first place.
- huebnerob 9y agoStatistically, we're not talking about a lot of requests here and they're most likely to be deletions which should be trivial.
- olliej 9y agoExactly how hard is it to do select * from x where user == “whoever”; Or whatever the syntax is. Alternatively: why are your personal projects storing that data in the first place? If you’re unwilling/unable to put the time into something as trivial as making an archive I’m assuming you also aren’t putting the time into making your data storage secure. Arguably securely storing data is harder than producing an archive. Or are you saying that gdpr sucks because it actually requires you to care about user data? Seriously if you think gdpr is “too hard” just. Do. Not. Store. User. Data. This is not hard. Arguably it is easier and cheaper than any option, including filtering users.
- trca 9y agoThis is an extremely naive bunch of statements. For side projects where there is only a single developer, it's not a matter of "not caring" but literally not having the time to do these things. Putting an archive system into a service may not be as easy as a DB query. It could be pulling images out of a file storage system, generating thousands of PDF documents or a million other ways data is stored. I hope you can realize that oversimplifying every application to a DB query is just absurd. Add on top of that, now the developer needs to support an entire separate system for pulling data out in addition to whatever the project is meant for. What if this system breaks? Does the developer have to guarantee uptime for this system? Also, I fail to see how not having time to build an archive system equates to the developer not storing their data securely? That's just an accusation you decided to make which is irrelevant and accusatory. The point of this post was to show an easy way to ensure you're compliant in 15 lines of code. Building the archive system and associated subsystems will be more than that, without question. Just because you don't like this solution doesn't mean it isn't a solution.
- olliej 9y agook, I am going to be nice here: * how are you structuring data such that it is available to you and your site, without also being able to pull it all out into an archive? * literally all of my experience has been that securing data is a much harder challenge than any other part of a web facing system. Also, the thing that everyone seems he’ll bent on ignoring: you do not need an archive mechanism if you do not store data. And given we’ve known gdpr has been coming for at least a year - aside from companies that tried to bribe it away I guess - new projects should have there data set up so that archiving isn’t a monumentally challenging task.
- inetsee 9y agoMy reading of the GDPR says that the MINIMUM fine is 20,000,000 Euros, which I think would be a pretty big problem for an individual working on a side project. I also think the 403 error page explaining that the GDPR is the reason the visitor can't access the page is a nice touch.
- matthewmacleod 9y agoYour reading of the GDPR is wrong. There is no minimum fine. There is a maximum fine of €20m or 4% of global turnover, whichever is greater.
- dragonwriter 9y ago> My reading of the GDPR says that the MINIMUM fine is 20,000,000 Euros. €20M is the minimum value for the upper limit of an Article 83(5) or Article 83(6) administrative fine; it's not a minimum fine, and a lesser value (€10M) applies as the corresponding base upper limit for some other violations.
- icedchai 9y agoIt's only a problem if you are fined, and actually pay it. The odds of an individual, unknown, low traffic side project facing these problems are effectively zero. Go play the lottery.
- Sohcahtoa82 9y agohttps://gdpr-info.eu/art-83-gdpr/ https://gdpr-info.eu/art-83-gdpr/ The wording says fines "up to 20,000,000 Euros" "up to" usually implies a minimum, not a maximum.
- dragonwriter 9y ago> "up to" usually implies a minimum, not a maximum. “Up to” literally means a maximum.
- olliej 9y agoMaybe they work in advertising ;)