dat share until a threshold of peers have an up to date version

[mrusme]

I am reporting:

• feature request

I would find an option for dat share very useful that would allow me to specify a minimum propagation of up to date content and make dat quit itself as soon as that was reached. By that, it would be possible to update content from the local machine to at least one homebase instance and have the dat process quit afterwards, so that starting could be automated within e.g. a local build procedure for content.

Suggestion:

dat share --until-propagated=3

for letting the process run until at least 3 peers have retrieved the current version of the content.