This is cool from a philosophy of the internet angle. It's also one of the worst workloads to try with P2P so it will be interesting to watch as a business. T

This is cool from a philosophy of the internet angle. It's also one of the worst workloads to try with P2P so it will be interesting to watch as a business. There are a number of fundamentally half-duplex technologies in widespread use, such as wifi. Others have very different transmission characteristics, for instance tx uses a second frequency on cellular but is obviously more power hungry, whereas DOCSIS, wifi, and pretty much any radio network have batching and even ack filtering that make ack clocking or even state of the art things like BBR congestion control difficult. On "eyeball networks", ISPs provision for downstream ratio and wholesale upload bandwidth to businesses as transit. That may manifest as policy such as upload caps, or monetarily. Drastically changing their network profile is more likely to result in hasty policy and financial games rather than re-architecture or capacity expansion. Also fundamentally, TCP is "easy" as a receiver and most stacks in common use are good receivers. TCP as a sender is hard, and most stacks have a ways to come, aside from sub-optimal defaults. Hard problems. Doesn't mean there aren't simple solutions like aggressively clamping where the tech is used. It also might spring the problem on other people (ISPs, and I mean this non-condescendingly but end users) in a way that is eventually a net win.