dfx 0.0.1 → 0.0.2

package/discord-api-docs/docs/resources/Webhook.md

@@ -1,281 +0,0 @@
-# Webhook Resource
-
-Webhooks are a low-effort way to post messages to channels in Discord. They do not require a bot user or authentication to use.
-
-### Webhook Object
-
-Used to represent a webhook.
-
-###### Webhook Structure
-
-| Field           | Type                                                             | Description                                                                                                   |
-| --------------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
-| id              | snowflake                                                        | the id of the webhook                                                                                         |
-| type            | integer                                                          | the [type](#DOCS_RESOURCES_WEBHOOK/webhook-object-webhook-types) of the webhook                               |
-| guild_id?       | ?snowflake                                                       | the guild id this webhook is for, if any                                                                      |
-| channel_id      | ?snowflake                                                       | the channel id this webhook is for, if any                                                                    |
-| user?           | [user](#DOCS_RESOURCES_USER/user-object) object                  | the user this webhook was created by (not returned when getting a webhook with its token)                     |
-| name            | ?string                                                          | the default name of the webhook                                                                               |
-| avatar          | ?string                                                          | the default user avatar [hash](#DOCS_REFERENCE/image-formatting) of the webhook                               |
-| token?          | string                                                           | the secure token of the webhook (returned for Incoming Webhooks)                                              |
-| application_id  | ?snowflake                                                       | the bot/OAuth2 application that created this webhook                                                          |
-| source_guild?   | partial [guild](#DOCS_RESOURCES_GUILD/guild-object) object       | the guild of the channel that this webhook is following (returned for Channel Follower Webhooks)              |
-| source_channel? | partial [channel](#DOCS_RESOURCES_CHANNEL/channel-object) object | the channel that this webhook is following (returned for Channel Follower Webhooks)                           |
-| url?            | string                                                           | the url used for executing the webhook (returned by the [webhooks](#DOCS_TOPICS_OAUTH2/webhooks) OAuth2 flow) |
-
-###### Webhook Types
-
-| Value | Name             | Description                                                                                                    |
-| ----- | ---------------- | -------------------------------------------------------------------------------------------------------------- |
-| 1     | Incoming         | Incoming Webhooks can post messages to channels with a generated token                                         |
-| 2     | Channel Follower | Channel Follower Webhooks are internal webhooks used with Channel Following to post new messages into channels |
-| 3     | Application      | Application webhooks are webhooks used with Interactions                                                       |
-
-###### Example Incoming Webhook
-
-```json
-{
-  "name": "test webhook",
-  "type": 1,
-  "channel_id": "199737254929760256",
-  "token": "3d89bb7572e0fb30d8128367b3b1b44fecd1726de135cbe28a41f8b2f777c372ba2939e72279b94526ff5d1bd4358d65cf11",
-  "avatar": null,
-  "guild_id": "199737254929760256",
-  "id": "223704706495545344",
-  "application_id": null,
-  "user": {
-    "username": "test",
-    "discriminator": "7479",
-    "id": "190320984123768832",
-    "avatar": "b004ec1740a63ca06ae2e14c5cee11f3",
-    "public_flags": 131328
-  }
-}
-```
-
-###### Example Channel Follower Webhook
-
-```json
-{
-  "type": 2,
-  "id": "752831914402115456",
-  "name": "Guildy name",
-  "avatar": "bb71f469c158984e265093a81b3397fb",
-  "channel_id": "561885260615255432",
-  "guild_id": "56188498421443265",
-  "application_id": null,
-  "source_guild": {
-    "id": "56188498421476534",
-    "name": "Guildy name",
-    "icon": "bb71f469c158984e265093a81b3397fb"
-  },
-  "source_channel": {
-    "id": "5618852344134324",
-    "name": "announcements"
-  },
-  "user": {
-    "username": "test",
-    "discriminator": "7479",
-    "id": "190320984123768832",
-    "avatar": "b004ec1740a63ca06ae2e14c5cee11f3",
-    "public_flags": 131328
-  }
-}
-```
-
-###### Example Application Webhook
-
-```json
-{
-  "type": 3,
-  "id": "658822586720976555",
-  "name": "Clyde",
-  "avatar": "689161dc90ac261d00f1608694ac6bfd",
-  "channel_id": null,
-  "guild_id": null,
-  "application_id": "658822586720976555"
-}
-```
-
-## Create Webhook % POST /channels/{channel.id#DOCS_RESOURCES_CHANNEL/channel-object}/webhooks
-
-Creates a new webhook and returns a [webhook](#DOCS_RESOURCES_WEBHOOK/webhook-object) object on success. Requires the `MANAGE_WEBHOOKS` permission.
-
-An error will be returned if a webhook name (`name`) is not valid. A webhook name is valid if:
-- It does not contain the substring '**clyde**' (case-insensitive)
-- It follows the nickname guidelines in the [Usernames and Nicknames](#DOCS_RESOURCES_USER/usernames-and-nicknames) documentation, with an exception that webhook names can be up to 80 characters
-
-> info
-> This endpoint supports the `X-Audit-Log-Reason` header.
-
-###### JSON Params
-
-| Field   | Type                                      | Description                           |
-| ------- | ----------------------------------------- | ------------------------------------- |
-| name    | string                                    | name of the webhook (1-80 characters) |
-| avatar? | ?[image data](#DOCS_REFERENCE/image-data) | image for the default webhook avatar  |
-
-## Get Channel Webhooks % GET /channels/{channel.id#DOCS_RESOURCES_CHANNEL/channel-object}/webhooks
-
-Returns a list of channel [webhook](#DOCS_RESOURCES_WEBHOOK/webhook-object) objects. Requires the `MANAGE_WEBHOOKS` permission.
-
-## Get Guild Webhooks % GET /guilds/{guild.id#DOCS_RESOURCES_GUILD/guild-object}/webhooks
-
-Returns a list of guild [webhook](#DOCS_RESOURCES_WEBHOOK/webhook-object) objects. Requires the `MANAGE_WEBHOOKS` permission.
-
-## Get Webhook % GET /webhooks/{webhook.id#DOCS_RESOURCES_WEBHOOK/webhook-object}
-
-Returns the new [webhook](#DOCS_RESOURCES_WEBHOOK/webhook-object) object for the given id.
-
-## Get Webhook with Token % GET /webhooks/{webhook.id#DOCS_RESOURCES_WEBHOOK/webhook-object}/{webhook.token#DOCS_RESOURCES_WEBHOOK/webhook-object}
-
-Same as above, except this call does not require authentication and returns no user in the webhook object.
-
-## Modify Webhook % PATCH /webhooks/{webhook.id#DOCS_RESOURCES_WEBHOOK/webhook-object}
-
-Modify a webhook. Requires the `MANAGE_WEBHOOKS` permission. Returns the updated [webhook](#DOCS_RESOURCES_WEBHOOK/webhook-object) object on success.
-
-> info
-> All parameters to this endpoint are optional
-
-> info
-> This endpoint supports the `X-Audit-Log-Reason` header.
-
-###### JSON Params
-
-| Field      | Type                                      | Description                                        |
-| ---------- | ----------------------------------------- | -------------------------------------------------- |
-| name       | string                                    | the default name of the webhook                    |
-| avatar     | ?[image data](#DOCS_REFERENCE/image-data) | image for the default webhook avatar               |
-| channel_id | snowflake                                 | the new channel id this webhook should be moved to |
-
-## Modify Webhook with Token % PATCH /webhooks/{webhook.id#DOCS_RESOURCES_WEBHOOK/webhook-object}/{webhook.token#DOCS_RESOURCES_WEBHOOK/webhook-object}
-
-Same as above, except this call does not require authentication, does not accept a `channel_id` parameter in the body, and does not return a user in the webhook object.
-
-## Delete Webhook % DELETE /webhooks/{webhook.id#DOCS_RESOURCES_WEBHOOK/webhook-object}
-
-Delete a webhook permanently. Requires the `MANAGE_WEBHOOKS` permission. Returns a `204 No Content` response on success.
-
-> info
-> This endpoint supports the `X-Audit-Log-Reason` header.
-
-## Delete Webhook with Token % DELETE /webhooks/{webhook.id#DOCS_RESOURCES_WEBHOOK/webhook-object}/{webhook.token#DOCS_RESOURCES_WEBHOOK/webhook-object}
-
-Same as above, except this call does not require authentication.
-
-## Execute Webhook % POST /webhooks/{webhook.id#DOCS_RESOURCES_WEBHOOK/webhook-object}/{webhook.token#DOCS_RESOURCES_WEBHOOK/webhook-object}
-
-Refer to [Uploading Files](#DOCS_REFERENCE/uploading-files) for details on attachments and `multipart/form-data` requests. Returns a message or `204 No Content` depending on the `wait` query parameter.
-
-> info
-> Note that when sending a message, you must provide a value for at **least one of** `content`, `embeds`, or `file`.
-
-###### Query String Params
-
-| Field | Type    | Description                                                                                                                                                                                  | Required |
-| ----- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
-| wait  | boolean | waits for server confirmation of message send before response, and returns the created message body (defaults to `false`; when `false` a message that is not saved does not return an error) | false    |
-| thread_id | snowflake | Send a message to the specified thread within a webhook's channel. The thread will automatically be unarchived. | false    |
-
-###### JSON/Form Params
-
-| Field            | Type                                                                                 | Description                                                                                                                                                                 | Required                     |
-| ---------------- | ------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------- |
-| content          | string                                                                               | the message contents (up to 2000 characters)                                                                                                                                | one of content, file, embeds |
-| username         | string                                                                               | override the default username of the webhook                                                                                                                                | false                        |
-| avatar_url       | string                                                                               | override the default avatar of the webhook                                                                                                                                  | false                        |
-| tts              | boolean                                                                              | true if this is a TTS message                                                                                                                                               | false                        |
-| embeds           | array of up to 10 [embed](#DOCS_RESOURCES_CHANNEL/embed-object) objects              | embedded `rich` content                                                                                                                                                     | one of content, file, embeds |
-| allowed_mentions | [allowed mention object](#DOCS_RESOURCES_CHANNEL/allowed-mentions-object)            | allowed mentions for the message                                                                                                                                            | false                        |
-| components \*    | array of [message component](#DOCS_INTERACTIONS_MESSAGE_COMPONENTS/component-object) | the components to include with the message                                                                                                                                  | false                        |
-| files[n] \*\*    | file contents                                                                        | the contents of the file being sent                                                                                                                                         | one of content, file, embeds |
-| payload_json \*\*| string                                                                               | JSON encoded body of non-file params                                                                                                                                        | `multipart/form-data` only   |
-| attachments \*\* | array of partial [attachment](#DOCS_RESOURCES_CHANNEL/attachment-object) objects     | attachment objects with filename and description                                                                                                                            | false                        |
-| flags            | integer                                                                              | [message flags](#DOCS_RESOURCES_CHANNEL/message-object-message-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field) (only `SUPPRESS_EMBEDS` can be set) | false                        |
-
-\* Requires an application-owned webhook.
-
-\*\* See [Uploading Files](#DOCS_REFERENCE/uploading-files) for details.
-
-> info
-> For the webhook embed objects, you can set every field except `type` (it will be `rich` regardless of if you try to set it), `provider`, `video`, and any `height`, `width`, or `proxy_url` values for images.
-
-## Execute Slack-Compatible Webhook % POST /webhooks/{webhook.id#DOCS_RESOURCES_WEBHOOK/webhook-object}/{webhook.token#DOCS_RESOURCES_WEBHOOK/webhook-object}/slack
-
-Refer to [Slack's documentation](https://api.slack.com/incoming-webhooks) for more information. We do not support Slack's `channel`, `icon_emoji`, `mrkdwn`, or `mrkdwn_in` properties.
-
-###### Query String Params
-
-| Field     | Type      | Description                                                                                                                                           | Required |
-| --------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
-| thread_id | snowflake | id of the thread to send the message in                                                                                                               | false    |
-| wait      | boolean   | waits for server confirmation of message send before response (defaults to `true`; when `false` a message that is not saved does not return an error) | false    |
-
-## Execute GitHub-Compatible Webhook % POST /webhooks/{webhook.id#DOCS_RESOURCES_WEBHOOK/webhook-object}/{webhook.token#DOCS_RESOURCES_WEBHOOK/webhook-object}/github
-
-Add a new webhook to your GitHub repo (in the repo's settings), and use this endpoint as the "Payload URL." You can choose what events your Discord channel receives by choosing the "Let me select individual events" option and selecting individual events for the new webhook you're configuring.
-
-###### Query String Params
-
-| Field     | Type      | Description                                                                                                                                           | Required |
-| --------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
-| thread_id | snowflake | id of the thread to send the message in                                                                                                               | false    |
-| wait      | boolean   | waits for server confirmation of message send before response (defaults to `true`; when `false` a message that is not saved does not return an error) | false    |
-
-## Get Webhook Message % GET /webhooks/{webhook.id#DOCS_RESOURCES_WEBHOOK/webhook-object}/{webhook.token#DOCS_RESOURCES_WEBHOOK/webhook-object}/messages/{message.id#DOCS_RESOURCES_CHANNEL/message-object}
-
-Returns a previously-sent webhook message from the same token. Returns a [message](#DOCS_RESOURCES_CHANNEL/message-object) object on success.
-
-###### Query String Params
-
-| Field     | Type      | Description                        | Required |
-| --------- | --------- | ---------------------------------- | -------- |
-| thread_id | snowflake | id of the thread the message is in | false    |
-
-## Edit Webhook Message % PATCH /webhooks/{webhook.id#DOCS_RESOURCES_WEBHOOK/webhook-object}/{webhook.token#DOCS_RESOURCES_WEBHOOK/webhook-object}/messages/{message.id#DOCS_RESOURCES_CHANNEL/message-object}
-
-Edits a previously-sent webhook message from the same token. Returns a [message](#DOCS_RESOURCES_CHANNEL/message-object) object on success.
-
-When the `content` field is edited, the `mentions` array in the message object will be reconstructed from scratch based on the new content. The `allowed_mentions` field of the edit request controls how this happens. If there is no explicit `allowed_mentions` in the edit request, the content will be parsed with _default_ allowances, that is, without regard to whether or not an `allowed_mentions` was present in the request that originally created the message.
-
-Refer to [Uploading Files](#DOCS_REFERENCE/uploading-files) for details on attachments and `multipart/form-data` requests.
-Any provided files will be **appended** to the message. To remove or replace files you will have to supply the `attachments` field which specifies the files to retain on the message after edit.
-
-> warn
-> Starting with API v10, the `attachments` array must contain all attachments that should be present after edit, including **retained and new** attachments provided in the request body.
-
-> info
-> All parameters to this endpoint are optional and nullable.
-
-###### Query String Params
-
-| Field     | Type      | Description                        | Required |
-| --------- | --------- | ---------------------------------- | -------- |
-| thread_id | snowflake | id of the thread the message is in | false    |
-
-###### JSON/Form Params
-
-| Field            | Type                                                                                 | Description                                                     |
-| ---------------- | ------------------------------------------------------------------------------------ | --------------------------------------------------------------- |
-| content          | string                                                                               | the message contents (up to 2000 characters)                    |
-| embeds           | array of up to 10 [embed](#DOCS_RESOURCES_CHANNEL/embed-object) objects              | embedded `rich` content                                         |
-| allowed_mentions | [allowed mention object](#DOCS_RESOURCES_CHANNEL/allowed-mentions-object)            | allowed mentions for the message                                |
-| components \*    | array of [message component](#DOCS_INTERACTIONS_MESSAGE_COMPONENTS/component-object) | the components to include with the message                      |
-| files[n] \*\*    | file contents                                                                        | the contents of the file being sent/edited                      |
-| payload_json \*\*| string                                                                               | JSON encoded body of non-file params (multipart/form-data only) |
-| attachments \*\* | array of partial [attachment](#DOCS_RESOURCES_CHANNEL/attachment-object) objects     | attached files to keep and possible descriptions for new files  |
-
-\* Requires an application-owned webhook.
-
-\*\* See [Uploading Files](#DOCS_REFERENCE/uploading-files) for details.
-
-## Delete Webhook Message % DELETE /webhooks/{webhook.id#DOCS_RESOURCES_WEBHOOK/webhook-object}/{webhook.token#DOCS_RESOURCES_WEBHOOK/webhook-object}/messages/{message.id#DOCS_RESOURCES_CHANNEL/message-object}
-
-Deletes a message that was created by the webhook. Returns a `204 No Content` response on success.
-
-###### Query String Params
-
-| Field     | Type      | Description                        | Required |
-| --------- | --------- | ---------------------------------- | -------- |
-| thread_id | snowflake | id of the thread the message is in | false    |

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

@@ -1,88 +0,0 @@
-# Rich Presence Best Practices
-
-> 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.
-
-Rich Presence is a new feature from Discord that allows you to surface unique, interesting, and actionable data inside a Discord user’s profile when they play your game! This guide is intended to show some best practices on how to make that data the best it can be. It will include images and code samples; for full technical documentation, see our developer documentation.
-
-If you take away one thing from this guide, let it be this:
-
-> warn
-> Rich Presence data should give others a clear understanding of what someone is doing so they can decide if they want to play together or not.
-
-## Who should use Rich Presence?
-
-Rich Presence is a powerful way to integrate your game with Discord. To do it most effectively, you should think about its purpose and how well (or not) it matches with your game and your implementation. Rich Presence is designed for these three things:
-
-1. Show interesting, unique, actionable data in a user’s profile
-2. Allow friends to spectate each other’s games
-3. Join a friend’s in-game party or server directly from Discord
-
-We certainly don’t want to stifle creativity, especially for games that can use Rich Presence in an interesting way. However, keep in mind that this sort of gameplay is what it was designed for, and how players will normally interact with it.
-
-If you want to do something creative, wacky, funky, or otherwise out-there with Rich Presence for your players and aren’t sure if you can, feel free to drop us a line at [gamedevs@discord.com](mailto:gamedevs@discord.com). We’re always happy to help!
-
-## How should you think about the data you show?
-
-The data in your players’ profiles is the first thing that others on Discord will see about your game, both those familiar with it and those who have never played. It should answer two questions: can I play with my friend right now, and if not, when can I? Show data like:
-
-- What the player is currently doing
-- How much time has elapsed or remains (if applicable)
-- Their party state
-- Your cool artwork!
-
-For a great real world example, check out [Holodrive](https://store.steampowered.com/app/370770/Holodrive/) for free on Steam!
-
-## Tips
-
-### Keep it Short
-
-- `details` and `state` should be snippets of data, not sentences.
-- Make sure your strings stay on one line—especially on the small profile!
-
-###### Examples
-
-|                                       Bad                                                    |                       Good                                                                          |
-| :------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------: |
-| ![A rich presence string that is too long and does not fit on one line](rp-long-strings.png) | ![Screenshot of a good rich presence string that is concise and easy to read](rp-short-strings.png) |
-| The data wraps onto multiple lines. It’s repetitive, slower to read, and messy.              | The data all fits on one line per string. Clean!                                                    |
-
-### Make it Actionable!
-
-- Always keep party size data up to date.
-- Keep accurate track of party state: In Queue, In Game, In Menus, etc.
-- Include game modes, ranked vs. unranked, etc. so others can clearly see.
-
-###### Examples
-
-|                                           Bad                                             |                                          Good                                                                                                     |
-| :---------------------------------------------------------------------------------------: | :-----------------------------------------------------------------------------------------------------------------------------------------------: |
-| ![Screenshot of a rich presence string reading "Rank 9999"](rp-non-actionable.png)        | ![Screenshot of a good rich presence string shows a game mode of "Ranked: Control Point" and that the user is in a queue](rp-actionable.png)      |
-| While Rank 9999 is impressive, it doesn’t present any actionable data for their friends.  | This player is in queue for something I want to play. Let's ask to join that open spot!                                                           |
-
-### Use ALL of the fields (where applicable)!
-
-- Make use of all the fields that are applicable to you.
-- Save space by putting map and character names in the tooltips.
-- Try not to repeat information.
-
-###### Examples
-
-|                                          Bad                                                    |                                                Good                                                                             |
-| :---------------------------------------------------------------------------------------------: | :-----------------------------------------------------------------------------------------------------------------------------: |
-| ![Screenshot of a rich presence string that is hard to read at a glance](rp-not-all-fields.png) | ![Screenshot of a good rich presence that takes advantage of storing less important information in tooltips](rp-all-fields.png) |
-| The map name takes up space and makes the player's status harder to read at a glance.           | Moving the name of the map to the tooltip makes the data cleaner and frees up space for the score.                              |
-
-### Have interesting, expressive art!
-
-- The large image should be consistent for all players in a party.
-- The small image is where you can customize on a per-player basis.
-- Use high resolution artwork so your art looks great on fancy, high DPI screens.
-- We strongly recommend image sizes of 1024x1024 pixels.
-
-###### Examples
-
-|                                     Bad                                               |                           Good                                                       |
-| :-----------------------------------------------------------------------------------: | :----------------------------------------------------------------------------------: |
-| ![Screenshot of a rich presence icon that is too dark to see clearly](rp-bad-art.png) | ![Screenshot of a rich presence icon that is clear and detailed](rp-good-art.png)    |
-| The image is dark and unfocused. Highly-detailed images can be hard to see.           | This image is bright and matches the details. Let's help!                            |

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

@@ -1,45 +0,0 @@
-# Rich Presence FAQ
-
-> 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.
-
-Below are answers to some common questions about integrating Rich Presence with your game. If you don't see your question answered here, feel free to reach out to [gamedevs@discord.com](mailto:gamedevs@discord.com) for more help.
-
-#### Q: I see "Playing MyGame", but no Rich Presence data.
-
-There's a couple things that could be going on:
-
-- If you're running two instances of the Discord client, check both!
-- Double check that your `Discord_Initialize()` function is correct.
-
-Throughout development, make sure you have your `errored()` and `disconnected()` callbacks hooked up for debugging. You can open up the console in Discord and look for errors pertaining to `SET_ACTIVITY` for more information as well.
-
-#### Q: I'm not seeing Spectate buttons on my profile.
-
-Make sure you applied for approval! If you want the Spectate button on your players' profiles, we require your integration to go through an approval process. If you have applied and have been approved and still don't see the buttons, check your Discord console for errors.
-
-#### Q: What happens if someone has more than one game running that supports Rich Presence?
-
-Due to recent changes in our infrastructure for support of multi-activities, the behavior of multiple connected Rich Presence apps has changed from what it was before. Previously, whichever application was focused would be the presence that was shown. With the recent changes, the application that connected _first_ is now displayed.
-
-However, invite functionality across multiple connected applications now works no matter which app is display on a user's profile. For example, if you are hosting a Spotify listening party, playing Game A that allows you to send Join invites, and playing Game B that allows you to send Spectate invites, you'll be able to send invites to all three simultaneously!
-
-#### Q: What if someone looking at my profile or an invite doesn't own the game?
-
-Anyone can see your profile data, whether they own the game or not. They'll only be able to interact with chat invites or profile buttons if they own the game and have launched it at least once. Otherwise, the invite/button tooltip will show "Game Not Detected".
-
-#### Q: Do join invitations allow players to select the number of open slots?
-
-Currently, the SDK does not support this. Party slot information is determined by the party data you sent in your presence payload.
-
-#### Q: Can I send images via the payload rather than uploading them to my Developer Dashboard?
-
-Yes! In addition to uploading an asset and specifying its name, you can also specify an external image URL for us to proxy. For more information, see [Activity Asset Image](#DOCS_TOPICS_GATEWAY/activity-object-activity-asset-image).
-
-#### Q: Can I change something in the SDK for my own purposes?
-
-Go nuts! The SDK is open source by design. If you need or want to change something for the purposes of your specific integration—like changing our JSON parser, or changing all of the variable names to the names of your pets—go ahead and tinker to your heart's content.
-
-#### Q: OK—I've got it working! Now, how do I make my integration look _awesome_?
-
-I'm happy ~~we preempted your question~~ you asked! Check out our [Rich Presence Best Practices](#DOCS_RICH_PRESENCE_BEST_PRACTICES/) guide for a rundown on how to make your integration the best that it can be!