If this helps, in order to join your network as per @tfa hack to the client.config file, I had to delete the node_connection_info.config file in .safe/node , otherwise that was the file that was used to launch the node
I’m initially going for having an additional networks set subcommand that it can receive IP:port (both ipv4 or ipv6) as opposed to networks add which expects a URL for where to pull the connection info from. So e.g.
$ safe networks add maidsafe-testnet https://sn-node-config.s3.eu-west-2.amazonaws.com/shared-section/node_connection_info.config
Network 'maidsafe-testnet' was added to the list. Connection information is located at 'https://sn-node-config.s3.eu-west-2.amazonaws.com/shared-section/node_connection_info.config'
$ safe networks set folaht-ipv6-testnet [2001:983:8610:1:854:efb1:52e6:85a3]:12000
Network 'folaht-ipv6-testnet' was added to the list. Contacts: '{[2001:983:8610:1:854:efb1:52e6:85a3]:12000}'
$ safe networks
+---------------------+----------------------------------------------------------------------------------------------+
| Networks | |
+---------------------+----------------------------------------------------------------------------------------------+
| Network name | Connection info |
+---------------------+----------------------------------------------------------------------------------------------+
| folaht-ipv6-testnet | {[2001:983:8610:1:854:efb1:52e6:85a3]:12000} |
+---------------------+----------------------------------------------------------------------------------------------+
| maidsafe-testnet | https://sn-node-config.s3.eu-west-2.amazonaws.com/shared-section/node_connection_info.config |
+---------------------+----------------------------------------------------------------------------------------------+