-
Notifications
You must be signed in to change notification settings - Fork 39
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
Feature: replicate Person data #708
Comments
\cc @CodeSandwich |
Just to clarify here,
This should be already the case. It's when a maintainer (or someone else who is not a maintainer) decides to replicate a non-delegate. |
Unfortunately, this turns out to be a bug-turned-feature: let If we are fetching Most definitely, this is not what we want -- the user told us to replicate OP asked to be able to include However, the reason we track indirect delegations implicitly is the idea that they can revoke keys without having to update all projects for which they are in the delegations set. If we want to retain this, I think the only solution is to allow partial replication akin to fetchspecs. |
On a high level as a user of the protocol, I want
Person
data to be replicated whenever a project is replicated.For example: a maintainer creates a project and that project gets replicated onto a seed node. Then a contributor follows this project and replicates it onto their machine. In this case I expect the maintainer's
Person
data to be available on the contributor's machine in thestate::list_users
list.Required by: radicle-dev/radicle-upstream#1912.
The text was updated successfully, but these errors were encountered: