@sun@oleksandr Federated networks already can't be compliant with GDPR, because there's zero guarantee that deletes federate properly. So far nobody tried to troll an instance operator with GDPR requests, but I wouldn't be surprised if someone tried in the next few years.
@sun@oleksandr Yes and no. It's in a gray area that nobody has the interpretation for. As an operator, you have the responsibility to delete the content and prevent it from getting accessible again (through exclusions on backup restores for example). If that also means making sure that every copy of it on the network is gone, or deleting it only on your end is sufficient, nobody knows yet I think.
@vokainen099@oleksandr@sun Read paragraph 2. I think in this case a Fediverse server acts as a data controller since it doesn't process the data on behalf of the controller, but I'm not sure because part of their database seems to be down. What is a reasonable step and a technical measure isn't defined in Art. 4 Definitions.
@phnt@oleksandr@sun That would technically apply in other cases even to other web platforms that sold your data at any point to any third party, whether you were willing or not, and, guess what, they can't go and order those third parties to delete your data either, at least demonstrably in a court-compliant manner
So, no, this would not apply only to the federation.
Those regulations are largely unapplied, BTW. They theoretically ban "automated treatments" but, guess what, the Internet is full of bots/AIs that ban/unban or administer other services with or without user input, and none do anything