guides/user: Update scope default from 'all' to 'followed' — radicle.xyz

rad:z371PVmDHdjJucejRoRYJcDEvD5pp

Radicle website including documentation and guides

guides/user: Update scope default from 'all' to 'followed'

Merged ade opened 2 months ago

As part of the v1.7.0 release the scope defualts for clone and seed have changed from ‘all’ to ‘followed’. Update the user guide to reflect this change.

Activity Changes +15 -17

1 file changed +15 -17 24cfa8d9 → d91591f4

modified _guides/user.md

@@ -461,8 +461,6 @@ nodes. In the early stages of the Radicle network, all public repositories are

 automatically seeded by `iris.radicle.xyz` and `rosa.radicle.xyz` which
 are *public seed nodes* run by the core team.
 <!-- TODO: Talk about seeding policies and following -->
 <aside class="span-2"> <strong>Seed nodes</strong> are always-on machines that
 significantly enhance the network’s capacity to provide continuous access to
 repositories. They can vary in their seeding policies, from public seed nodes

@@ -645,7 +643,7 @@ Radicle protocol. An alpha version was initially released in April 2023.

 </aside>
     $ rad clone rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5
     ✓ Seeding policy updated for rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5 with scope 'all'
     ✓ Seeding policy updated for rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5 with scope 'followed'
     ✓ Fetching rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5 from z6Mkk4R…SBiyXVM..
     ✓ Fetching rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5 from z6Mksmp…1DN6QSz..
     ✓ Fetching rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5 from z6MkrLM…ocNYPm7..

@@ -688,7 +686,7 @@ This works similarly to cloning, where the RID is provided, the main difference

 is that it doesn't create a working copy.
     $ rad seed rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5
     ✓ Seeding policy updated for rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5 with scope 'all'
     ✓ Seeding policy updated for rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5 with scope 'followed'
     ✓ Fetching rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5 from z6Mkk4R…SBiyXVM..
 When you seed a repository, it updates your seeding policy to subscribe to

@@ -717,21 +715,21 @@ some way, for example by pushing a branch or commenting on an issue, simply run

 > 👾
 >
 > The set of peers that are followed in the context of a seeded repository
 > is called the *scope*.
 >
 > The set of peers that are followed in the context of a seeded repository is
 > called the *scope*.
 >
 > By default, when cloning or seeding a repository, your node will subscribe to
 > content from *all* peers. This behavior is part of the seeding policy and can
 > be changed by passing `--scope followed` to the `seed` and `clone` commands,
 > to only subscribe to content from the repository *delegates* plus any node
 > that is explicitly followed via `rad follow`.
 >
 > content from the **repository delegates plus any node explicitly followed via**
 > `rad follow`. This behavior is part of the seeding policy and can be changed by
 > passing `--scope all` to the seed and clone commands, to subscribe to content
 > from all peers.
 >
 > If a repository wasn't initially cloned or seeded in this way, it can also be
 > changed later via the `rad seed` command, e.g.
 >
 >     rad seed rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5 --scope followed
 >
 > Conversely, to reset it to the default, `--scope all` can be passed.
 >
 >     rad seed rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5 --scope all
 >
 > Conversely, to reset it to the default, `--scope followed` can be passed.
 This marks the end of our initial foray into Radicle. As we move forward to
 Chapter 2, we'll dissect the collaborative mechanisms at play, exploring

@@ -1437,7 +1435,7 @@ synchronized to your device.

 You can change this behavior by specifying a different scope when cloning or
 initializing a repository, with the `--scope` option. For example, `--scope
 followed` will only synchronize changes by peers you explicitly follow with the
 `rad follow` command. The default is `--scope all`.
 `rad follow` command and the delegates. This is default behaviour.
 But if a peer becomes a regular collaborator, it would be useful to add them as
 a Git remote to track their changes and `checkout` their branches, even if