In the spirit of reporting things that can improve the UX.

Here is an example of a rad clone that eventually succeeds:

$ rad clone rad:z35CgFVYCKpqqDtJMzk8dyE6dViS6
✓ Seeding policy updated for rad:z35CgFVYCKpqqDtJMzk8dyE6dViS6 with scope 'all'
✗ Fetching rad:z35CgFVYCKpqqDtJMzk8dyE6dViS6 from z6Mki4C…kfVo5Zr.. error: failed to perform fetch handshake
✓ Fetching rad:z35CgFVYCKpqqDtJMzk8dyE6dViS6 from z6MkrLM…ocNYPm7..
✗ Fetching rad:z35CgFVYCKpqqDtJMzk8dyE6dViS6 from z6Mksmp…1DN6QSz.. error: failed to perform fetch handshake
✓ Fetching rad:z35CgFVYCKpqqDtJMzk8dyE6dViS6 from z6MkmvN…3GFjkf2..
✓ Fetching rad:z35CgFVYCKpqqDtJMzk8dyE6dViS6 from z6Mksqu…7327TEt..
✓ Creating checkout in ./radicle-ci-ambient..
✓ Remote liw@z6MkgEMYod7Hxfy9qCvDv5hYHkZ4ciWmLFgfvm3Wn1b2w2FV added
✓ Remote-tracking branch liw@z6MkgEMYod7Hxfy9qCvDv5hYHkZ4ciWmLFgfvm3Wn1b2w2FV/main created for z6MkgEM…1b2w2FV
✓ Repository successfully cloned under /Users/yorgos/dev/radicle/projects/radicle-ci/radicle-ci-ambient/
╭──────────────────────────────────────────────╮
│ radicle-ci-ambient                           │
│ Radicle CI adapter for the Ambient CI engine │
│ 6 issues · 1 patches                         │
╰──────────────────────────────────────────────╯
Run `cd ./radicle-ci-ambient` to go to the repository directory.
25-04-02 9:28 ➜  radicle-ci rad node status
✓ Node is running.

╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ Peer                                               Address                        State       Since         │
├─────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ z6Mki4CGSgAgzf1dUpgwzs4eXSsqyyGMMraBn86LukfVo5Zr   seed.radworks.garden:7777      connected   10.32 hour(s) │
│ z6MktbmhQxBYWcqE6MTRd4XEp8gKtfrxafmqiotqjyxphc5P   radicle.dpc.pw:8776            connected   10.33 hour(s) │
│ z6Mkj8fboRBXkHYvAnDnzc5bc8jh5jhJNmcK7SLTJw6SphqX   radicle.fillari.xyz:8776       attempted                 │
│ z6MksErwFmss7v3ahBAF7d8uadKBsHFK58dsA7pdLLqcD9YN   rad.credenso.cafe:8776         connected   10.32 hour(s) │
│ z6MkvswafXNZe3VeZG8yAuxbXiwMV4paK19nZQLptxs6r7pE   seed.thefarshore.dev:8776      connected   10.33 hour(s) │
│ z6MkgPQzQNqLjDxfPbU8Ct6zVE7ctnJ7owDtyevfB5Ap5VXr   seed.lioka.obninsk.ru:8765     attempted                 │
│ z6MksCgjxU4VZt6qgtZntdikhtXFbsfvKRLPzpKtfCY4rAHR   seed.vidarmagnusson.com:8776   connected   10.33 hour(s) │
│ z6MksmpU5b1dS7oaqF2bHXhQi1DWy2hB7Mh9CuN7y1DN6QSz   seed.radicle.xyz:8776          connected   10.32 hour(s) │
│ z6MksnL33SUMHhXbJTacUunU8sghiYmMKPQ8w6WGggkzbZme   radicle.fedimint.org:8776      connected   10.33 hour(s) │
│ z6MksW9jjJurZz968iWAJJwdj7zJBDPXmcTdDxCA8je3UuX5   132-145-248-26.sslip.io:8776   connected   10.33 hour(s) │
│ z6MkexpEu1KndFksdpMNAQnMMeg8B4SX4sP77Pjw1WTPT1f5   seed.kdevlab.com:8776          connected   10.33 hour(s) │
│ z6Mki1A19fZDxXT1XB2j3RGMEo4tKq43r9hm2HoaDZjKdEFn   seed.syu.ovh:8776              connected   10.33 hour(s) │
│ z6MkrLMMsiPWUcNPHcRajuMi9mDfYckSoJyPwwnknocNYPm7   seed.radicle.garden:8776       connected   10.32 hour(s) │
│ z6MksquLuyRingrR4gB399a8HdEg3CZtgusjoHWTq7327TEt   radicle.linuxw.info:8776       connected   10.33 hour(s) │
│ z6MkrEyxh4FtegNuAJFAwjyLL4ZT6M7i4ENYzLJmrcAEYX1D   seed.voidfarers.net:8776       connected   10.33 hour(s) │
│ z6Mkn5jXo24ZmXQGfTW9x22Hrb6pCGXpdEgr9yBTVAHtErQE   rad.nihili.st:8776             connected   10.33 hour(s) │
│ z6MkjZoLDRpZb8GXnMrfsXPtWkVJrLPcCiMkvffNgHUYBQ9T   seed.nyaw.xyz:8776             connected   10.33 hour(s) │
[...]

On the one hand, the error: failed to perform fetch handshake is confusing: the clone operation succeeded.

On the other hand, it is confusing because my node is connected to both those nodes with which the handshake failed…