I think the “near zero latency” is still a valid UX concern. Do you know if it’s possible to setup a webtorrent library in a way that it is forced to try fetching from HTTP the first couple of chunks and only after a short delay fire up the lookup for seeders?

Replies (1)

It's already doing that, there's no round-trip to a tracker required before hitting the webseed directly to get the mov atom and first chunks. It's just a client that makes use of additional data.