-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mapping owners -> published afs #18
Comments
@MarkGeeRomano is this still needed/wanted? |
If it doesn't blow up the cost of publishing, I'd say so. If we don't have this feature, we need to keep track of published by writing to a centralized db or locally. I'd bring Logan in on this too. He was asking about this feature yesterday. |
Okay, @mahjiang what are your thoughts? |
We could add a mapping in the Registry contract to a Struct of some sort which holds a This wouldn't allow us to display any resellable content (post MVP scope). If the purpose is to allow someone to easily obtain a list of content they can purchase from someone, then we'd want to take that into consideration as well |
Tabling this issue for now. I think the approach we are taking is if new features come out after the core contracts have been deployed, we will rely on services which aggregate blockchain events to provide us the information we need. |
For the dapp, there is a 'Published' view in the ui, that displays all of the files published under the AID of the user. Currently, there's no mapping of owners directly to their afs. This would be a really nice feature to have for the dapp, and probably for any other projects built off ara and the probably for the users themselves. We could just make a
call
to one of the contracts, and return an array of did we could render to the app.The text was updated successfully, but these errors were encountered: