Łukasz Magiera
Łukasz Magiera
For the cluster case - this would probably have to be implemented at bitswap level, where we'd filter from which peers we want to fetch content. We could do that...
Note that few read-only `/api` endpoints aren't yet covered by this option - see https://github.com/ipfs/go-ipfs/pull/5649#issuecomment-451337849 for the list
https://github.com/ipfs/go-ipfs/issues/5929
It seems to be more of an issue with the cifs fs. Can you record an strace (`strace -ff ipfs init > init.trace`) and send it here? (upload it to...
This would require extracting namesys, but can be done.
What I noticed missing from one of the earlier PRs is the ability to tell to which peer connected to a listener. Earlier PRs had a switch that caused ipfs...
I'd need to look into how websockets are currently handled in go-ipfs. For dialing this should be relatively simple to do, though listen mode would probably have to use some...
This creates listening libp2p handler and when p2p connection is incoming it(ipfs daemon) then opens a tcp connection to a given address and proxies the data. This seems counterintutive at...
I don't think using config for that is a good idea. What may work is extracting whole `ipfs p2p` into a separate program as it doesn't really fit ipfs (imo),...
https://github.com/ipfs/go-ipfs/pull/4929 includes api-breaking changes, it will likely be released with the new version of go-ipfs. EDIT: This changed a bit while the PR was open, this is the current version:...