diff --git a/guide/matrix-vs-discord.md b/guide/matrix-vs-discord.md
index aef8d5ae..3ebfcbf9 100644
--- a/guide/matrix-vs-discord.md
+++ b/guide/matrix-vs-discord.md
@@ -100,7 +100,7 @@ Matrix has a handful server implementations and about a dozen general purpose cl
 | **Direct messages** | Not encrypted. | **Encrypted by default**, including VoIP. | Not encrypted. End-to-end encryption support planned. |
 | Starting a DM | Depending on privacy settings, initiating a DM requires the two users to have established "friendship" or have certain mutual "servers." Users are given the choice to accept, remove, or report a DM (since late 2021). | Initiating a DM solely requires the recipient to accept the request[^2]. Users can leave DMs anytime they wish. |
 | **Group chats** | A group chat channel is associated with a "server." You can only join 100 "servers," 200 with Nitro. Additionally, there are group chats not associated with servers, called group DMs, with far more limited features than servers can. | A room is standalone, but can be optionally included and associated with a Space, which is just a room linking to other rooms. You can join **unlimited** amount of rooms (in theory). | Same as Discord. |
-| VoIP in groups | Supported. End to end encrypted VoIP support planned. | Supported. The room plays the role of signalling, audiovisual data is sadly routed through a separate WebRTC channel. End to end encryption supported. | Supported. End to end encryption planned. |
+| VoIP in groups | Supported. End to end encrypted VoIP support using MLS implemented, albeit with a huge security issue: [the session is silently downgraded if there is a non-E2EE-capable client](https://github.com/discord/discord-api-docs/issues/6574). | Supported. The room plays the role of signalling, audiovisual data is sadly routed through a separate WebRTC channel. End to end encryption supported. | Supported. End to end encryption using MLS planned. |
 | Organizing chats | "Servers" can be organized into folders, but each "server" can only belong to 1 folder. Channels in a "server" can only be organized by the "server" owner and moderators with "manage channels" permission, in a many to one fashion, and cannot be moved to another "server" once created. | Rooms can be included within an unlimited amount of Spaces. Spaces may also include other Spaces (similar to Discord's channel categories). | Same as Discord. |
 | Group chat privacy | Denying "View Channel History" permission prevents users from reading messages prior to their most recent login. However the "server" owners cannot enjoy that privacy, as "server" owners cannot deny their own permissions due to how Discord's permission system works. | You may deny new members from reading messages prior to them being invited / joining. You may also allow or deny guest access (such as [Matrix Static](http://view.matrix.org/)) from reading messages. You may also enable encryption[^3]. | Same as Discord. |
 | Server-side deletion guarantees | Messages that are removed from Discord are garbage collected from discord.com databases within less than 2 days.[^8]  Guild messages from deleted users are mapped to the unified ghost user, including mentions to them. Direct messages stay unless explicitly closed by the counterparty. | As Matrix follows an event chain model, there is no true deletion. The closest thing available is redaction, which instructs the users and servers to blank the content but not the metadata of the event. Redactions are best-effort[^12]. | Depends on the instance. |