Add flags to configure bootstrapping for peer discovery

[RangerMauve]

Feature request

Dat works great out of the box when you're on the same wifi, or are connected to the internet at large, but it's not as great when you're connected to a network that's not totally local, but isn't connected to the internet. Key uses would be something like #1066 where China was blocking traffic, or #1071 talking about mesh networks, which could be relevant to dweb camp 2019.

I was thinking it could be addressed with CLI flags added to dat clone and dat share which would be passed into discovery-swarm. Maybe just IP addresses to use for bootstrapping to start so that we can get more bang for our buck.

dat clone --bootstrap-dns 192.168.1.1:666 --bootstrap-dht 127.0.0.1:420

CC @pfrazee since this applies to Beaker

[benhylau]

@RangerMauve is this proposal simply to add / swap Internet bootstrap nodes? Similar to ipfs bootstrap add?

[RangerMauve]

Yup!

[okdistribute]

how about a config file which can set a lot of networking options, and those options can also be set through commandline parameters (they would be named the same?)

[RangerMauve]

I really like the config file idea! Maybe we could set something up on top of dat-swarm-defaults so that it can be handled in the same way across tools.

[okdistribute]

sweet!