Arvid Norberg
Arvid Norberg
I think the main use case for this is block references being passed in to the generator. I will update this at some point with that use case in mind.
I think there are some good parts of this patch, I would suggest splitting it up into smaller PRs, that do one thing each
there is no way to indicate that payload received by ``on_read`` has not been consumed by the upper layer. If you cannot consume it immediately, you need to stick it...
how would you expect clients to act on this tracker response? normally clients just include extra parameters on the GET request as best-effort, assuming they will be ignored if not...
> if the tracker doesn't include 'bt_v2' in the extension list, it indicates non-support. The point of v2 hashes being truncated is to preserve the DHT protocol and the tracker...
> Okay, I didn't expect that change, in fact I didn't expect any alterations to v2 from now, thanks for clarifying this. What are your referring to as having changed?...
you would probably need permissions to such service. Especially if you expose it to (untrusted) web pages running in your browser.
ping @xercesblue @the8472
> It skews the availability calculations that clients make I take it you don't mean the piece picker's piece-availability state, right? presumably it would not track availability of pieces it...
> I'm worrying because I already see clients misbehaving and unilaterally dropping haves. So I see this as encouraging this further, even talking about making it the default behavior in...