31–40 of 54 posts
Earlier quoted context omitted.
Yes, 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.
Maybe they don't want to spend time doing it manually...?
If you can't be bothered to care about people's personal information, then maybe you don't need it in the first place.
If you have a side project that siphons personal information from people for no reason, then maybe the gdpr isn’t the problem...
I 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.
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.
HN crowd loves GDPR, so get ready for this never making to the front page.
Do they? It's kind of a mixed bag. I see about 60% say "well, if your side project doesn't respect your users privacy, maybe you shouldn't have a side project.", and the remaining 40% saying "I'm too scared of the consequences from doing illegal stuff"
Earlier quoted context omitted.
Why 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.
The 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.
If you have a side project that siphons personal information from people for no reason, then maybe the gdpr isn’t the problem...
My 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.
Basically if you’re a small business your maximum fine is likely 20 million, if you’re a large one it’s 4% of your global revenue. The global revenue is needed because companies are perfectly happy moving their money around to minimize the amount of money they make in places that will fine and tax them. They’re also super good at manufacturing reasons that profit does not actually get recorded as profit. Also it’s generally accepted that fines and settlements are an expense, so you’d get a situation where ome fine would effectively discount another.
Earlier quoted context omitted.
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.
> "up to" usually implies a minimum, not a maximum. “Up to” literally means a maximum.
Assuming there is any significant adoption of your proposed solution to avoid GDPR rules the likelyhood is EU citizens will use VPN or Proxy services to bypass the restrictions.
I don’t think the use of a VPN would remove the GDPR obligations on the data controller or data processor.
Earlier quoted context omitted.
I 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.
Exactly 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 archiv…
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.
Earlier quoted context omitted.
The 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.
If it makes no money why spend money on storage?
Earlier quoted context omitted.
Exactly 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 archiv…
This 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 r…
* 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.