A rough estimate of a traditional server's video streaming network capacity is usually quite straightforward. You simply divide your server's available bandwidth by the average bandwidth per stream, and you have an upper bound.
In other news, we are going to change the moderation policy of the public instances index we maintain on <a href="https://instances.joinpeertube.org/instances">instances.joinpeertube.org</a>. The new moderation terms are stated in the header and will take effect on Monday September, 21.
Take a server for example with a 1 Gbit/s uplink for example pushing out 1080p60 streams at 5 Mbit/s per stream. That means the absolute theoretical upper capacity bound is 200 simultaneous viewers if your server's disk i/o can keep up. Expect a bit less in practice.
Storage: we may implement <a target="_blank" rel="noopener noreferrer" href="https://github.com/Chocobozzz/PeerTube/issues/3661">S3/Object storage</a> in the future
In September 2019 when <a rel="noreferrer noopener" target="_blank" href="https://joinpeertube.org/fr/news#release-1-4-0">PeerTube v.1.4 was released</a>, we announced the creation of a plugin system. This system allows PeerTube instance administrators to create and/or install plugins depending on their specific feature needs, without having to rely on our small non-profit for this creative work.
But what if you need to serve more users? That's where PeerTube's federation feature shines. If other PeerTube instances following yours, chances are they have decided to mirror part of your instance! The feature is called "server redundancy" and caches your most popular videos to help serve additional viewers. While viewers themselves contribute a little additional bandwidth while watching the video in their browsers (mostly during surges), mirroring servers have a much greater uplink and will help your instance with sustained higher concurrent streaming.
In terms of interface, the video report window has been greatly improved by @rigelk. As a reminder, the video reporting feature is accessible if you have an account and are logged in. It is therefore only possible to report videos that you see from the instance where you are registered: either because this video is hosted on your instance, or because your instance is federated to the instance where the video was uploaded.
If you want to store many videos on your PeerTube instance, you may want to store videos externally using <a href="https://docs.joinpeertube.org/admin-remote-storage" target="_blank">Object Storage</a>.
In the <a href="https://framablog.org/2021/01/07/peertube-v3-its-a-live-a-liiiiive/" target="_blank">PeerTube v3 release blogpost</a>, we announced that we wouldn't resort to crowdfunding to finance PeerTube's development in 2021.
Bandwidth: can be mitigated using <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/admin-following-instances?id=instances-redundancy">PeerTube redundancy system</a> and cache servers that serve video static files in front of your PeerTube instance
You're right. PeerTube 1.0 is not the perfect tool, far from it. And we never promised that this version 1.0 would be a tool that would include all the features corresponding to all cases.
In the different tests we've had, we have managed to keep lag between 30s to 1mn. To our knowledge, peer-to-peer live broadcasting will induce an incompressible lag between the streamer and the audience. Ultimately, this lag will depend on the server charge (how many live streams are happening at the same time) and bandwidth.
Storage: can be mitigated using <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/admin-remote-storage">S3/Object storage</a>
"It's outrageous and unconscious: you're releasing a PeerTube version that doesn't contain the necessary tools to effectively manage videos claimed by rights holders, or to effectively manage the issue of online harassment in comments, or to effectively manage monetization through advertising, or to (insert here your request to PeerTube). It will never work! What do you intend to do about it?"
Video transcoding: we may implement <a target="_blank" rel="noopener noreferrer" href="https://github.com/Chocobozzz/PeerTube/issues/947">transcoding by remote workers</a> in the future