Solid Webbook - Enabling Social into Solid

[aveltens]

@pmbrull

I do believe that the most tidy and easy to manage approach would be the “members container”, so we first would need to figure out how to assign the permissions on the membership files.

I think there is nothing to figure out. This involves a change in the Solid Spec.

@pmbrull

I am not sure how we could use a solution only on the client. Because we not only need to ensure that the protocol logic is followed correctly

That’s true, but also for the server side. We need a specification for that in the end and apps need to follow it, whether they are client or server-side apps. I am not saying we will never need server-side apps. I just want to go without as far as possible. Also for server-to-pod communication we are still missing important pieces as well regarding authentication, since at least NSS relies completely on browser cookies currently

@pmbrull

any kind of extra computing power.

Why do you think computing power is a constraint here?

@pmbrull

My final thoughts on this are that we are maybe focusing on the wrong approach. Instead of trying to make our social solution fit into the current Solid state, we may need to think how to enhance the pods protocols in the first place.

I deliberatly tried to use Solid “as is” to explore it’s limits. I am sure we need to enhance the Spec and protocols to realize everyhing in the end.