This might belong to The Basics, but I think this is more suitable. There should be some best practices for applying Solid to social, so that end users will be able to apply their understanding to several systems.
A common example given for Solid is this scenario:
A publishes a picture and stores it on their Solid Pod PodA
B comments a picture and stores the comment on their PodB
C looks at the picture and also sees the comment, thanks to the magic of RDF
That is the simple usecase and easily understood. The picture belongs to A, the comment to B.
But what if A objects to the comment being shown on their picture? I can imagine that A can then disable the link on PodA- so the comment is not shown anymore when the picture is loaded.
People can probably still go to PodB and see the comment there - and probably also still get to the Picture because there is a comment link still on PodB?
Should A be able to prohibit B from making that comment link?
Things get interesting when we have a group discussion:
A hosts a place where people can discuss topics.
B posts a statement there
C comments on the statement
That leads me to several questions:
- Who should be able to modify or delete the comment or original statement?
- Where is the statement stored?
- Where is the comment stored?
- What happens if A eventually decides to hand over the place to D?
The expected behavior would be that when joining the hosted place, people agree that the host acts as a moderator and thus controls everything shown there. That control is usually partly shared, so that everyone can at least modify their own content while some act as additional moderators.
For Solid, I could expect that adding content to such a hosted place would mean that you still keep your own content in your own pod, but also have to give control of that content to the host and their intermediaries?
Or do they only have the permission to remove the link to your content from the hosted place so that your content does not show up there anymore but is still kept at your pod? (Iâm currently favoring this approach)