-
Notifications
You must be signed in to change notification settings - Fork 14
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
does directory.rho implement the PetNames ocap pattern? #8
Comments
looks like things are moving to https://github.com/rchain-community/community ? |
directory.rho is a key-value store not necessarily about users. It allows separate object capabilities to be created (granted) for each key which makes it useful for user directories with a self modification capability. A pet names directory could be created using it. |
@dckc @jimscarver |
In our demo we used registry URIs. That certainly doesn't address this issue. |
#126 helps to address the issue of using URIs, but https://github.com/dckc/awesome-ocap/wiki/PetNames is not my area of expertise, so I leave resolution to @dckc |
petnames are not implemented yet but everyone has a personal directory so there can be a personal rover, a group rover and a global rgov rover. |
So as stated, the issue is addressed: no, it doesn't. I'm still interested in PetNames, but I can make a separate issue if I get any more clear about it. |
here's hoping I find time to review from this angle.
https://github.com/dckc/awesome-ocap/wiki/PetNames
p.s. This is meant as an issue in the liquid democracy work. @jimscarver , your latest work on directory.rho seems to be here in rho-bot, so I'm raising the issue here.
The text was updated successfully, but these errors were encountered: