We welcome you to take part in discussions to <a target="_blank" rel="noopener noreferrer" href="https://github.com/Chocobozzz/PeerTube/issues">help ongoing efforts</a> in that direction or <a target="_blank" rel="noopener noreferrer" href="https://github.com/Chocobozzz/PeerTube/issues/new">suggest new ones</a>!
The web browser generates a random string to identify the viewer during the browser session and periodically notifies the server that a user is watching the video.
We did not go any further to not impose, in the code, a political vision of cultural content funding. It's the reason why we encourage developers to use the <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/contribute-plugins">PeerTube plugin API</a> to create their own monetization system.
By <strong>filtering according to your profile</strong> (video maker or viewer), <strong>topics</strong> that you are looking for or <strong>languages</strong> you speak, <strong>find an instance whose rules match your needs!</strong>
We have a policy for contributions related to security. Please refer to <a target="_blank" rel="noopener noreferrer" href="https://github.com/Chocobozzz/PeerTube/blob/develop/SECURITY.md">SECURITY.md</a>.
Transcoding can also be offloaded to other machines using <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/admin/remote-runners">remote runners</a>.
Video transcoding: can be mitigated using <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/admin/remote-runners">remote transcoding</a> by remote workers
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.
