From c7cb3c4b23719a90bcc0f22a077baa7fd72ffca5 Mon Sep 17 00:00:00 2001
From: Cas <6506529+ThaUnknown@users.noreply.github.com>
Date: Tue, 15 Mar 2022 18:41:05 +0100
Subject: [PATCH] Update README.md

---
 README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index c082e46..d8d52ed 100644
--- a/README.md
+++ b/README.md
@@ -1,5 +1,7 @@
 # Miru
 
+Discord link: https://discord.gg/Z87Nh7c4Ac
+
 Originally a joke project, turned out to be semi-viable.
 
 A pure JS BitTorrent streaming environment, with a built-in list manager. Imagine qBit + Taiga + MPV, all in a single package, but streamed real-time.
@@ -13,4 +15,4 @@ Electron has node.js integration, which can use TCP/UDP, that is the only reason
 Yes. A BitTorrent implementation which uses WebRTC exists, but it's not yet adopted by any clients, and libtorrent [the library which qBit and others use] is still working/just added support for WebRTC, which means there's no swarm. This will hopefully change in the future.
 
 ## Where codec support?
-This uses the browser's built in video player, which uses a cut down version of FFMPEG, which lacks a support for a LOT of containers and codecs because of licensing. Since Electron is just Chromium IN THEORY it is possible to re-compile FFMPEG with support for more containers and codecs, but people seem to be going out of their way to make sure you can't find how to do that. PR pls?
\ No newline at end of file
+This uses the browser's built in video player, which uses a cut down version of FFMPEG, which lacks a support for a LOT of containers and codecs because of licensing. Since Electron is just Chromium IN THEORY it is possible to re-compile FFMPEG with support for more containers and codecs, but people seem to be going out of their way to make sure you can't find how to do that. PR pls?