Zen

Chaîne source Chaîne source

172/10000 · 172

La chaîne est en lecture seule.

Anglais (États-Unis) Actions
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...
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.
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 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 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 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:
Releasing a new PeerTube version takes a lot of our time, so we cannot change this release cycle.
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
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.
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>.
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:
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
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.
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.
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
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
"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?"
Sensitive content blurred
If you notice performance problems or a bottleneck at your scale, don't hesitate to <a target="_blank" rel="noopener noreferrer" href="https://github.com/Chocobozzz/PeerTube/issues/new/choose">create an issue</a> to discuss it.
In the meantime, if you try and test <a href="https://github.com/Chocobozzz/PeerTube/releases/tag/v3.0.0-rc.1">Peertube v3 RC</a> and its live feature, please be sure to give us some feedback on the code respository issues or <a href="https://framacolibri.org/c/peertube/38">on our forum</a>.

Chargement…

Avatar de l’utilisateur Aucun

Chaîne source ajoutée
Sepia can also help you to search PeerTube content like videos or channels on <a target="_blank" rel="noopener noreferrer" href="https://sepiasearch.org/">Sepia Search</a>!
Il y a un an
Parcourir toutes les modifications de chaînes

Points à vérifier

Plusieurs vérifications en échec

Les contrôles suivants sont défaillants :
Incohérence de point d’exclamation: Anglais (Shavien), Anglais (Shavien), Turc, Turc, Azéri, Coréen, Coréen, Hébreu, Grec, Portugais (Portugal), Portugais (Portugal), Chinois (sinogrammes simplifiés), Chinois (sinogrammes simplifiés), Vietnamien, Thaï, Thaï, Sarde, Sarde, Russe, Russe, Polonais, Polonais, Lituanien, Lituanien, Kabyle, Kabyle, Italien, Italien, Hongrois, Hongrois, Persan, Persan, Espéranto, Espéranto, Catalan, Catalan, Serbe, Serbe, Bulgare, Bulgare

Réinitialiser

Glossaire

Anglais (États-Unis) Anglais (États-Unis)
Aucune chaîne correspondante n’a été trouvée dans le glossaire.

Informations sur la chaîne

Drapeaux
read-only
Emplacement de la chaîne source
src/components/faq/common/FAQSepiaName.vue:19 • src/components/faq/common/FAQSepiaName.vue:20
Âge de la chaîne
Il y a un an
Date de dernière mise à jour
Il y a un an
Âge de la chaîne source
Il y a un an
Fichier de traduction
src/locale/en_US/LC_MESSAGES/app.po, chaîne 378