English (United States)
English (United States) Japanese
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:
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.
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.
Network ネットワーク
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.
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.
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.
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="">PeerTube redundancy system</a> and cache servers that serve video static files in front of your PeerTube instance
Storage: can be mitigated using <a target="_blank" rel="noopener noreferrer" href="">S3/Object storage</a> PeerTubeの <a target="_blank" rel="noopener noreferrer" href="">プラグインやテーマ</a>を調べ、インストールできます
Video transcoding: we may implement <a target="_blank" rel="noopener noreferrer" href="">transcoding by remote workers</a> in the future
If you notice performance problems or a bottleneck at your scale, don't hesitate to <a target="_blank" rel="noopener noreferrer" href="">create an issue</a> to discuss it.
Framasoft tries to make around 4 major releases per year. Releasing a new PeerTube version takes a lot of our time, so we cannot change this release cycle. Framasoftは一年に約4回のメジャーリリースをするために努力しています。PeerTubeの新バージョンをリリースするには多くの時間がかかるため、このリリースサイクルを変更する事はできません。
There is no LTS version: only the latest stable version of PeerTube is supported by Framasoft. PeerTubeにLTS(ロングタームサポート)バージョンはありません。Framasoftによってサポートされている、最新安定版のみです。
If you want to test the PeerTube develop branch, we provide <a target="_blank" rel="noopener noreferrer" href="">nightly builds</a>. もしPeerTubeの開発ブランチをテストしたい場合、私たちは<a target="_blank" rel="noopener noreferrer" href="">nightlyビルド</a>を配布しています。
We <strong>try</strong> to keep compatibility with the latest minor version (2.3.1 with 2.2 for example). Unfortunately we don't have enough resources to keep compatibility with other versions. 最新のマイナーバージョン間(例えばv2.3.1とv2.2)での互換性を維持するために<strong>努力</strong> してます。しかし残念ながら、他のバージョンとの互換性を維持するための十分な種々のリソースがありません。
"It's outrageous and unconscionable: 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?" 「この点は非常識であるし、道徳的に外れています: あなたたちがリリースしたPeerTubeのバージョンには、権利者から特定の要求をされた動画を効率的に管理するための、またはコメント欄上でのいわゆるオンライン・ハラスメントの問題を効率的に管理するための、または-あなたのPeerTubeへのリクエストをここに-するための、必要なツールがありません。インスタンスの管理が上手くできません!この点について、あなたたちはどうされますか?」
You're right. PeerTube is not the perfect tool, far from it. And we never promised this software would include all the features corresponding to every use cases. あなたは正しい。PeerTubeは完璧なツールではなく、それからは程遠いモノです。そして私たちは、このソフトウェアがそれぞれのユーズケースに妥協して、あらゆる機能を含むことを絶対に約束しません。
Remember that PeerTube has only <a href="#who-is-working-on-peertube">one full time developer</a> and a small handful of very involved volunteers. It is not a product developed by a start-up with a full time team and significant financial support. PeerTubeには<a href="#who-is-working-on-peertube">一人のフルタイムでの開発者</a>と、プロジェクトにとてもよく関わって頂けている、ごく一握りのボランティアのみがいることを思い出してください。PeerTubeはフルタイムでの開発者チームとかなりの財政的なサポートがある、スタートアップ企業によって開発された商品ではありません。
So if you feel that PeerTube does not currently meet your needs, it's simple: don't use it right now. We remind you that we don't make money developing PeerTube, and if we obviously hope for its success, Framasoft does not depend on it to continue its activities. よって、もしPeerTubeが現在のあなたのニーズにあっていないと感じるなら、シンプルに言います: 今は、PeerTubeを利用しないでください。私たちはPeerTubeを開発することによってお金を稼いではいない、ということを気づかせるとともに、仮にこのソフトウェアの成功を明らかに望んだとしても、Framasoftは非営利団体としての活動を継続するために、PeerTubeには依存しません。
<a href="#what-are-the-peertube-features-for-administrators">Yes it does!</a> Since the first stable release of PeerTube in October 2018, <strong>every release</strong> added or improved moderation features: <a href="#what-are-the-peertube-features-for-administrators">はい、あります!</a>2018年10月の最初のPeerTube安定版リリース以降、<strong>新しいリリースごと</strong>にモデレーション機能が加えられる、または改善されています:
<strong>PeerTube 1.1</strong> added bulk actions in the admin users table and instance/account muting;
<strong>PeerTube 1.2</strong> added the ability to unfederate a video on blacklist; the notification system now shows reports, and new users;
<strong>PeerTube 1.3</strong> added the possibility for admins to automatically quarantine new videos for new/untrusted users until a moderator reviews it. The instance's followers management was also reworked: UI is improved, follows can be denied;
<strong>PeerTube 1.4</strong> added a plugin system, and made sure plugins can for instance automatically blacklist videos or reject comments based on any rule (similar to Pleroma MRF);
<strong>PeerTube 2.0</strong> setup now asks the admin to answer questions regarding their moderation policy and dedication to it. Make a feature to automatically follow a public index of PeerTube instances part of core PeerTube, instead of leaving admins to script it themselves. This allows instance administrators to automatically follow instances of a "follow list" of their choice; a list which is self-hostable, so that communities can grow at their own pace;
<strong>PeerTube 2.1</strong> added an <em>internal</em> privacy mode to videos (such videos won't be shared outside of the instance), and added quick access to moderation tools below the comments and hooks to create registration plugins (geoblocking or captchas for example); some third-party plugins already demonstrate this ability. This release also put emphasis on describing moderation features within the interface: warnings for features that might increase moderation work like autofollow, and descriptions to the action dropdowns.
<strong>PeerTube 2.2</strong> greatly improved video abuses management (search, abuses display, actions on the video or account etc), added moderation hooks and helpers in the plugins API and Framasoft developed an experimental <em>Auto mute</em> plugin based on public lists.


User avatar 4ioskd

New translation

joinpeertube / mainJapanese

7 months ago
Browse all component changes


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

String information

Source string location
String age
9 months ago
Source string age
9 months ago
Translation file
src/locale/ja/LC_MESSAGES/app.po, string 380