-## Features
-
-- [X] Angular frontend
-- [X] Join the fediverse
- - [X] Follow other instances
- - [X] Unfollow an instance
- - [X] Get for the followers/following list
-- [X] Upload a video
- - [X] Seed the video
- - [X] Send the meta data with ActivityPub to followers
-- [X] Remove the video
-- [X] List the videos
-- [X] View the video in an HTML5 player with WebTorrent
-- [X] Admin panel
-- [X] OpenGraph tags
-- [X] OEmbed
-- [X] Update video
-- [X] Federated videos view counter
-- [X] Federated videos likes/dislikes
-- [X] Transcoding to different definitions
-- [X] Download file/torrent
-- [X] User video bytes quota
-- [X] User video channels
-- [X] NSFW warnings/settings
-- [X] Video description in markdown
-- [X] User roles (administrator, moderator)
-- [X] User registration
-- [X] Video privacy settings (public, unlisted or private)
-- [X] Signaling a video to the admin origin PeerTube instance
-- [X] Federated videos comments
-- [ ] Video imports (URL, Torrent, YouTube...)
-- [ ] Advanced search
-- [ ] Subtitles
-- [ ] User playlist
-- [ ] User subscriptions (by tags, author...)
-- [ ] Add "DDOS" security
-
-
-## Front compatibility
-
- * Firefox
- * Chrome/Chromium
-
-## Dependencies
-
- * nginx
- * PostgreSQL
- * Redis
- * **NodeJS >= 8.x**
- * yarn
- * OpenSSL (cli)
- * FFmpeg
-
-## Run using Docker
-
-You can quickly get a server running using Docker. You need to have [docker](https://www.docker.com/community-edition) and [docker-compose](https://docs.docker.com/compose/install/) installed.
-
-For this example configuration, you should also run a reverse proxy. The example
-Docker Compose file provides example labels for the Traefik load balancer,
-though any HTTP reverse proxy is compatible.
-
-Example for running a peertube server locally:
-
-```bash
-sudo \
- PEERTUBE_HOSTNAME=peertube.lvh.me \
- PEERTUBE_ADMIN_EMAIL=test@example.com \
- PEERTUBE_TRANSCODING_ENABLED=true \
- docker-compose up app
-```
-
-(Get the initial root user password from the program output.)
-
-## Production
-
-See the [production guide](support/doc/production.md).
-
-## Contributing
-
-See the [contributing
-guide](/.github/CONTRIBUTING.md)
-to see how to contribute to PeerTube. Spoiler alert: you don't need to be a
-coder to help!
-
-## API REST documentation
-
-For now only on Github:
-
- * HTML version: [/support/doc/api/html/index.html](/support/doc/api/html/index.html)
- * Swagger/OpenAPI schema: [/support/doc/api/openapi.yaml](/support/doc/api/openapi.yaml)
-
-## Architecture
-
-See [ARCHITECTURE.md](/ARCHITECTURE.md) for a more detailed explanation.
-
-### Backend
-
- * The backend is a REST API.
- * Servers communicate with each others with [Activity
- Pub](https://www.w3.org/TR/activitypub/).
- * Each server has its own users who query it (search videos, query where the
- torrent URI of this specific video is...).
- * If a user uploads a video, the server seeds it and sends its followers some
- metadata (name, short description, torrent URI...).
- * A server is a tracker responsible for all the videos uploaded in it.
- * 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.
-
-Here are some simple schemes: