Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Message forwarding #6833

Merged
merged 12 commits into from
Jul 16, 2024
Merged

Message forwarding #6833

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
12 commits
Select commit Hold shift + click to select a range
3fafad6
[docs] Message Forwards feature
lytefast Apr 23, 2024
352e211
udpate how reference pseudo types are defined
lytefast Apr 23, 2024
d18f72d
multi snapshots + forward restrictions
lytefast Apr 26, 2024
bf6d515
table formatting lint is too damn sensitive
lytefast Apr 26, 2024
41f5329
field name split blockquotes
lytefast Apr 29, 2024
c2cabda
better formatting and some grammer cleanups
lytefast Apr 30, 2024
aa04692
add changelog
lytefast Jul 12, 2024
2bd7447
suggestion updates
lytefast Jul 15, 2024
c66ea82
Update docs/resources/Channel.md
shaydewael Jul 16, 2024
8a88695
Update docs/resources/Channel.md
shaydewael Jul 16, 2024
40bda3a
Update docs/resources/Channel.md
shaydewael Jul 16, 2024
2d38dd4
Update docs/resources/Channel.md
shaydewael Jul 16, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 38 additions & 0 deletions docs/Change_Log.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,43 @@
# Change Log

## Message Forwarding rollout

#### July 15, 2024

We are slowly rolling out the message forwarding feature to users. This feature allows callers to create a message using `message_reference.type = FORWARD` and have the API generate a `message_snapshot` for the sent message. The feature has [some limitations](#DOCS_RESOURCES_CHANNEL/message-reference-types) and the snapshot is a minimal version of a standard `MessageObject`, but does capture the core parts of a message.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
We are slowly rolling out the message forwarding feature to users. This feature allows callers to create a message using `message_reference.type = FORWARD` and have the API generate a `message_snapshot` for the sent message. The feature has [some limitations](#DOCS_RESOURCES_CHANNEL/message-reference-types) and the snapshot is a minimal version of a standard `MessageObject`, but does capture the core parts of a message.
We are slowly rolling out the message forwarding feature to users. This feature allows to create a message using `message_reference.type = FORWARD` and have the API generate a `message_snapshot` for the sent message. The feature has [some limitations](#DOCS_RESOURCES_CHANNEL/message-reference-types) and the snapshot is a minimal version of a standard message object that only captures the core parts.


The resulting message will look something like:
```json
{
"id": "1255957733279273083",
"message_reference": {
"type": 1, // Forward
...
}
"message_snapshots": [
{
"message": {
"content": "original message",
"embeds": [...],
"attachments": [...],
...
}
}
],
...
}
```

We have applied stricter rate limits for this feature based on the following:
- number of forwards sent by the user
- total attachment size

###### API Updates since preview

This was [previously announced](https://discord.com/channels/613425648685547541/697138785317814292/1233463756160503859) but note that the final API has a few changes since the API was first previewed:
- [`message snapshot`](#DOCS_RESOURCES_CHANNEL/message-snapshot-object) objects don't include a `guild` field anymore since the `message_reference` already provides that information
- forwarded messages have a distinctive `message_reference` type of `FORWARD` now

## User-Installed Apps General Availability

#### June 27, 2024
Expand Down
2 changes: 1 addition & 1 deletion docs/interactions/Receiving_and_Responding.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -154,7 +154,7 @@ All options have names, and an option can either be a parameter and input value-
This is sent on the [message object](#DOCS_RESOURCES_CHANNEL/message-object) when the message is a response to an Interaction without an existing message.

> info
> This means responses to [Message Components](#DOCS_INTERACTIONS_MESSAGE_COMPONENTS/) do not include this property, instead including a [message reference](#DOCS_RESOURCES_CHANNEL/message-reference-object-message-reference-structure) object as components _always_ exist on preexisting messages.
> This means responses to [Message Components](#DOCS_INTERACTIONS_MESSAGE_COMPONENTS/) do not include this property, instead including a [message reference](#DOCS_RESOURCES_CHANNEL/message-reference-structure) object as components _always_ exist on preexisting messages.

###### Message Interaction Structure

Expand Down
Loading