Source string Source string

English (United States)
However, on PeerTube each account is linked to one or multiple channels that can be named as the users sees fit. You also have to create at least one channel when creating an account. Once the channels have been created, users can upload videos to each channel to organize their contents (for example, you could have a channel about cooking and another one about biking).
Use external auth (LDAP, OpenID Connect...) using auth plugins
Set the default NSFW policy (hide, blur or display these videos)
Choose your trending algorithm
Broadcast a message to users using a banner
The <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/install-any-os">installation guide is here</a> (only in English).
IPFS is a great technology, but it still seems very (too!) young for large scale streaming of large files.
If you need help, check the <a target="_blank" rel="noopener noreferrer" href="https://joinpeertube.org/help">help page</a>.
Let’s pave the way towards PeerTube's v3!
PeerTube should run happily on a virtual machine with 2 threads/vCPUs, at least 1 Gb of RAM and enough storage for videos. In terms of bandwidth, a lot will depend on which PeerTube instances you federate with and what your relation with them is (more about that below).
If it was easy to embed a PeerTube video on a website or to share it on social media, it wasn't possible to embed playlists. So we worked on their integration on third party websites. It's now very easy to share playlists with the embed code:
It allows you to choose a hoster that fits you. YouTube's excesses are a good example: its hoster, Google/Alphabet, can impose its "Robocopyright" (the ContentID system) or its tools to index, recommend and spotlight videos; and those tools seem as unfair as they are obscure. Even though, it already forces you <a target="_blank" rel="noopener noreferrer" href="https://tosdr.org/#youtube"> to give it extended copyrights on your videos, for free</a>!
As a real life example, the PeerTube demonstration server https://peertube.cpy.re runs on 2 vCores and 2GB of RAM. Average consumption is:
CPU: nginx ~ 2%, peertube ~ 10%, postgres ~ 1%, redis ~ 1%
If you also to contribute to the growing of PeerTube, you can participate in its funding here: <a target="_blank" rel="noopener noreferrer" href="https://soutenir.framasoft.org/en">https://soutenir.framasoft.org/en</a>
If you have any questions, feel free to use our forum: <a target="_blank" rel="noopener noreferrer" href="https://framacolibri.org/c/peertube">https://framacolibri.org/c/peertube</a>
RAM: nginx ~ 1MB, peertube ~ 150MB, postgres ~ 30MB, redis ~ 20MB
Network: ~200GB sent per month (https://framatube.org: ~1.5TB sent per month)
CPU
If you want to support PeerTube, you can <a target="_blank" rel="noreferrer noopener" href="https://soutenir.framasoft.org/en">support Framasoft with a donation</a>, but also by helping others to discover and <a target="_blank" rel="noreferrer noopener" href="https://joinpeertube.org/">learn more about PeerTube</a> and our projects: sharing is caring!
Except for video transcoding, a PeerTube instance is not CPU bound. Neither Nginx, PeerTube itself, PostgreSQL nor Redis require a lot of computing power. If it were only for those, one could easily get by with just one thread/vCPU.
You will hugely benefit from at least a second thread though, because of transcoding. Transcoding is very cpu intensive. It serves two purposes on a PeerTube instance: it ensures all videos can be played optimally in the web interface, and it generates different resolutions for the same video. PeerTube support for offloading transcoding to other machines is <a target="_blank" rel="noopener noreferrer" href="https://github.com/Chocobozzz/PeerTube/issues/947">being discussed</a>, but not yet implemented.
RAM
It's best to contact and talk directly with hosting providers, to understand their business model, vision, etc. Because only you can determine what makes you trust such or such host, and thus entrust your videos to them.
Illustration CC-BY david revoy
It's up to everyone to be responsible: parents, visitors, uploaders, PeerTube administrators to respect the law and avoid any problematic situations.
1/2 GB of RAM should be plenty for a basic PeerTube instance, which usually takes at most 150 MB in RAM. The only reason you might want more would be if you colocate your Redis or PostgreSQL services on a non-SSD system.
Storage
In December 2018, we released version 1.1 which contained some moderation tools requested by instance administrators.
In early August we finalized the work on the moderation tools: accounts and comments reporting, improving the administration and moderation interface, reporting logs, messages between the moderation team and the reporter…
There are two important angles to storage: disk space usage and sustained read speed. To make a rough estimate of your disk space usage requirements, you want to know the answer to three questions:
Its development is community-based, it can be enhanced by everyone's contributions.
In early August, we entered a new stage in <a href="https://joinpeertube.org/roadmap/" target="_blank">the development of PeerTube v3</a>.
What is the total size of the videos you wish to stream?
Do you want to enable transcoding? If so, do you want to provide multiple resolutions per video? Try this out with a few videos and you will get an idea of how much extra space is required per video and estimate a multiplication factor for future space allocation.
In early june, we released PeerTube 2.2 and less than two months later we are releasing this 2.3 version. We are proud to move forward so fast on PeerTube development! As we continue to follow <a target="_blank" href="https://joinpeertube.org/en_US/roadmap">our roadmap</a>, this release incorporates the features we told you about in the latest news. Let's look around and see what it brings us...
Which sharing mechanisms do you want to enable? Just WebTorrent, or also HLS with p2p? If you want both, this will double your storage needs.
In January, we released version 1.2 that supports 3 new languages: Russian, Polish and Italian. Thanks to PeerTube's community of translators, PeerTube is now translated into 16 different languages!
In terms of read speed, you want to make sure that you can saturate your network uplink serving PeerTube videos. This should not be a problem with SSD disks, whereas traditional HDD should be accounted for: typical sustained read rates for a well tuned system with a 7200rpm hard disk should hover around 120 MB/s or 960 Mbit/s. The latter should be enough for a typical 1 Gbit/s network uplink.
In mid-july, we released PeerTube 2.3 and now here is the 2.4 version. This latest release implements features we've already told you about in the last news as we still follow our <a target="_blank" href="https://joinpeertube.org/roadmap">roadmap</a>. Let us present you in details our latest innovations!
Network
In order to make this channel idea more understandable, we have changed the sign-up form, which from now on consists of two steps:
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.
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
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.
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.
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.
No it doesn't. You can't deploy multiple PeerTube nodes behind a load balancer.
As far as we know, there are 3 limitations to handle a large amount of users in PeerTube:
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
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.
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>
More information
"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?"
In the last few months, we have created 2 new plugins:
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

Loading…

User avatar None

New source string

joinpeertube / mainEnglish (United States)

New source string 9 months ago
Browse all component changes

Things to check

Long untranslated

The string has not been translated for a long time

Reset

Glossary

English (United States) English (United States)
No related strings found in the glossary.

String information

Flags
read-only
Source string location
src/views/FAQ.vue:622
String age
9 months ago
Source string age
9 months ago
Translation file
src/locale/en_US/LC_MESSAGES/app.po, string 359