decentralized-web-node
decentralized-web-node copied to clipboard
Expected runtime environments
What environments are hubs expected to run in?
The first image in the spec implies that hubs can run "locally" and in "the cloud". Local is presumably mobile devices and browsers. The spec does not address the fact that local hubs will likely have restrictions that prevent them from running as the spec states.
For example, if a local hub is running within a mobile app, is the expectation that the mobile app be running a server that can accept requests from anyone in the world? I realize that hubs are transport agnostic, but it seems to be the case that hubs necessitate listening over some transport.
I think it might be worth clarifying the distinction
Definitely worthwhile noting limitations of environments, will do a PR for this.
I see this as a delegation issue, not a transport.
If we presume a DID or a directory that points to a service endpoint as the universal foundation, then the transport is subsumed in the service endpoint pointer. The service endpoint could, optionally, be a mediator that points to the hub but the hub transport can be different as long as the mediator is willing to translate.
Building hubs and directories on top of DIDcomm or any other single messaging protocol is possible but seems impractical to those of us that see delegation as the core decentralization issue.
On Thu, Mar 10, 2022 at 6:22 AM Daniel Buchner @.***> wrote:
Definitely worthwhile noting limitations of environments, will do a PR for this.
— Reply to this email directly, view it on GitHub https://github.com/decentralized-identity/identity-hub/issues/124#issuecomment-1063950422, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABB4YPEAGTY4BI6SAYY7WTU7HLOLANCNFSM5QLY777A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
I see the delegation issue here also. If I have 2 nodes, 1 running on the cloud and 1 running on my mobile. I'm always going to want the cloud to handle requests and pub/sub messaging. My mobile has no value in retrying publications, and taking requests.
@csuwildcat bringing this back from the dead.
Thanks! @csuwildcat! Was there a PR related to this? Just so those following this thread can tune into relevant work that resolves this?