As pointed out in #42, if the local ipfs version is newer than the node used by Superhighway84, then people are unable to initialize a repo for Superhighway84.
It would be helpful if there was a way to make the IPFS node used within Superhighway84 initialize its own repository in case there are problem with the exiting one. This way we wouldn't be depending on the external ipfs binary anymore and users could simply run Superhighway84 without caring too much for IPFS internals.
As pointed out in #42, if the local ipfs version is newer than the node used by Superhighway84, then people are unable to initialize a repo for Superhighway84.
It would be helpful if there was a way to make the IPFS node used within Superhighway84 initialize its own repository in case there are problem with the exiting one. This way we wouldn't be depending on the external
ipfsbinary anymore and users could simply run Superhighway84 without caring too much for IPFS internals.