ordo_inf
We don't need crappy pens, toys, electronics, etc...
I don't know about you, but I'm personally happy to own one ballpoint pen that'll last me for 20 years (and only have to refill it from time to time). If anything, just to not see some poor guy work as a slave (long work-days, minimum pay, suicide nets). Right now you can just go purchase 10x crappy pens that easily break and dry out for around €2, whyyyy?
Regardless, it's possible to host PyPi wheels yourself if necessary. The installation process wont be as straight-forward as "pip install youtube_dl", but it's still doable with one command.
Also, a recommendation for the youtube_dl crew is to use a self-hosted solution (if GitHub/GitLab/SourceForge wont do). Find a cheap Linux hosting provider and run Gitea on it: https://github.com/go-gitea/gitea
It's the best tips I can give for now.
I don't know if this belongs in the list. xD
What happens? You say we need a (couple of) SELECT-statement(s)? I say we need more than that. Also, I'll tell you right now that doing a SELECT-query isn't something customer support can handle, this is something you ask from a developer or server administrator (== more wasted $$$$). So think about that while we go through the information retrieval process:
(1)-(3) You'll need select-statements, retrieval from log-files (such as access_log and error_log). Text explaining the data and explaining what it is used for. The data should be categorized and machine-readable in a common format. These requirements require a deeper understanding of the systems than just running a Wordpress site with a few plugins.
(4) "the recipients or categories of recipient to whom the personal data have been or will be disclosed;", that includes the payment, hosting and (possibly) delivery services.
(5) "where possible, the envisaged period for which the personal data will be stored, or, if not possible, the criteria used to determine that period;". Again, this requires extra knowledge.
(6) Since we haven't mentioned analytics services or any other privacy invasive service that knows more about the user than what they explicitly provide, this is not applicable in this example. However, it is still applicable for many real-world websites.
(7) Not relevant.
To be fair, the information retrieval can be automated, and a template can be used to compose a GDPR response. However, this does require the company to hire someone competent to do it, and also keep this process up-to-date so that it doesn't conflict with newer versions of Wordpress/plugins. And there WILL be newer versions because exploits are found on a regular basis. The developer will also have to make sure that the data is retrievable, and isn't stored offline or in an inconvenient format (such as the case with compressed logfiles). All of this costs money, and different solutions must be prepared for different systems. If the owner decides to move away from Wordpress to another CMS, he will have to hire someone to also replace the GDPR automation process.
This is not practical for a start-up, or a small business. Unless the infrastructure adapts (again, when?), people will have to write custom scripts/solutions to automate the process.
> And to be fair, GDPR was npt imposed by elites, it was demanded by an awful lot of consumers in Europe.
People are rightfully worried about their privacy, of course we are! But that doesn't give the elites the right to willy nilly impose (because that's what they have done) any solution without at the very least making sure it doesn't infringe upon other rights, and consult experts before writing the law. If they would've bothered to consult a seasoned and non-partisan server administrator, I think GDPR would've looked very differently.
I personally believe that the current infrastructure must change to respect user privacy, but this is not the way to do it.
And aaallll of this doesn't directly address the main issue, which is that the accumulation of laws has caused everyone to become a criminal in one way or another.
"Every law is an excuse for violence."
https://www.reddit.com/r/hearthstone/comments/df0zx5/upset_a...
Most server applications are not designed for invasive laws like this. Think of all the HTTP servers that save IP addresses in log files, or all the mail servers that save user messages, IP addresses, and what not. Think of all the other kinds of software that save "personal data". Now think of the way companies backup this data. Do you think most companies out there have the infrastructure to automatically pull all information about a specific user from all of these sources? No way!!
Sure, a company the size of Activision-Blizzard can maybe pull it of, but the little guy has no practical way to be compliant. Not until GDPR compliance becomes a standard in server applications and backup solutions, and when is that going to happen? This is a serious problem that a few people among the elite have thrown at society without understanding the consequences, or caring about them.
And if you don't comply? Well, then this law is just another set of mines in the minefield.