This makes the default policy block with scope all. The good thing
about this is that you don’t have to manage individual nodes in the
beginning. You simply seed the repos you want, and everything is
followed within those repos. This matches user expectations, as rad seed does what you expect it to do.
For open-policy seed nodes, it also means that simply changing block
to allow from the default config is all you need.
This leaves the non-default followed scope as a more “advanced”
setting, since it is much more cumbersome: it forces you to follow a
user before you can see their issues/patches, which is not something
most users expect coming from old-shcool forges.
This makes the default policy block with scope all. The good thing
about this is that you don’t have to manage individual nodes in the
beginning. You simply seed the repos you want, and everything is
followed within those repos. This matches user expectations, as rad seed does what you expect it to do.
For open-policy seed nodes, it also means that simply changing block
to allow from the default config is all you need.
This leaves the non-default followed scope as a more “advanced”
setting, since it is much more cumbersome: it forces you to follow a
user before you can see their issues/patches, which is not something
most users expect coming from old-shcool forges.
Rebase.