dfx 0.0.1 → 0.0.2

package/discord-api-docs/docs/rich_presence/How_To.md

@@ -1,302 +0,0 @@
-# Introducing Rich Presence
-
-> danger
-> The SDK that this documentation references, [Discord-RPC](https://github.com/discord/discord-rpc), has been deprecated in favor of our new [Discord GameSDK](#DOCS_GAME_SDK_SDK_STARTER_GUIDE/). Replacement functionality for the Rich Presence SDK can be found in the [Activity Manager](#DOCS_GAME_SDK_ACTIVITIES/) of that SDK. This documentation can be referenced for education but does not entirely reflect the new SDK.
-
-How easy is it for people to play your game together? With Rich Presence from Discord, it just got so easy, a ~~caveman~~ Junior Dev could do it.
-
-If you are testing a game integration with Rich Presence, other users will be able to see it. Please create a private test account and do not join any public servers while testing your integration.
-
-## So, what is it?
-
-Rich Presence allows you to leverage the totally overhauled "Now Playing" section in a Discord user's profile to help people play your game together. Rich game data—including duration, score, current boss or map, and so much more—lives inside Discord. You can spectate a friend's game directly from their profile popout, or party up via beautiful chat embeds with real-time information about open party slots and the party's in-game status. No more exchanging usernames and friend codes, or wondering if there's room for you to join. Rich Presence is a living invitation to play together, or to watch your friends kick butt.
-
-## Step 0: Get the SDK
-
-> warn
-> Please use our new Discord GameSDK. Read the documentation and get it [here](#DOCS_GAME_SDK_SDK_STARTER_GUIDE/).
-
-## So, how does it work?
-
-We worked hard to make using Discord's Rich Presence system as easy as possible. All you need is our header file—what you will interact with—and our library—where we did all the hard work for you—and you are ready to roll!
-
-In the header file, you'll find six event-emitting callbacks:
-
-1.  `ready()`
-2.  `errored()`
-3.  `disconnected()`
-4.  `joinGame()`
-5.  `spectateGame()`
-6.  `joinRequest()`
-
-These six callbacks make up the entirety of what you need to implement. Behind the scenes, we do all the heavy lifting for you.
-
-The header file also contains the `Discord_RunCallbacks()` function. This invokes any pending callbacks from Discord on the calling thread (it's thread safe!).
-
-## Initialization
-
-The first step in implementing Rich Presence is [creating an application](#APPLICATIONS). Once you've created your application, note and save your `Client ID`. You will need this to initialize the SDK; this value will be referred to throughout this documentation as both `client_id` and `application_id`. Next, scroll down to the bottom of your application's page and hit the button that says "Enable Rich Presence". This will allow you to upload assets to your dashboard for later use.
-
-To begin, you'll register your callback functions to the six `DiscordEventHandlers` and then call `Discord_Initialize()` with your `APPLICATION_ID`. If your game is distributed via Steam, you should also pass your application's Steam ID so Discord can launch your game through Steam:
-
-###### SDK Initialization Example
-
-```c
-void InitDiscord()
-{
-    DiscordEventHandlers handlers;
-    memset(&handlers, 0, sizeof(handlers));
-    handlers.ready = handleDiscordReady;
-    handlers.errored = handleDiscordError;
-    handlers.disconnected = handleDiscordDisconnected;
-    handlers.joinGame = handleDiscordJoinGame;
-    handlers.spectateGame = handleDiscordSpectateGame;
-    handlers.joinRequest = handleDiscordJoinRequest;
-
-    // Discord_Initialize(const char* applicationId, DiscordEventHandlers* handlers, int autoRegister, const char* optionalSteamId)
-    Discord_Initialize("418562325121990661", &handlers, 1, "1234");
-}
-```
-
-A quick breakdown on the `Discord_Initialize()` function:
-
-- `applicationId`: your client_id/application_id
-- `handlers`: the callback functions you registered for each Discord event
-- `autoRegister`: whether or not to register an application protocol for your game on the player's computer—necessary to launch games from Discord
-- `optionalSteamId`: your game's Steam application id, if your game is distributed on Steam
-
-When you are ready to publish your integration, we recommend digging into the source code of the SDK and copying `discord_register.h`, `discord_register_win.cpp`, `discord_register_osx.m`, and `discord_register_linux.cpp` into your installation and update process. By registering your application protocols on installation and update, your players won't need to run the game before being able to interact with invites, Ask to Join, and spectating in Discord.
-
-## Shutting Down
-
-Don't leave so soon! But when you _do_ shut down your application, don't forget to call `Discord_Shutdown()`. This properly terminates the thread and allows your application to shut down cleanly.
-
-If you don't want to register all your event handlers at initialization, you can do so dynamically with `Discord_UpdateHandlers()`; this will allow you to register a new set of event handlers. Be mindful that this will delete old handlers if they are not explicitly bound to your handlers struct when calling this function.
-
-## Updating Presence
-
-> warn
-> Deprecated in favor of [Discord GameSDK ActivityManager.UpdateActivity()](#DOCS_GAME_SDK_ACTIVITIES/updateactivity)
-
-The core of Discord's Rich Presence SDK is the `Discord_UpdatePresence()` function. This is what sends your game data up to Discord to be seen and used by others. You should call `Discord_UpdatePresence()` any time something important in the presence payload changes.
-
-`Discord_UpdatePresence()` has a rate limit of one update per 15 seconds. Developers do not need to do anything to handle this rate limit. The SDK will queue up any presence updates sent in that window and send the newest one once the client is free to do so. If you are sending presence updates very frequently and wondering why you don't see your Discord presence changing, that's why!
-
-###### Update Presence Example
-
-```c
-void UpdatePresence()
-{
-    char buffer[256];
-    DiscordRichPresence discordPresence;
-    memset(&discordPresence, 0, sizeof(discordPresence));
-    discordPresence.state = "In a Group";
-    sprintf(buffer, "Ranked | Mode: %d", GameEngine.GetMode());
-    discordPresence.details = buffer;
-    discordPresence.endTimestamp = time(0) + 5 * 60;
-    discordPresence.largeImageKey = "canary-large";
-    discordPresence.smallImageKey = "ptb-small";
-    discordPresence.partyId = GameEngine.GetPartyId();
-    discordPresence.partySize = 1;
-    discordPresence.partyMax = 6;
-    discordPresence.matchSecret = "4b2fdce12f639de8bfa7e3591b71a0d679d7c93f";
-    discordPresence.spectateSecret = "e7eb30d2ee025ed05c71ea495f770b76454ee4e0";
-    discordPresence.instance = 1;
-    Discord_UpdatePresence(&discordPresence);
-}
-```
-
-###### Update Presence Payload
-
-```c
-typedef struct DiscordRichPresence {
-    const char* state; /* max 128 bytes */
-    const char* details; /* max 128 bytes */
-    int64_t startTimestamp;
-    int64_t endTimestamp;
-    const char* largeImageKey; /* max 32 bytes */
-    const char* largeImageText; /* max 128 bytes */
-    const char* smallImageKey; /* max 32 bytes */
-    const char* smallImageText; /* max 128 bytes */
-    const char* partyId; /* max 128 bytes */
-    int partySize;
-    int partyMax;
-    const char* matchSecret; /* max 128 bytes */
-    const char* joinSecret; /* max 128 bytes */
-    const char* spectateSecret; /* max 128 bytes */
-    int8_t instance;
-} DiscordRichPresence;
-```
-
-###### Update Presence Payload Fields
-
-| parameter      | type     | description                                                                                                | example                                                    |
-| -------------- | -------- | ---------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- |
-| state          | char\*   | the user's current party status                                                                            | "Looking to Play", "Playing Solo", "In a Group"            |
-| details        | char\*   | what the player is currently doing                                                                         | "Competitive - Captain's Mode", "In Queue", "Unranked PvP" |
-| startTimestamp | int64_t  | epoch seconds for game start - including will show time as "elapsed"                                       | 1507665886                                                 |
-| endTimestamp   | int64_t  | epoch seconds for game end - including will show time as "remaining"                                       | 1507665886                                                 |
-| largeImageKey  | char\*   | name of the uploaded image for the large profile artwork                                                   | "default"                                                  |
-| largeImageText | char\*   | tooltip for the largeImageKey                                                                              | "Blade's Edge Arena", "Numbani", "Danger Zone"             |
-| smallImageKey  | char\*   | name of the uploaded image for the small profile artwork                                                   | "rogue"                                                    |
-| smallImageText | char\*   | tooltip for the smallImageKey                                                                              | "Rogue - Level 100"                                        |
-| partyId        | char\*   | id of the player's party, lobby, or group                                                                  | "ae488379-351d-4a4f-ad32-2b9b01c91657"                     |
-| partySize      | int      | current size of the player's party, lobby, or group                                                        | 1                                                          |
-| partyMax       | int      | maximum size of the player's party, lobby, or group                                                        | 5                                                          |
-| matchSecret    | char\*   | (for future use) unique hashed string for a player's match                                                 | MmhuZToxMjMxMjM6cWl3amR3MWlqZA==                           |
-| spectateSecret | char\*   | unique hashed string for Spectate button                                                                   | MTIzNDV8MTIzNDV8MTMyNDU0                                   |
-| joinSecret     | char\*   | unique hashed string for chat invitations and Ask to Join                                                  | MTI4NzM0OjFpMmhuZToxMjMxMjM=                               |
-| instance       | int8_t   | (for future use) integer representing a boolean for if the player is in an instance (an in-progress match) | 1                                                          |
-
-> info
-> Sending `endTimestamp` will **always** have the time displayed as "remaining" until the given time. Sending `startTimestamp` will show "elapsed" as long as there is no `endTimestamp` sent.
-
-Here's a handy image to see how these fields are actually displayed on a profile:
-
-![Graphical representation of the legend for rich presence details](rp-legend.png)
-
-| location                               | field name             | notes                                                                       |
-| -------------------------------------- | ---------------------- | --------------------------------------------------------------------------- |
-| First row below title                  | details                |                                                                             |
-| Second row below title                 | state                  |                                                                             |
-| Second row below title                 | partySize              | In parenthesis next to the `state`, first number in the format `(1 of 10)`  |
-| Second row below title                 | partyMax               | In parenthesis next to the `state`, second number in the format `(1 of 10)` |
-| Third row below title                  | startTimestamp         | Converted to a format such as `01:33 elapsed`                               |
-| First button at the bottom             | joinSecret             | Button has the text "Ask to join"                                           |
-| Second button at the bottom            | spectateSecret         | Button has the text "Spectate"                                              |
-| Large image to the left of any content | largeImageKey          | Four rows high, includes the title but not the bottom buttons               |
-| Small image to the left of any content | smallImageKey          | Small icon inset on the bottom right of the `largeImageKey`                 |
-
-Note that this layout may be subject to change without warning. This information is only provided to help those with
-impaired eyesight to understand the potential layout of this information in a user interface.
-
-## Joining
-
-> warn
-> Deprecated in favor of [Discord GameSDK ActivityManager.OnActivityJoin](#DOCS_GAME_SDK_ACTIVITIES/onactivityjoin) and [Discord GameSDK ActivityManager.OnActivityJoinRequest](#DOCS_GAME_SDK_ACTIVITIES/onactivityjoinrequest)
-
-#### Relevant Callbacks:
-
-`joinGame()`
-`joinRequest()`
-
-#### Relevant Payload Data:
-
-`partyId`
-`partySize`
-`partyMax`
-`joinSecret`
-
-When you send the relevant payload data in the `Discord_UpdatePresence()` call, your player can invite a Discord chat channel to play with them. This invite is tied to the player's party information; if their `partyId` changes, the invite will expire. If their `partySize` and `partyMax` changes, the invite will add, remove, and fill up slots dynamically.
-
-Other Discord users can click "Join" on the invitation. Their game will then launch, and the `joinGame()` callback will fire in their client with the inviting player's `joinSecret`. The client should reverse hash or otherwise unencrypt this secret and match the players together.
-
-### Ask to Join
-
-When Player B clicks the Ask to Join button on Player A's profile, the `joinRequest()` callback fires for Player A, sending the following data:
-
-###### Ask to Join Payload
-
-```c
-typedef struct DiscordJoinRequest {
-    char userId[32];
-    char username[344];
-    char discriminator[8];
-    char avatar[128];
-} DiscordJoinRequest;
-```
-
-###### Ask to Join Payload Fields
-
-| parameter     | type      | description                                                                                                                         |
-| ------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------- |
-| userId        | char[24]  | the userId of the player asking to join                                                                                             |
-| username      | char[344] | the username of the player asking to join                                                                                           |
-| discriminator | char[8]   | the discriminator of the player asking to join                                                                                      |
-| avatar\*      | char[128] | the avatar hash of the player asking to join—see [image formatting](#DOCS_REFERENCE/image-formatting) for how to retrieve the image |
-
-> warn
-> `avatar` can be an empty string if the user has not uploaded an avatar to Discord
-
-When it fires, your game should surface this data with a Yes or No choice for Player A to accept whether or not they wish to play with Player B. Then, call `Discord_Respond()` with Player B's `userId` and the appropriate response code:
-
-###### Ask to Join Response Codes
-
-| code                 | value |
-| -------------------- | ----- |
-| DISCORD_REPLY_NO     | 0     |
-| DISCORD_REPLY_YES    | 1     |
-| DISCORD_REPLY_IGNORE | 2     |
-
-The Ask to Join request persists for 30 seconds after the request is received, regardless of whether you have called `Discord_RunCallbacks()` within that window. Therefore, keep these two points in mind:
-
-- Ensure you call `Discord_RunCallbacks()` as frequently as possible to ensure your game client is up to date with any data from Discord
-- If the player is in a state in which they cannot interact with an Ask to Join request—like in the middle of a match—you should not send a `joinSecret` in the presence payload
-
-## Spectating
-
-> warn
-> Deprecated in favor of [Discord GameSDK ActivityManager.OnActivitySpectate](#DOCS_GAME_SDK_ACTIVITIES/onactivityspectate)
-
-#### Relevant Callbacks:
-
-`spectateGame()`
-
-#### Relevant Payload Data:
-
-`spectateSecret`
-
-When you send the relevant payload data in the `Discord_UpdatePresence()` call, your player will gain the ability to invite a Discord chat channel to spectate their game. This invite is tied to the `matchSecret` and will expire when it changes.
-
-Other Discord users can click "Spectate" on the invitation. Their game will launch, and the `spectateGame()` callback will fire in their client with the original player's `spectateSecret`. The client should reverse hash or otherwise unencrypt this secret and spectate that player's game.
-
-## Secrets
-
-Security is of the utmost importance to us here at Discord, and we know it is for you, too. That's why we want to make sure that you properly understand `matchSecret`, `joinSecret`, and `spectateSecret` so that your game data is safe and secure over the wire.
-
-To keep security on the up and up, Discord requires that you properly hash/encode/encrypt/put-a-padlock-on-and-swallow-the-key-but-wait-then-how-would-you-open-it your secrets.
-
-Secrets are obfuscated data of your choosing. They could be match ids, player ids, lobby ids, etc. You should send us data that someone else's game client would need to join or spectate their friend. If you can't or don't want to support those actions, you don't need to send us secrets.
-
-## Rich Presence Field Requirements
-
-All fields in the `DiscordRichPresence` object are entirely optional. Anything you choose to omit simply won't be displayed; the UI will dynamically adapt from the full Rich Presence object all the way down to the basic presence view. We highly encourage you to include as many fields as you can to make your game as attractive and interactive for other players as possible. However, if you choose to be a bit more selective, here's a handy table for what each piece of Rich Presence requires:
-
-###### Rich Presence Field Requirements
-
-|     Field      | Custom Artwork | Spectating | Joining | Ask to Join |
-| :------------: | :------------: | :--------: | :-----: | :---------: |
-|     state      |                |            |         |             |
-|    details     |                |            |         |             |
-| startTimestamp |                |            |         |             |
-|  endTimestamp  |                |            |         |             |
-| largeImageKey  |       x        |            |         |             |
-| smallImageKey  |       x        |            |         |             |
-| largeImageText |       x        |            |         |             |
-| smallImageText |       x        |            |         |             |
-|    partyId     |                |            |    x    |      x      |
-|   partySize    |                |            |    x    |      x      |
-|    partyMax    |                |            |    x    |      x      |
-|  matchSecret   |                |            |         |             |
-|   joinSecret   |                |            |    x    |      x      |
-| spectateSecret |                |     x      |         |             |
-|    instance    |                |            |         |             |
-
-## Your New Developer Dashboard
-
-Included with the launch of Rich Presence is an overhaul of Discord's Developer Dashboard. We want to make Rich Presence as easy as possible to use. Our first step is helping you ditch your CDN. You're welcome.
-
-OK, well, not entirely. But! Discord _will_ host any and all artwork that you need to have the very richest of presences. Upload an image, tag it with a key—preferably one you can remember—and **bam**. It's ready for Rich Presence use. Head over to your [applications page](#APPLICATIONS) to check it out!
-
-> warn
-> **Asset keys are automatically normalized to lowercase**. Be mindful of this when referring to them in your code.
-
-## A note on testing and Game Detection
-
-If you don't see Rich Presence data in your profile while testing, make sure you don't have multiple instances of Discord running—if you do, your presence might be changing in one of those!
-
-If you're testing on your own, we recommend [downloading two separate release channels](https://discord.com/download) of the Discord desktop client. You can log into the stable, public test, and canary builds with separate credentials, making testing easier for a single developer.
-
-## So, what now?
-
-Get to coding! We can't wait to see the awesome integration you come up with. If you need some quick questions answered, look no further than our [Rich Presence FAQ](#DOCS_RICH_PRESENCE_FAQ/). If you want to know how to make your integration the best it can be, read our [Best Practices Guide](#DOCS_RICH_PRESENCE_BEST_PRACTICES/). If you're ready to release, consult our [Launch Checklist](#DOCS_RICH_PRESENCE_LAUNCH_CHECKLIST/) and make sure you haven't missed anything!

package/discord-api-docs/docs/rich_presence/Launch_Checklist.md

@@ -1,46 +0,0 @@
-# Rich Presence Launch Checklist
-
-> danger
-> The SDK that this documentation references, [Discord-RPC](https://github.com/discord/discord-rpc), has been deprecated in favor of our new [Discord GameSDK](#DOCS_GAME_SDK_SDK_STARTER_GUIDE/). Replacement functionality for the Rich Presence SDK can be found in the [Activity Manager](#DOCS_GAME_SDK_ACTIVITIES/) of that SDK. This documentation can be referenced for education but does not entirely reflect the new SDK.
-
-Ready to launch a Rich Presence integration for your game? Did you read our [Best Practices](#DOCS_RICH_PRESENCE_BEST_PRACTICES/) guide? If so, we recommend looking over this checklist one last time to ensure that your integration is as great as it can be!
-
-> warn
-> Our precompiled libraries depend on the [Visual C++ Redistributable for Visual Studio 2015](https://www.microsoft.com/en-us/download/details.aspx?id=48145). If you distribute your game on Steam, make sure to check that box in your common redistributable settings.
-
-#### Profile Strings
-
-- Have you made use of all available fields where appropriate?
-- Do your strings fit on their own lines without line wrapping?
-  - Did you check on the smaller profile pop out?
-- Do they clearly communicate:
-  - What the player is currently doing?
-  - If the player is in a group or playing alone?
-  - If the player is in a state where they can party up?
-
-#### Artwork
-
-- Is your artwork high resolution?
-- Are your images at least 1024x1024 pixels?
-- Is it clean, interesting, and descriptive without being too highly detailed?
-- Do you have artwork for every different state? Don't forget your default state/main menu!
-- Did you make use of tooltips and the small image where appropriate?
-
-#### Joining
-
-- Have you successfully implemented join invites for your game if applicable?
-- Does the state of the invite properly represent the party/group in-game with regards to:
-  - Size?
-  - Open slots?
-  - Discord _and_ non-Discord users in the party?
-- Are you able to post invites to Discord without any additional in-game setup or configuration?
-- Are you properly removing data from the presence payload when someone can no longer send invites?
-  - A `joinSecret` should not be sent if the player can't invite anyone!
-
-#### Spectating
-
-- Have you successfully implemented spectate invites for your game if applicable?
-- Is your game's spectate mode true spectating?
-  - We do _not_ allow using the Spectate button as a pseudo-Join button.
-- Are you properly removing data from the presence payload when someone can no longer spectate?
-  - A `spectateSecret` should not be sent if the player can't be spectated!

package/discord-api-docs/docs/topics/Certified_Devices.md

@@ -1,200 +0,0 @@
-# Certified Devices
-
-Baked into Discord is the ability for hardware manufacturers to tell us a little more about the certified devices that are plugged into a user's computer. Unfortunately, no, you can't show that a user's PUBG Chicken Dinner was all thanks to the amazing TotallyRealHardware RGB Mouse and Keyboard Set Extraordinaire™, but you _can_ give them an amazing experience using your hardware with Discord!
-
-## How's it work?
-
-I'm glad you asked!
-
-1. [Create an application](#APPLICATIONS) for your hardware vendor—save the Client ID!
-2. Talk to Discord via one simple HTTP or WebSocket call
-3. Send us a [`SET_CERTIFIED_DEVICES`](#DOCS_TOPICS_RPC/setcertifieddevices) WebSocket payload or equivalent HTTP POST whenever the state of the device changes
-
-Yup, that's it. You give us the real-time info about any connected devices, and we'll handle the rest to make sure that anyone using your device will have an awesome experience. Your device will also have a `CERTIFIED` badge in Discord's audio settings, and really, who doesn't love badges?
-
-![An example of how a certified device may be shown for an example audio input and output device](certified-device.png)
-
-## Connecting
-
-###### Query String Params
-
-| Name      | Value                | Required  |
-| --------- | -------------------- | --------- |
-| v         | `1`                  | All       |
-| client_id | your app's client id | All       |
-| encoding  | `json`               | WebSocket |
-
-You can send event updates to the following URIs:
-
-###### HTTP
-
-```
-http://127.0.0.1:PORT/rpc?v=1&client_id=YOUR_CLIENT_ID
-```
-
-###### WebSocket
-
-```
-ws://127.0.0.1:PORT?v=1&client_id=YOUR_CLIENT_ID&encoding=json
-```
-
-`PORT` is a range of ports from `6463` to `6473`. You should iterate over these ports with your request until one returns a success response code or succeeds with a socket connection. Keep track of that port number for the rest of the session.
-
-To keep your hardware in sync with Discord, send updates any time the hardware mute is toggled, or one of the voice features like echo cancellation is enabled or disabled by the user. This lets Discord get out of the way of your optimization when you're in control, or help out when you're not, ensuring an awesome experience for anyone using your hardware.
-
-Each time you update, send a full array of `devices`, sorted by your preferred priority. That means if you want a specific headset to be the default that Discord will attempt to use, put it first in the array.
-
-## Getting Device UUID
-
-For each device in the `SET_CERTIFIED_DEVICES` payload, there is an `id` field. This `id` should be the Windows device's UUID, retrieved through the native Windows API. You'll get back something that looks like `{0.0.1.00000000}.{6cff2b76-44a8-46b9-b528-262ad8609d9f}`.
-
-> info
-> On macOS, the `id` will be the name of the device.
-
-###### Microphone Id Example
-
-```cpp
-id = waveInMessage((HWAVEIN)IntToPtr(index),
-                      DRV_QUERYFUNCTIONINSTANCEID,
-                      (DWORD_PTR)pstrEndpointId,
-                      cbEndpointId);
-```
-
-###### Speaker Id Example
-
-```cpp
-id = waveOutMessage((HWAVEIN)IntToPtr(index),
-                      DRV_QUERYFUNCTIONINSTANCEID,
-                      (DWORD_PTR)pstrEndpointId,
-                      cbEndpointId);
-```
-
-## HTTP Example
-
-###### HTTP Request Example
-
-```
-curl -X POST -H 'Content-Type: application/json' -d '
-{
-  "nonce": "9b4e9711-97f3-4f35-b047-32c82a51978e",
-  "cmd": "SET_CERTIFIED_DEVICES",
-  "args": {
-    "devices": [
-      {
-        "type": "audioinput",
-        "id": "{0.0.1.00000000}.{6cff2b76-44a8-46b9-b528-262ad8609d9f}",
-        "vendor": {
-          "name": "SteelSeries",
-          "url": "https://steelseries.com"
-        },
-        "model": {
-          "name": "Arctis 7",
-          "url": "https://steelseries.com/gaming-headsets/arctis-7"
-        },
-        "related": ["{0.0.1.00000000}.{6cff2b76-44a8-46b9-b528-262ad8609d9f}"],
-        "echo_cancellation": true,
-        "noise_suppression": true,
-        "automatic_gain_control": true,
-        "hardware_mute": false
-      }
-    ]
-  }
-}
-' http://127.0.0.1:PORT/rpc?v=1&client_id=YOUR_CLIENT_ID
-```
-
-The socket will respond with a `200 OK` status code and the following JSON.
-
-###### HTTP Response Example
-
-```json
-{
-  "cmd": "SET_CERTIFIED_DEVICES",
-  "data": null,
-  "evt": null,
-  "nonce": "9b4e9711-97f3-4f35-b047-32c82a51978e"
-}
-```
-
-## WebSocket Example
-
-###### RPC Command Example
-
-```json
-{
-  "nonce": "9b4e9711-97f3-4f35-b047-32c82a51978e",
-  "cmd": "SET_CERTIFIED_DEVICES",
-  "args": {
-    "devices": [
-      {
-        "type": "audioinput",
-        "id": "{0.0.1.00000000}.{6cff2b76-44a8-46b9-b528-262ad8609d9f}",
-        "vendor": {
-          "name": "SteelSeries",
-          "url": "https://steelseries.com"
-        },
-        "model": {
-          "name": "Arctis 7",
-          "url": "https://steelseries.com/gaming-headsets/arctis-7"
-        },
-        "related": ["{0.0.1.00000000}.{6cff2b76-44a8-46b9-b528-262ad8609d9f}"],
-        "echo_cancellation": true,
-        "noise_suppression": true,
-        "automatic_gain_control": true,
-        "hardware_mute": false
-      }
-    ]
-  }
-}
-```
-
-###### RPC Response Example
-
-```json
-{
-  "nonce": "9b4e9711-97f3-4f35-b047-32c82a51978e",
-  "cmd": "SET_CERTIFIED_DEVICES",
-  "data": null,
-  "evt": null
-}
-```
-
-## Models
-
-###### Device Object
-
-| Field                     | Type                                                                 | Description                                              |
-| ------------------------- | -------------------------------------------------------------------- | -------------------------------------------------------- |
-| type                      | [device type](#DOCS_TOPICS_CERTIFIED_DEVICES/models-device-type)     | the type of device                                       |
-| id                        | string                                                               | the device's Windows UUID                                |
-| vendor                    | [vendor](#DOCS_TOPICS_CERTIFIED_DEVICES/models-vendor-object) object | the hardware vendor                                      |
-| model                     | [model](#DOCS_TOPICS_CERTIFIED_DEVICES/models-model-object) object   | the model of the product                                 |
-| related                   | array of strings                                                     | UUIDs of related devices                                 |
-| echo_cancellation?\*      | boolean                                                              | if the device's native echo cancellation is enabled      |
-| noise_suppression?\*      | boolean                                                              | if the device's native noise suppression is enabled      |
-| automatic_gain_control?\* | boolean                                                              | if the device's native automatic gain control is enabled |
-| hardware_mute?\*          | boolean                                                              | if the device is hardware muted                          |
-
-\*These fields are only applicable for `AUDIO_INPUT` device types
-
-###### Vendor Object
-
-| Field | Type   | Description        |
-| ----- | ------ | ------------------ |
-| name  | string | name of the vendor |
-| url   | string | url for the vendor |
-
-###### Model Object
-
-| Field | Type   | Description       |
-| ----- | ------ | ----------------- |
-| name  | string | name of the model |
-| url   | string | url for the model |
-
-###### Device Type
-
-| Type         | Value         |
-| ------------ | ------------- |
-| AUDIO_INPUT  | "audioinput"  |
-| AUDIO_OUTPUT | "audiooutput" |
-| VIDEO_INPUT  | "videoinput"  |

package/discord-api-docs/docs/topics/Community_Resources.md

@@ -1,98 +0,0 @@
-# Community Resources
-
-Discord has the best online community. At least, we like to think so, and this is our website, so our word is law, deal with it. Therefore it's a fact that our community is the best, and they make really awesome things that we want to share with developers to make their lives easier. From permissions calculators to embed visualizers to full libraries to interface with our API, there are so many great things that have come out of our community.
-
-## Discord Developers
-
-The [Official Discord Developers server](https://discord.gg/discord-developers) is a developer ran, but community driven, support hub. If you need help with developing something on Discord or want official updates from the developers, this is the place to be.
-
-## Libraries
-
-Discord does not maintain official SDKs.  The following table is an inexhaustive list of third-party libraries that have valid rate limit implementations, are recently maintained, and have large communities of active bots.
-
-###### Discord Libraries
-
-| Name                                                         | Language   |
-| ------------------------------------------------------------ | ---------- |
-| [Discord.Net](https://github.com/discord-net/Discord.Net)    | C#         |
-| [DSharpPlus](https://github.com/DSharpPlus/DSharpPlus)       | C#         |
-| [nyxx](https://github.com/l7ssha/Nyxx)                       | Dart       |
-| [DiscordGo](https://github.com/bwmarrin/discordgo)           | Go         |
-| [Discord4J](https://discord4j.com/)                          | Java       |
-| [Javacord](https://github.com/Javacord/Javacord)             | Java       |
-| [JDA](https://github.com/DV8FromTheWorld/JDA)                | Java       |
-| [discord.js](https://github.com/discordjs/discord.js)        | JavaScript |
-| [Eris](https://github.com/abalabahaha/eris)                  | JavaScript |
-| [Discordia](https://github.com/SinisterRectus/Discordia)     | Lua        |
-| [DiscordPHP](https://github.com/discord-php/DiscordPHP)      | PHP        |
-| [discord.py](https://github.com/Rapptz/discord.py)           | Python     |
-| [disnake](https://github.com/DisnakeDev/disnake)             | Python     |
-| [hikari](https://github.com/hikari-py/hikari)                | Python     |
-| [nextcord](https://github.com/nextcord/nextcord)             | Python     |
-| [pycord](https://github.com/Pycord-Development/pycord)       | Python     |
-| [discordrb](https://github.com/shardlab/discordrb)           | Ruby       |
-| [Serenity](https://github.com/serenity-rs/serenity)          | Rust       |
-
-## Interactions
-
-[Interactions](#DOCS_INTERACTIONS_RECEIVING_AND_RESPONDING/) are the great, new way of making a Discord bot. The following open-source libraries provide help for the security and authentication checks that are mandatory if you are receiving Interactions via outgoing webhook. They also include some types for the Interactions data models.
-
-- Clojure
-  - [ring-discord-auth](https://github.com/JohnnyJayJay/ring-discord-auth)
-- Dart
-  - [nyxx_interactions](https://github.com/l7ssha/Nyxx)
-- Go
-  - [discord-interactions-go](https://github.com/bsdlp/discord-interactions-go)
-- Javascript
-  - [discord-interactions-js](https://github.com/discord/discord-interactions-js)
-  - [discord-slash-commands](https://github.com/MeguminSama/discord-slash-commands) and its [Deno fork](https://deno.land/x/discord_slash_commands)
-  - [slash-create](https://github.com/Snazzah/slash-create)
-- Python
-  - [discord-interactions-python](https://github.com/discord/discord-interactions-python)
-  - [discord-interactions.py](https://github.com/LiBa001/discord-interactions.py)
-  - [dispike](https://github.com/ms7m/dispike)
-  - [flask-discord-interactions](https://github.com/Breq16/flask-discord-interactions)
-- PHP
-  - [discord-interactions-php](https://github.com/discord/discord-interactions-php)
-- Other
-  - [caddy-discord-interactions-verifier](https://github.com/CarsonHoffman/caddy-discord-interactions-verifier)
-  - [Rauf's Slash Command Generator](https://rauf.wtf/slash)
-  - [Autocode Slash Command Builder](https://autocode.com/tools/discord/command-builder/)
-
-## Game SDK Tools
-
-Discord Game SDK's lobby and networking layer shares similarities with other gaming platforms (i.e. Valve's Steamworks SDK). The following open source library provides developers a uniform interface for these shared features and can simplify developing for multiple platforms. Note: this library is tailored for Unity3D development.
-
-- [HouraiNetworking](https://github.com/HouraiTeahouse/HouraiNetworking)
-
-## Dispatch Tools
-
-Using Discord's [Dispatch](#DOCS_DISPATCH_DISPATCH_AND_YOU) tool for game developers publishing on Discord can sometimes involve using the same long commands multiple times. The following open-source tool helps shorten these commands for you. It will also provide webhook support for when you're pushing an update.
-
-- [JohnyTheCarrot's Dispatch CLI](https://github.com/JohnyTheCarrot/droops-dispatch)
-
-## Permission Calculators
-
-[Permissions](#DOCS_TOPICS_PERMISSIONS/permissions) in Discord are tricky. Luckily, we've got really smart people who love us and have made some great permissions calculators. If you're making a bot for others, and you're not sure how to properly calculate permissions or generate your [authorization URL](#DOCS_TOPICS_OAUTH2/bot-authorization-flow), these are great tools:
-
-- [FiniteReality's Permissions Calculator](https://finitereality.github.io/permissions-calculator/?v=0)
-- [abalabahaha's Permissions Calculator](https://discordapi.com/permissions.html#0)
-
-## Intent Calculators
-
-[Gateway Intents](#DOCS_TOPICS_GATEWAY/gateway-intents) are pretty confusing at first. If you're not sure what to send in your [identify payload](#DOCS_TOPICS_GATEWAY/identify), then these tools may be of help:
-
-- [ziad87's Intent Calculator](https://ziad87.net/intents/)
-- [Larko's Intent Calculator](https://discord-intents-calculator.vercel.app/)
-
-## Embed Visualizer
-
-Webhooks and embeds might seem like black magic. That's because they are, but let us help you demystify them a bit. This sweet embed visualizer lets you play around with JSON data and see exactly how it will look embedded in Discord. It even includes a webhook mode!
-
-- [Autocode Embed Builder](https://autocode.com/tools/discord/embed-builder/)
-
-## API Types
-
-If you're working on a project that interacts with our API, you might find an API types module useful as it provides type inspection/completion for the Discord API.
-
-- [discord.js API Types](https://github.com/discordjs/discord-api-types)