diff options
Diffstat (limited to 'NETWORKING')
| -rw-r--r-- | NETWORKING | 45 |
1 files changed, 45 insertions, 0 deletions
@@ -102,3 +102,48 @@ which is able to reach the whole public network of cjdns. TODO: We should be storing the output on a relevant file so it can be reached by the API as well or ask for current known nodes without rescanning the network. + +Part 5: Update on networking +---------------------------- +Great news everyone! `ak-network` is here: +``` +$ ak network +ak-network - AK Nettool +======================= + +Network tools + +Usage: + + -h, --help Prints this help message + + -c, --connect [ipfs|cjdns] Connect to network(s) + + -p, --peers [ipfs|cjdns|stellar] Outputs peers found + + -s, --scan [ipfs|cjdns|stellar] Scan network(s) for peers + +Bonus: CJDNS network scanning flags + + -s, --scan cjdns [-w|--whole] Scan using HIA's knowledge + + -s, --scan cjdns [-d|--dump] Scan using CJDNS' dumpLinks (default) + +``` + +Though: +``` +$ ak network --scan ipfs +20240707_065927 <ak-network> [ERROR] Not implemented: _ak_network_scan_ipfs +``` + +Which I think I should not try to do since we use `ak-config` as the key on IPFS +to publish our `node_info` at and we can not guess keys just in case we found +one with `node_info`. A work around could be to use the `self` key and publish +there instead of `ak-config`. Previously, since we were using for `IPFS_REPO` +the default directory, it was thought that the `self` key could be already in +use. Now that we do have our own dedicated path for `IPFS_REPO`, it could be +revisited. But, as mentioned in other places, we are about to drop IPFS in the +future. Whichever comes first? + +TODO ^^ maybe |