@7235c54512c28918a4dcb0d47aa48709feef5c4be45e85f5672cdc4a9a32a871 @d0debf9fb12def81f43d7c69429bb784812ac1e4d2d53a202db6aac7ea4b466c @63fe6318dc58583cfe16810f86dd09e18bfd76aabc24a0081ce2856f330504ed wrong on a couple fronts.

PeerTube can use a variety of s3 compatible object stores and CDNs to store the video data. This means the bandwidth limits for the video comes from the CDN system, not the peertube instance.

Additionally when other PeerTube instances enable redundancy, they make a local copy of popular videos and share out the chunks as well as the home instance. For example, if you watch the bridge talk @alex gave from poast.tv, you can see on the network tab of the console panel that poast.tv is serving a fraction of the data .

The p2p in the browser only really kicks in for truly viral videos that are being viewed by many people simultaneously. It also works with livestreams since everyone is by nature viewing simultaneously, it doesn't really take any longer for the video to start, but there is noticeable latency with the stream.

poast.tv/w/jUknj6g3BbkESsidKbDRzr