That would be very handy.
In the meantime, we can probably get at some of the information by mashing together
ipfs refs -r <hash> and
ipfs dht findprovs like so.
( HASH=QmX8LDhDSYdX3xG6cHFUybXLDSuvo9Lz6wF5NU3UVmJRnB ; echo $HASH ; ipfs refs -r $HASH ) | xargs -l bash -c 'echo -n "$0 - "; ipfs dht findprovs -n 2 $0 | wc -l'
This returns output that looks like this:
QmX8LDhDSYdX3xG6cHFUybXLDSuvo9Lz6wF5NU3UVmJRnB - 2
QmPYVMnpamYrLC9W49eJfieh9Po613UUxaBY9UE8Rmrcm6 - 2
Qmaw9M9C7JKwT3XoucoJyxoEJxPxPSp1bpxQvYcLgGJskb - 2
QmQNvsA6aqAL5GRCRokNq7pkQHeJ19rQ45XLcRGaFPiSbR - 2
QmQ5BJLdLM8HShW35RXHoujbkvQxh9UiDZJs44JxkQxtMg - 2
Qmbmfk69gtUqkXLXP6nSh9C3hEBk4hQGGz1Nc6ET7hZtJt - 2
To make this much faster than it would be otherwise,
findprovs is limited to only searching for 2 providers with the
-n 2 flag.
I’m not sure why this happens, but after running this for a while on a large file (like the one in the example) my daemon almost always seems to crash and then
ipfs dht findprovs starts returning “Error: api not running”.