Regarding 1): What I was told by the Polypoly.eu guys is that they were pushing for and helping with the policy making that led to the GDPR. They said that onc

Regarding 1): What I was told by the Polypoly.eu guys is that they were pushing for and helping with the policy making that led to the GDPR. They said that once it gets weaponized, using e.g. ML, it becomes /very/ effective at protecting an individual's privacy. Think seeing some picture of yourself drunk at a stag night in a strip club on FB and marking it for being moved to your private pod (for memory's sake) or deleted (because you hold a leadership position and the picture doesn't resonate 'enough' with your carefully crafted social archetype). Now the pod software will ask FB to remove the picture with a timeframe X in compliance with GDPR. Including each and every copy of the content they hold. All this happens automatically. This also triggers a process that checks if the data has disappeared from the public after timeframe X has passed. If not, the whole thing gets added to a class action lawsuit bundle by an AI. This also happens automatically. When the lawsuit reaches critical mass, it gets filed in Brussels. Automatically. Regarding 2): This is indeed a big problem still. But even more so is why people use e.g. FB in the first place. I think it will require some sort of services running atop the the pod infrastructure to make up for the loss of convenience the disappearance of certain data from platforms like FB has on end users. And I see a missing piece here, at the end, in the approaches of Inrupt/Polypoly.