>Framasoft also announced that next year they will bet big on PeerTube, working on features such as better moderation tools, working on promoting the ecosystem more, and an official PeerTube mobile app.
And on another front of the mobile battle, podcasting 2.0 apps are increasingly supporting PeerTube video via the RSS feed.
It was announced a few days ago at the Capitole du Libre festival in Toulouse, France. Framasoft is hiring a second developer to work on PeerTube (for now it is mostly the work of a single individual), and they will, among other numerous things, work on mobile apps and video/sound decoupling to allow for the podcast usage cited in another comment, for example.
That's the p2n layer that already exists in PeerTube through the redundancy feature in federation.
Federated instances that enable redundancy copy all resolutions of a video that meet chosen criteria of popularity. When a user views the video on PeerTube, their browser grabs the sections of the video from any of the PeerTube instances that have a copy, creating an ad-hoc distributed CDN. This covers the mid-level of popularity and keeps the hosting instance from getting slammed on bandwidth.
If something goes viral, or during livestreams which are by nature simultaneous, then the p2p in the browser between viewers kicks in and reduces load on the peering servers even more.
That's great! And along the lines of what I was hoping might be true. A question though: It sounds like you are saying various instances can help each other on a per-video basis, for videos above a popularity threshold.
But what about the prospects of distributing the load that isn't localized to a particular video? As in, users do some peer to peer load distribution of any and all videos above the threshold, regardless of whether it's the one they are watching?
