<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">On 10/11/21 22:57, Matthew Walster
wrote:<br>
<br>
</div>
<blockquote type="cite"
cite="mid:CADLW2vze_5VFXxBi6vLTaAnczxo=QOY-=weJe7dB2M5rG7eNdw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_quote">
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif">Ignoring for
the moment that P2P is inherently difficult to stream with
(you're usually downloading chunks in parallel, and with
devices like Smart TVs etc you don't really have the storage
to do so anyway) there's also the problem that things like
BitTorrent don't know network topology and therefore only
really increases the cross-sectional bandwidth required.</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif">Not to
mention that it has been tried before, and didn't work then
either.</div>
</div>
</div>
</blockquote>
<br>
Yeah, and people also want to click a title and start watching
immediately.<br>
<br>
Someone can correct me if I'm wrong, but the way I know BitTorrent
to work is the file is downloaded to disk, unarchived and then
listed as ready to watch. It also assumes the device has all the
necessary apps and codecs needed to render the file.<br>
<br>
On the other hand, BitTorrent could just make an Apple
TV/PS4/PS5/Xbox/whatever-device-you-use app as well. But I doubt
that will work, unless someone can think up a clever way to modify
BitTorrent to suit today's network architectures.<br>
<br>
Mark.<br>
</body>
</html>