Deploying a personal node on a VPS or similar is oftentimes done to ensure personal repos are replicated while the personal machine is offline without relying on public seed nodes. This also enables use cases like collaborating on private repositories.

The intention of those users is not to run a seed node but rather to seed a personal subset of repositories.

Currently this setup involves SSHing into the node to update the seeding policy whenever a new repository needs to be tracked.

It would be convenient to set up a node to follow the seeding decisions of other users on the network.

• This would help with the simple use case of making my repositories available
• This would help with the team node use case of making every team members repositories accessible
• This could even allow to create a non-permissive seed-node that replicates almost all of the network by following the moderation choices of another node