Problem
When ActivityPods was started, other SemApps servers were deployed on the root server, with a single dataset, so we added a podProvider setting everywhere to differentiate between the two architectures.
The problem is that this make the code very complicated to maintain.
Proposed solution
Consider everything as a Solid storage. Every storage includes a webId (a person, a group or an application) and a LDP server. If an application needs a single storage, it can create it and work with it. We should allow to disable the creation of other storages (because the server may not want to be a Pod provider !)
ActivityPub would be still optional. If we activate ActivityPub, we won't need to create a "relay" actor anymore because the WebID of the storage will be this relay.
The only difference is that the root path will look like http://localhost:3000/{username} instead of http://localhost:3000.
In the future, we can plan to have "single-storage servers", so that this minor annoyance can disappear. We would like to do this for ActivityPods anyway, so that a user can decide to create a server for his own storage, but no one else.
Problem
When ActivityPods was started, other SemApps servers were deployed on the root server, with a single dataset, so we added a
podProvidersetting everywhere to differentiate between the two architectures.The problem is that this make the code very complicated to maintain.
Proposed solution
Consider everything as a Solid storage. Every storage includes a webId (a person, a group or an application) and a LDP server. If an application needs a single storage, it can create it and work with it. We should allow to disable the creation of other storages (because the server may not want to be a Pod provider !)
ActivityPub would be still optional. If we activate ActivityPub, we won't need to create a "relay" actor anymore because the WebID of the storage will be this relay.
The only difference is that the root path will look like
http://localhost:3000/{username}instead ofhttp://localhost:3000.In the future, we can plan to have "single-storage servers", so that this minor annoyance can disappear. We would like to do this for ActivityPods anyway, so that a user can decide to create a server for his own storage, but no one else.