diff --git a/docs/activities/building-an-activity.mdx b/docs/activities/building-an-activity.mdx index 364d6002a5..81705ce0e1 100644 --- a/docs/activities/building-an-activity.mdx +++ b/docs/activities/building-an-activity.mdx @@ -112,7 +112,9 @@ With our project set up, let's create our app and configure the Activity. Create Enter a name for your app, select a development team, then press **Create**. :::info -**Development Team Access**
Launching a non-distributed Activity is limited to you or members of the developer team, so if you're collaborating with others during development, create a [developer team](https://discord.com/developers/teams) and set it to the owner when you create the app. +**Development Team Access** + +Launching a non-distributed Activity is limited to you or members of the developer team, so if you're collaborating with others during development, create a [developer team](https://discord.com/developers/teams) and set it to the owner when you create the app. ::: After you create your app, you'll land on the **General Overview** page of the app's settings, where you can update basic information about your app like its description and icon. @@ -160,7 +162,9 @@ cp example.env .env ``` :::warn -**Secure Your Secrets**
Your `DISCORD_CLIENT_SECRET` and `DISCORD_BOT_TOKEN` are *highly* sensitive secrets. Never share either secrets or check them into any kind of version control. +**Secure Your Secrets** + +Your `DISCORD_CLIENT_SECRET` and `DISCORD_BOT_TOKEN` are *highly* sensitive secrets. Never share either secrets or check them into any kind of version control. ::: Back in your app's settings, click on **OAuth2** on the sidebar: @@ -168,7 +172,9 @@ Back in your app's settings, click on **OAuth2** on the sidebar: 2. **Client Secret**: Copy the value for Client Secret and add it to your `.env` as **`DISCORD_CLIENT_SECRET`**. This is a private, sensitive identifier that your app will use to grant an OAuth2 `access_token`, and should never be shared or checked into version control. :::info -**Why is there a VITE_ prefix before our Client ID?**
Prefixing the `CLIENT_ID` environment variable with `VITE_` makes it accessible to our client-side code. This security measure ensures that only the variables you intend to be accessible in the browser are available, and all other environment variables remain private. You can read details in the [Vite documentation](https://vitejs.dev/guide/env-and-mode). +**Why is there a VITE_ prefix before our Client ID?** + +Prefixing the `CLIENT_ID` environment variable with `VITE_` makes it accessible to our client-side code. This security measure ensures that only the variables you intend to be accessible in the browser are available, and all other environment variables remain private. You can read details in the [Vite documentation](https://vitejs.dev/guide/env-and-mode). ::: @@ -239,7 +245,9 @@ document.querySelector('#app').innerHTML = ` :::warn -**Time to leave your browser behind**
Once you add the SDK to your app, you will **not** be able to view your app inside your web browser. In the next step, we will run your Activity inside of Discord. In the next step, we will go over how to view your app in Discord. +**Time to leave your browser behind** + +Once you add the SDK to your app, you will **not** be able to view your app inside your web browser. In the next step, we will run your Activity inside of Discord. In the next step, we will go over how to view your app in Discord. ::: @@ -336,7 +344,9 @@ Clicking on your app will launch your locally running app from inside Discord! ![Running your activity](images/activities/start-activity.png) :::info -**Customizing your Activity**
If you'd like to set images for your Activity, you can learn how to do that [here](/docs/activities/development-guides#setting-up-activity-metadata). +**Customizing your Activity** + +If you'd like to set images for your Activity, you can learn how to do that [here](/docs/activities/development-guides#setting-up-activity-metadata). ::: We're looking pretty good so far, but we haven't wired up any Discord functionality yet. Let's do that next. diff --git a/docs/developer-tools/embedded-app-sdk.mdx b/docs/developer-tools/embedded-app-sdk.mdx index afde3d6a37..0535683607 100644 --- a/docs/developer-tools/embedded-app-sdk.mdx +++ b/docs/developer-tools/embedded-app-sdk.mdx @@ -1057,7 +1057,7 @@ No scopes required ### ENTITLEMENT_CREATE :::preview - Coming soon! Not available during Developer Preview +Coming soon! Not available during Developer Preview ::: ## SDK Interfaces diff --git a/docs/developer-tools/game-sdk.mdx b/docs/developer-tools/game-sdk.mdx index 531d799982..f3baab355d 100644 --- a/docs/developer-tools/game-sdk.mdx +++ b/docs/developer-tools/game-sdk.mdx @@ -3,7 +3,11 @@ # Game SDK :::warn -**The Game SDK has been archived.**
We recommend using the [Discord Social SDK](/docs/discord-social-sdk/overview) for new projects.
Existing projects using the Game SDK will continue to work, but we encourage you to migrate to the [Discord Social SDK](/docs/discord-social-sdk/overview) for new features and updates. +**The Game SDK has been archived.** + +We recommend using the [Discord Social SDK](/docs/discord-social-sdk/overview) for new projects. + +Existing projects using the Game SDK will continue to work, but we encourage you to migrate to the [Discord Social SDK](/docs/discord-social-sdk/overview) for new features and updates. ::: Welcome to the documentation for the Discord Game SDK! We're glad you made it. The Game SDK helps you develop your 3rd party game or app, and integrate it with Discord. diff --git a/docs/discord-social-sdk/core-concepts.mdx b/docs/discord-social-sdk/core-concepts.mdx index 86c2f9e550..020ab8840b 100644 --- a/docs/discord-social-sdk/core-concepts.mdx +++ b/docs/discord-social-sdk/core-concepts.mdx @@ -48,7 +48,7 @@ The following features are only fully unlocked when joining the closed beta: While these limited access features are available in the Discord Social SDK, their usage is capped with a rate limit. Please read our [documentation on rate limits](/docs/topics/rate-limits) to learn more. :::preview - To apply for full access to closed beta features or to reach out to Discord directly to discuss your game, please fill out [this form](https://discord.com/developers/social-sdk-closed-beta-access-request-form). +To apply for full access to closed beta features or to reach out to Discord directly to discuss your game, please fill out [this form](https://discord.com/developers/social-sdk-closed-beta-access-request-form). ::: --- @@ -215,7 +215,7 @@ Some SDK features are currently available but have limited access. Those feature - `sdk.social_layer` :::preview - For more information about these features, please see [Core Concepts: Limited Access Features](/docs/discord-social-sdk/core-concepts#limited-access-features). +For more information about these features, please see [Core Concepts: Limited Access Features](/docs/discord-social-sdk/core-concepts#limited-access-features). ::: The Social SDK provides two helper methods that you can use when setting up your OAuth2 flow: diff --git a/docs/discord-social-sdk/getting-started/using-c++.mdx b/docs/discord-social-sdk/getting-started/using-c++.mdx index 9cdcd8c843..f737023348 100644 --- a/docs/discord-social-sdk/getting-started/using-c++.mdx +++ b/docs/discord-social-sdk/getting-started/using-c++.mdx @@ -296,8 +296,7 @@ Most Discord features won't work until the status is [`Client::Status::Ready`]. - The **status callback** tells you when you're connected and ready to use Discord features :::info -At this point, these callbacks **won't get called** since the client setup is not yet complete. However, very soon we -will be using them to view debug information and see what our connection status is! +At this point, these callbacks **won't get called** since the client setup is not yet complete. However, very soon we will be using them to view debug information and see what our connection status is! ::: To get to a [`Client::Status::Ready`] state, we need to authenticate with Discord. We'll do that shortly. diff --git a/docs/discord-social-sdk/overview.mdx b/docs/discord-social-sdk/overview.mdx index 1abaff40b4..6b376f9b85 100644 --- a/docs/discord-social-sdk/overview.mdx +++ b/docs/discord-social-sdk/overview.mdx @@ -43,7 +43,7 @@ Start integrating the SDK into your game with our getting started guides, design Discord Social SDK features for text and voice communication are available but have limited access. :::preview - For more information on how to access these features, please see [Core Concepts: Limited Access Features](/docs/discord-social-sdk/core-concepts#limited-access-features). +For more information on how to access these features, please see [Core Concepts: Limited Access Features](/docs/discord-social-sdk/core-concepts#limited-access-features). ::: --- diff --git a/docs/discord-social-sdk/partials/callouts/limited-access.mdx b/docs/discord-social-sdk/partials/callouts/limited-access.mdx index 49edead8e4..5d08228a0b 100644 --- a/docs/discord-social-sdk/partials/callouts/limited-access.mdx +++ b/docs/discord-social-sdk/partials/callouts/limited-access.mdx @@ -1,3 +1,3 @@ :::preview - This feature is currently available with [limited access](/docs/discord-social-sdk/core-concepts#limited-access-features). To apply for full access to closed beta features, or to reach out to Discord directly to discuss your game, please fill out [this form](https://discord.com/developers/social-sdk-closed-beta-access-request-form). +This feature is currently available with [limited access](/docs/discord-social-sdk/core-concepts#limited-access-features). To apply for full access to closed beta features, or to reach out to Discord directly to discuss your game, please fill out [this form](https://discord.com/developers/social-sdk-closed-beta-access-request-form). ::: \ No newline at end of file diff --git a/docs/interactions/application-commands.mdx b/docs/interactions/application-commands.mdx index 4edb16cec7..8df90d591e 100644 --- a/docs/interactions/application-commands.mdx +++ b/docs/interactions/application-commands.mdx @@ -428,7 +428,7 @@ Slash commands—the `CHAT_INPUT` type—are a type of application command. They Slash commands can also have groups and subcommands to further organize commands. More on those later. :::warn -Slash commands can have a maximum of 8000 characters for combined name, description, and value properties for each command, its options (including subcommands and groups), and choices. When [localization fields](/docs/interactions/application-commands#localization) are present, only the longest localization for each field (including the default value) is counted towards the size limit. +Slash commands can have a maximum of 8000 characters for combined name, description, and value properties for each command, its options (including subcommands and groups), and choices. When [localization fields](/docs/interactions/application-commands#localization) are present, only the longest localization for each field (including the default value) is counted towards the size limit. ::: @@ -1096,7 +1096,7 @@ An application command furnished with localizations might look like this: For application commands, there are built-in fallbacks in case a user's locale isn't present in the localizations. If the fallback locale is also missing, it will use the default. :::warn -You should make sure to include your default value in its proper locale key, otherwise it may use a fallback value unexpectedly. For example, if your default value is `en-US`, but you don't specify the `en-US` value in your localizations, users with `en-US` selected will see the `en-GB` value if it's specified. For example, if you have a command with the default name "color", and your localizations specify only the `en-GB` value as "colour", users in the `en-US` locale will see "colour" because the `en-US` key is missing. +You should make sure to include your default value in its proper locale key, otherwise it may use a fallback value unexpectedly. For example, if your default value is `en-US`, but you don't specify the `en-US` value in your localizations, users with `en-US` selected will see the `en-GB` value if it's specified. For example, if you have a command with the default name "color", and your localizations specify only the `en-GB` value as "colour", users in the `en-US` locale will see "colour" because the `en-US` key is missing. ::: | Locale | Fallback | diff --git a/docs/monetization/managing-skus.mdx b/docs/monetization/managing-skus.mdx index 4100eb6a62..b8450370c6 100644 --- a/docs/monetization/managing-skus.mdx +++ b/docs/monetization/managing-skus.mdx @@ -67,8 +67,10 @@ Subscription SKUs are automatically charged each month unless canceled. Changing To set an icon using a standard Unicode emoji, enter the emoji in the `Unicode Emoji or Custom Emoji Name` field. :::info -Using an emoji keyboard can make it easier to pick an icon to display alongside your SKU benefit. -MacOS: `control + command + space bar` +Using an emoji keyboard can make it easier to pick an icon to display alongside your SKU benefit. + +MacOS: `control + command + space bar` + Windows: `Windows + .` ::: diff --git a/docs/reference.mdx b/docs/reference.mdx index 3176ab3b5a..683f403f57 100644 --- a/docs/reference.mdx +++ b/docs/reference.mdx @@ -415,7 +415,7 @@ The `attachments` JSON parameter includes all files that will be appended to the ###### Example Request Bodies (multipart/form-data) -Note that these examples are small sections of an HTTP request to demonstrate behaviour of this endpoint - client libraries will set their own form boundaries (`boundary` is just an example). For more information, refer to the [multipart/form-data spec](https://tools.ietf.org/html/rfc7578#section-4). +Note that these examples are small sections of an HTTP request to demonstrate behavior of this endpoint - client libraries will set their own form boundaries (`boundary` is just an example). For more information, refer to the [multipart/form-data spec](https://tools.ietf.org/html/rfc7578#section-4). This example demonstrates usage of the endpoint *without* `payload_json`. diff --git a/docs/resources/emoji.md b/docs/resources/emoji.md index c8823024d9..22f7d177e4 100644 --- a/docs/resources/emoji.md +++ b/docs/resources/emoji.md @@ -68,11 +68,13 @@ The `user` field of an app emoji object represents the team member that uploaded ###### Custom Emoji Examples ->info ->In `MESSAGE_REACTION_ADD`, `MESSAGE_REACTION_REMOVE` and `MESSAGE_REACTION_REMOVE_EMOJI` gateway events `animated` will be returned for animated emoji. +:::info +In `MESSAGE_REACTION_ADD`, `MESSAGE_REACTION_REMOVE` and `MESSAGE_REACTION_REMOVE_EMOJI` gateway events `animated` will be returned for animated emoji. +::: ->info ->In `MESSAGE_REACTION_ADD` and `MESSAGE_REACTION_REMOVE` gateway events `name` may be `null` when custom emoji data is not available (for example, if it was deleted from the guild). +:::info +In `MESSAGE_REACTION_ADD` and `MESSAGE_REACTION_REMOVE` gateway events `name` may be `null` when custom emoji data is not available (for example, if it was deleted from the guild). +::: ```json { diff --git a/docs/resources/message.md b/docs/resources/message.md index 5aaba09743..cec22bb11e 100644 --- a/docs/resources/message.md +++ b/docs/resources/message.md @@ -70,7 +70,7 @@ An app will receive empty values in the `content`, `embeds`, `attachments`, and ###### Message Types :::warn -Type `19` and `20` are only available in API v8 and above. In v6, they are represented as type `0`. Additionally, type `21` is only available in API v9 and above. +Type `19` and `20` are only available in API v8 and above. In v6, they are represented as type `0`. Additionally, type `21` is only available in API v9 and above. ::: | Type | Value | Deletable | @@ -313,7 +313,7 @@ Information about the call in a private channel. | guild_id? | snowflake | id of the originating message's guild | | fail_if_not_exists? | boolean | when sending, whether to error if the referenced message doesn't exist instead of sending as a normal (non-reply) message, default true | -\* If `type` is unset, `DEFAULT` can be assumed in order to match the behaviour before message reference had types. +\* If `type` is unset, `DEFAULT` can be assumed in order to match the behavior before message reference had types. In future API versions this will become a required field. \*\* `channel_id` is optional when creating a reply, but will always be present when receiving an event/response that includes this data model. **Required for forwards.** diff --git a/docs/rich-presence/overview.mdx b/docs/rich-presence/overview.mdx index bc9956d303..a7a5faeee8 100644 --- a/docs/rich-presence/overview.mdx +++ b/docs/rich-presence/overview.mdx @@ -43,7 +43,11 @@ After a user joins an Activity, Rich Presence can be used to dynamically show da ### Game SDK :::warn -**The Game SDK has been archived.**
We recommend using the [Discord Social SDK](/docs/discord-social-sdk/overview) for new projects.
Existing projects using the Game SDK will continue to work, but we encourage you to migrate to the [Discord Social SDK](/docs/discord-social-sdk/overview) for new features and updates. +**The Game SDK has been archived.** + +We recommend using the [Discord Social SDK](/docs/discord-social-sdk/overview) for new projects. + +Existing projects using the Game SDK will continue to work, but we encourage you to migrate to the [Discord Social SDK](/docs/discord-social-sdk/overview) for new features and updates. ::: The [Game SDK](/docs/developer-tools/game-sdk) makes it easier to build 3rd party games and integrate them with Discord. While many features of the Game SDK are deprecated, it can still be used for a few use cases (like integrating Rich Presence!). diff --git a/docs/rich-presence/using-with-the-game-sdk.mdx b/docs/rich-presence/using-with-the-game-sdk.mdx index 336bd12878..d83b1b1256 100644 --- a/docs/rich-presence/using-with-the-game-sdk.mdx +++ b/docs/rich-presence/using-with-the-game-sdk.mdx @@ -5,7 +5,11 @@ sidebar_label: Using with the Game SDK # Using Rich Presence with the Game SDK :::warn -**The Game SDK has been archived.**
We recommend using the [Discord Social SDK](/docs/discord-social-sdk/overview) for new projects.
Existing projects using the Game SDK will continue to work, but we encourage you to migrate to the [Discord Social SDK](/docs/discord-social-sdk/overview) for new features and updates. +**The Game SDK has been archived.** + +We recommend using the [Discord Social SDK](/docs/discord-social-sdk/overview) for new projects. + +Existing projects using the Game SDK will continue to work, but we encourage you to migrate to the [Discord Social SDK](/docs/discord-social-sdk/overview) for new features and updates. ::: The [Game SDK](/docs/developer-tools/game-sdk) helps you build 3rd party games and integrate them with Discord. One of its specialties is making it easy to bring your game's data to Discord using [Rich Presence](/docs/rich-presence/overview), which this guide will cover. diff --git a/docs/topics/oauth2.md b/docs/topics/oauth2.md index 6e0d78718c..ce8bc0eae3 100644 --- a/docs/topics/oauth2.md +++ b/docs/topics/oauth2.md @@ -54,8 +54,7 @@ These are a list of all the OAuth2 scopes that Discord supports. Some scopes req | webhook.incoming | this generates a webhook that is returned in the oauth token response for authorization code grants | :::info -In order to add a user to a guild, your bot has to already belong to that guild. -`role_connections.write` cannot be used with the [Implicit grant type](/docs/topics/oauth2#implicit-grant). +In order to add a user to a guild, your bot has to already belong to that guild. `role_connections.write` cannot be used with the [Implicit grant type](/docs/topics/oauth2#implicit-grant). ::: ## State and Security diff --git a/docs/topics/rpc.md b/docs/topics/rpc.md index d40e7f87b5..64b0608eee 100644 --- a/docs/topics/rpc.md +++ b/docs/topics/rpc.md @@ -485,12 +485,7 @@ Used to change voice settings of users in voice channels | mute? | boolean | set the mute state of the user | :::info -In the current release, we only support a single modifier of voice settings at a time over RPC. -If an app changes voice settings, it will lock voice settings so that other apps connected simultaneously -lose the ability to change voice settings. Settings reset to what they were before being changed after the -controlling app disconnects. When an app that has previously set voice settings connects, the client will swap -to that app's configured voice settings and lock voice settings again. This is a temporary situation that will -be changed in the future. +In the current release, we only support a single modifier of voice settings at a time over RPC. If an app changes voice settings, it will lock voice settings so that other apps connected simultaneously lose the ability to change voice settings. Settings reset to what they were before being changed after the controlling app disconnects. When an app that has previously set voice settings connects, the client will swap to that app's configured voice settings and lock voice settings again. This is a temporary situation that will be changed in the future. ::: ###### Pan Object @@ -739,12 +734,7 @@ Used to join and leave text channels, group dms, or dms. Returns the [Get Channe #### SET_VOICE_SETTINGS :::info -In the current release, we only support a single modifier of voice settings at a time over RPC. -If an app changes voice settings, it will lock voice settings so that other apps connected simultaneously -lose the ability to change voice settings. Settings reset to what they were before being changed after the -controlling app disconnects. When an app that has previously set voice settings connects, the client will swap -to that app's configured voice settings and lock voice settings again. This is a temporary situation that will -be changed in the future. +In the current release, we only support a single modifier of voice settings at a time over RPC. If an app changes voice settings, it will lock voice settings so that other apps connected simultaneously lose the ability to change voice settings. Settings reset to what they were before being changed after the controlling app disconnects. When an app that has previously set voice settings connects, the client will swap to that app's configured voice settings and lock voice settings again. This is a temporary situation that will be changed in the future. ::: When setting voice settings, all fields are optional. Only passed fields are updated. diff --git a/docs/topics/voice-connections.mdx b/docs/topics/voice-connections.mdx index 6a6af958cf..133de03e33 100644 --- a/docs/topics/voice-connections.mdx +++ b/docs/topics/voice-connections.mdx @@ -8,8 +8,9 @@ To ensure that you have the most up-to-date information, please use [version 8]( Previously if the version query string `v` was omitted the voice gateway would default to version 1. That behavior is being deprecated, in the future you must present a voice gateway version or your voice connection will be rejected. ->warn ->Versions below 4 as well as the default version behaviour will be discontinued as of November 18th, 2024. Connections without a version or with a version less than version 4 will be rejected as of this date. +:::warn +Versions below 4 as well as the default version behavior will be discontinued as of November 18th, 2024. Connections without a version or with a version less than version 4 will be rejected as of this date. +::: ###### Gateway Versions @@ -66,9 +67,7 @@ With this information, we can move on to establishing a voice WebSocket connecti When sending a voice state update to change channels within the same guild, it is possible to receive a VOICE_SERVER_UPDATE with the same `endpoint` as the previous VOICE_SERVER_UPDATE. The `token` will be changed and you cannot re-use the previous session during a channel change, even if the endpoint remains the same. :::info -Bot users respect the voice channel's user limit, if set. When the voice channel is full, you will not receive -the Voice State Update or Voice Server Update events in response to your own Voice State Update. Having `MANAGE_CHANNELS` -permission bypasses this limit and allows you to join regardless of the channel being full or not. +Bot users respect the voice channel's user limit, if set. When the voice channel is full, you will not receive the Voice State Update or Voice Server Update events in response to your own Voice State Update. Having `MANAGE_CHANNELS` permission bypasses this limit and allows you to join regardless of the channel being full or not. ::: @@ -211,8 +210,9 @@ First, we open a UDP connection to the IP and port provided in the Ready payload Since September 2024, Discord is migrating voice and video in DMs, Group DMs, voice channels, and Go Live streams to use end-to-end encryption (E2EE). ->info ->You are not immediately required to support the E2EE protocol, as calls will automatically upgrade/downgrade to/from E2EE depending on the support of clients in the call. Non-E2EE connections to voice in DMs, Group DMs, voice channels, and Go Live streams will soon be deprecated and will be discontinued (after at least a six month deprecation window). +:::info +You are not immediately required to support the E2EE protocol, as calls will automatically upgrade/downgrade to/from E2EE depending on the support of clients in the call. Non-E2EE connections to voice in DMs, Group DMs, voice channels, and Go Live streams will soon be deprecated and will be discontinued (after at least a six month deprecation window). +::: This section is a high-level overview of how to support Discord's audio & video end-to-end encryption (DAVE) protocol, centered around the voice gateway opcodes necessary for the protocol. The most thorough documentation on the DAVE protocol is found in the [Protocol Whitepaper](https://daveprotocol.com). You may additionally be able to leverage or refer to our open-source library [libdave](https://github.com/discord/libdave) to assist your implementation. The exact format of the DAVE protocol opcodes is detailed in the [Voice Gateway Opcodes section of the protocol whitepaper](https://daveprotocol.com/#voice-gateway-opcodes). @@ -236,8 +236,9 @@ Include the highest DAVE protocol version you support in [Opcode 0 Identify](/do The voice gateway specifies the initial protocol version in [Opcode 4 Session Description](/docs/topics/opcodes-and-status-codes#voice) under `dave_protocol_version`. This may be any non-discontinued protocol version equal to or less than your supported protocol version. ->warn ->Clients must retain backwards-compatibility of any non-discontinued DAVE protocol versions. The voice gateway selects the lowest shared protocol version for the call. +:::warn +Clients must retain backwards-compatibility of any non-discontinued DAVE protocol versions. The voice gateway selects the lowest shared protocol version for the call. +::: ### Protocol Transitions @@ -397,11 +398,13 @@ Voice data sent to discord should be encoded with [Opus](https://www.opus-codec. | XSalsa20 Poly1305 Suffix | xsalsa20_poly1305_suffix | 24 random bytes | Deprecated | | XSalsa20 Poly1305 Lite | xsalsa20_poly1305_lite | 32-bit incremental integer value, appended to payload | Deprecated | ->warn ->The deprecated encryption modes above will be discontinued as of November 18th, 2024. As of this date the voice gateway will not allow you to connect with one of the deprecated encryption modes. +:::warn +The deprecated encryption modes above will be discontinued as of November 18th, 2024. As of this date the voice gateway will not allow you to connect with one of the deprecated encryption modes. +::: ->warn ->The nonce has to be stripped from the payload before encrypting and before decrypting the audio data +:::warn +The nonce has to be stripped from the payload before encrypting and before decrypting the audio data +::: The RTP size variants determine the unencrypted size of the RTP header in [the same way as SRTP](https://tools.ietf.org/html/rfc3711#section-3.1), which considers CSRCs and (optionally) the extension preamble to be part of the unencrypted header. The deprecated variants use a fixed size unencrypted header for RTP.