Accept nonce when executing a webhook

[advaith1]

Currently, the Create Message endpoint accepts the nonce field and includes it in the sent message, but the Execute Webhook endpoint does not accept the nonce field.

The nonce field is useful for matching new messages with stored unsent messages. It would be useful for applications that use webhooks to send messages to channels. The messages can be matched using the content, but this is not fully reliable due to Discord's message normalization, which is likely why the client sends the nonce field.

[jhgg]

The nonce field is used for optimistic message sending, something that I don't think webhooks even care about. The nonce is not stored anywhere, and is only used to match a MESSAGE_CREATE event with a pending http request. Additionally we also use the nonce to dedupe retried messages within a small time window.

Given this context, I'm not sure why nonce would need to exist on webhooks. The use-case you provide seems to be trivially accomplishable by recording the message id.

[MinnDevelopment]

Additionally we also use the nonce to dedupe retried messages within a small time window.

Would this not also apply to retried webhook messages?

[jhgg]

Perhaps - our use-case really for this is deduping messages sent on bad mobile networks.

[MinnDevelopment]

Also, I think it could also be useful for interaction follow-up webhooks, no?

[advaith1]

The nonce field is used for optimistic message sending, something that I don't think webhooks even care about.

Sorry if I wasn't clear; this is my use case. The application in question uses a bot and sends messages using bot-created webhooks (like many others).

The use-case you provide seems to be trivially accomplishable by recording the message id.

not sure how the ID is relevant here? since that's only generated when the message is sent

[ghost]

If you send a nonce, you can store the nonce before sending it to Discord, thus having an unlimited time between requesting a message send and waiting for a message create.
if you rely on the message ID, it is possible that you get the message create before getting the message ID back, which can cause issues if you start waiting for a message with a certain ID after you already received it.