The terminology used by the #GDPR Article 4 [1] might be helpful here, IMHO (In My Humble Opinion). The concepts behind “controller”, “processor” are more in the #DigitalSovereignty realm, the concepts behind “recipient”, “consent” belong more to the #DigitalIndependence realm. But it’s not binary. More Venn Diagram with overlaps. And these overlaps are where things become really interesting and hard to solve.
Discussion
Loading...
Post
Both things interact, but lumping them together as one is oversimplifying the different perspectives from an individual (human) rights expectations with regards to “their” data and the requirements of organisations tasked with organising data and access for many. So #DigitalIndependence works better with services that have #DigitalSovereignty, but they are not the same thing. Hrmpf. It’s hard to explain, I’ll work on a better explanation.
The terminology used by the #GDPR Article 4 [1] might be helpful here, IMHO (In My Humble Opinion). The concepts behind “controller”, “processor” are more in the #DigitalSovereignty realm, the concepts behind “recipient”, “consent” belong more to the #DigitalIndependence realm. But it’s not binary. More Venn Diagram with overlaps. And these overlaps are where things become really interesting and hard to solve.
Addendum: This is why I think #SelfHosting is more about #DigitalIndependence than #DigitalSovereignty, for example.
And yes, services that implement #DigitalSovereignty can still violate my #DigitalIndependence when they use my data our data about me.
The digital life is complex, not binary ...
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled