aboutsummaryrefslogtreecommitdiffhomepage
path: root/README.md
diff options
context:
space:
mode:
authorChocobozzz <florian.bigard@gmail.com>2017-10-31 16:11:38 +0100
committerChocobozzz <florian.bigard@gmail.com>2017-10-31 16:11:38 +0100
commit604e02abcba0a50be23f243db30eca94b68cd35f (patch)
treee3ddecb2752912351fc520a09ab18a3406d32ad2 /README.md
parent11474c3cd904fa0fc07fc0a3a9a35496da17f300 (diff)
downloadPeerTube-604e02abcba0a50be23f243db30eca94b68cd35f.tar.gz
PeerTube-604e02abcba0a50be23f243db30eca94b68cd35f.tar.zst
PeerTube-604e02abcba0a50be23f243db30eca94b68cd35f.zip
Update PeerTube features
Diffstat (limited to 'README.md')
-rw-r--r--README.md25
1 files changed, 17 insertions, 8 deletions
diff --git a/README.md b/README.md
index 8248e3a7c..78dbbc613 100644
--- a/README.md
+++ b/README.md
@@ -100,14 +100,23 @@ Thanks to [WebTorrent](https://github.com/feross/webtorrent), we can make P2P (t
100 - [X] Friends list 100 - [X] Friends list
101 - [X] Manage users (create/remove) 101 - [X] Manage users (create/remove)
102- [X] OpenGraph tags 102- [X] OpenGraph tags
103- [X] OEmbed
103- [X] Update video 104- [X] Update video
104- [X] Videos view count 105- [X] Videos view counter
105- [X] Videos likes/dislikes 106- [X] Videos likes/dislikes
106- [ ] Videos comments? 107- [X] Transcoding to different definitions
108- [X] Download file/torrent
109- [X] User video bytes quota
110- [X] User channels
111- [X] NSFW warnings/settings
112- [X] Video description in markdown
113- [X] User roles (administrator, moderator)
107- [X] User registration 114- [X] User registration
108- [ ] User playlists 115- [X] Video privacy settings (public, unlisted or private)
109- [ ] User subscriptions (by tags, author...)
110- [X] Signaling a video to the admin origin pod 116- [X] Signaling a video to the admin origin pod
117- [ ] Videos comments
118- [ ] User playlist
119- [ ] User subscriptions (by tags, author...)
111 120
112 121
113## Installation 122## Installation
@@ -239,13 +248,13 @@ See [ARCHITECTURE.md](https://github.com/Chocobozzz/PeerTube/blob/master/ARCHITE
239 * Each server of a network has a list of all other servers of this network 248 * Each server of a network has a list of all other servers of this network
240 * When a new installed server wants to join a network, it just has to get the servers list through a server that is already in the network and tell "Hi I'm new in the network, communicate with me and share me your servers list please". Then the server will "make friend" with each server of this list 249 * When a new installed server wants to join a network, it just has to get the servers list through a server that is already in the network and tell "Hi I'm new in the network, communicate with me and share me your servers list please". Then the server will "make friend" with each server of this list
241 * Each server has its own users who query it (search videos, where the torrent URI of this specific video is...) 250 * Each server has its own users who query it (search videos, where the torrent URI of this specific video is...)
242 * If a user upload a video, the server seeds it and sends the video informations (name, short description, torrent URI...) to each server of the network 251 * If a user upload a video, the server seeds it and sends the video information (name, short description, torrent URI...) to each server of the network
243 * Each server has a RSA key to encrypt and sign communications with other servers 252 * Each server has a RSA key to encrypt and sign communications with other servers
244 * A server is a tracker responsible for all the videos uploaded in it 253 * A server is a tracker responsible for all the videos uploaded in it
245 * Even if nobody watches a video, it is seeded by the server (throught [WebSeed protocol](http://www.bittorrent.org/beps/bep_0019.html)) where the video was uploaded 254 * Even if nobody watches a video, it is seeded by the server (through [WebSeed protocol](http://www.bittorrent.org/beps/bep_0019.html)) where the video was uploaded
246 * A network can live and evolve by expelling bad pod (with too many downtimes for example) 255 * A network can live and evolve by expelling bad pod (with too many downtime for example)
247 256
248See the ARCHITECTURE.md for more informations. Do not hesitate to give your opinion :) 257See the ARCHITECTURE.md for more information. Do not hesitate to give your opinion :)
249 258
250Here are some simple schemes: 259Here are some simple schemes:
251 260