dirkmc
dirkmc
I agree I think the glove doesn't quite fit so it's better to punt on back-pressure
The backup pool idea makes sense. The Session may also want to keep track of peers it deliberately removed from the Session (for example because they sent too many DONT_HAVEs)...
I agree with the general idea 👍 We don't need to broadcast so many CIDs. Two considerations: - We may become connected to new peers during a long-running transfer. They...
> it won't get us any closer to finding the CIDs that are already in our broadcast set Ok makes sense 👍 > I'm proposing announcing the last block requested...
I updated the original post to change the interfaces a little. I think we can tackle streaming GetBlocks() separately, but it shouldn't be a bit lift to change it. I'll...
@magik6k what else needs to be done to get the IPNS helper working?
When you say "integrate with keystore nicely" do you mean that when pushing the first time, the IPNS git helper should create a new key in the key store, and...
Currently it prints the IPFS hash of the patched object with an `ipns::` prefix, eg `Pushed to IPFS as ipns::Qmeue...` Do you think it would make sense to instead update...
Ok so I'm imagining that the user would do one of the following: - `git push --set-upstream ipns::/ipns/QmIPNSkey branchname` - `git push --set-upstream ipns:: branchname` In the second case the...
It seems like there is a bug in go-ipfs-api ipns name publish so I will wait till you have completed the work on core API