Closed nugaon closed 1 year ago
Should these kind of permissions be related to currently active account? For example, if the user has several accounts, both portable and local, and allow a dApp to access some specific pod. Then logs out and logs in with a different account. Should that dApp be able to access that pod then?
The permissions should be account based
It is likely to have applications that want to write into a common storage-space with different dApps (favoring interoperability) or have different forks of that which do not reach the default POD based on dAppID.
A feature is needed that allows dApp to interact with a specific POD identified by its name e.g.
comments
. The given POD permissions must be listed somewhere on the UI page of the extension where the user can revoke the permission in the form ofdAppID->allowed pod list
Obviously, the permission request should appear in some sort of popup page for the user with all relevant details. After the confirmation, the POD must be created if it did not exist before.