Source string Source string

English (United States) Actions
Enable video import using youtube-dl (Youtube, Dailymotion...)
Here is another step in the <a href="" target="_blank">PeerTube roadmap</a> leading to v3! June has been dedicated to implement a system to enable global video search across PeerTube instances. Thank you all for being so many in funding this solution! This allows us to be free minded for the next few weeks to work on moderation tools.
Hi everybody,
We are well aware of the shortcomings of PeerTube 1.0, especially in the moderation tools area (videos, comments, etc.). And we intend to work on these weaknesses.
Enable video import using webtorrent (torrent file or magnet URI)
Enable signups and set a max users and upload limits
Assign <a target="_blank" rel="noopener noreferrer" href="">moderator/admin</a> roles
Manage abuse reports on videos, accounts or comments using a dedicated dashboard
Automatically block videos from untrusted users awaiting a review by moderators
Indeed, we do not claim to have the science behind it and know how best to manage each of the tools according to each of the needs. For example: with regard to the question of DMCA requests, cases vary according to geographical jurisdictions (European law is different from French law, itself different from Canadian law, itself different from American law, etc.). Concerning the tools for moderating comments, here again, we cannot decree ourselves experts of the subject, because this is simply not the case.
Block specific videos and specify a reason
Enable signup and set a max users and upload limits
Ban local users, mute accounts or instances
Let's pave the way to PeerTube live streaming in the v3!
Highly configurable
Easily set instance metadata: name, description, main categories...
Search and install PeerTube <a target="_blank" rel="noopener noreferrer" href="">plugins or themes</a>
Use external auth (LDAP, OpenID Connect...) using auth plugins
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).
Set the default NSFW policy (hide, blur or display these videos)
Choose your trending algorithm
Create your own homepage using markdown or HTML
Broadcast a message to users using a banner
IPFS is a great technology, but it still seems very (too!) young for large scale streaming of large files.
The <a target="_blank" rel="noopener noreferrer" href="">installation guide is here</a> (only in English).
Let’s pave the way towards PeerTube's v3!
If you need help, check the <a target="_blank" rel="noopener noreferrer" href="">help page</a>.
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:
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).
Choose default user settings (NSFW policy, comments/download/P2P enabled, etc)
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=""> to give it extended copyrights on your videos, for free</a>!
Store videos in the server filesystem of in object storage
As a real life example, the PeerTube demonstration server runs on 2 vCores and 2GB of RAM. Average consumption is:
If you also to contribute to the growing of PeerTube, you can participate in its funding here: <a target="_blank" rel="noopener noreferrer" href=""></a>
CPU: nginx ~ 2%, peertube ~ 10%, postgres ~ 1%, redis ~ 1%
RAM: nginx ~ 1MB, peertube ~ 150MB, postgres ~ 30MB, redis ~ 20MB
If you have any questions, feel free to use our forum: <a target="_blank" rel="noopener noreferrer" href=""></a>
Network: ~200GB sent per month ( ~1.5TB sent per month)
If you want to support PeerTube, you can <a target="_blank" rel="noreferrer noopener" href="">support Framasoft with a donation</a>, but also by helping others to discover and <a target="_blank" rel="noreferrer noopener" href="">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="">being discussed</a>, but not yet implemented.
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
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.
It's up to everyone to be responsible: parents, visitors, uploaders, PeerTube administrators to respect the law and avoid any problematic situations.
In December 2018, we released version 1.1 which contained some moderation tools requested by instance administrators.
Its development is community-based, it can be enhanced by everyone's contributions.
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:
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…
What is the total size of the videos you wish to stream?
In early August, we entered a new stage in <a href="" target="_blank">the development of PeerTube v3</a>.
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="">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...
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.


User avatar None

New source string

joinpeertube / mainEnglish (United States)

New source string a year ago
Browse all component changes

Things to check

Multiple failing checks

Following checks are failing:
Mismatched semicolon: Portuguese (Portugal), Portuguese (Portugal), Greek, Arabic, Arabic, Korean, Korean, Lithuanian, Lithuanian, Chinese (Traditional), Chinese (Traditional), Sardinian, Sardinian, Thai, Chinese (Simplified), Chinese (Simplified), Catalan, Catalan, Hungarian, Hungarian



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

String information

Source string location
String age
a year ago
Source string age
a year ago
Translation file
src/locale/en_US/LC_MESSAGES/app.po, string 348