I’ve been playing with ipfs and applications that use ipfs. I’ve noticed every application use ipfs daemon in a different way and doesn’t necessary interact with each other.
For example, IPFS-GUI starts
ipfs daemon but doesn’t recognize if I launch daemon from command line. Arbore launches a daemon from an installed go-ipfs. Akasha embeds his own daemon (which conflict with already installed go-ipfs). While Chrome extension always detects if a daemon is running.
It’s not easy and confusing to test multiple apps… Should there be a consensus on own applications handle ipfs daemon ? (detect an already running daemon, check ports, propose to change path for a second daemon…)