9b1e2c4 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'

Adrian Duke committed 1 month ago

commit 9b1e2c48fbd153d672ae5c6a3e0712ef6c109256
parent 24cfa8d

1 file changed +15 -15

modified _guides/user.md

@@ -645,7 +645,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 +688,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 +717,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 +1437,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. The default is `--scope followed`.
 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