Allow bots to send up to 4k characters in a message or the description field in embed.

[applebee1558]

Description
Increasing the message content length limit to 4000 characters to be consistent with user accounts that have nitro.

Why This is Needed
People can log moderation cases, or forward messages to the staff team directly, and the bot does a exact copy of the message. Now, if a nitro user sends over 2k characters in a message, it causes the api to reject the forwarded message to staff because it exceeds 2k characters.

Alternatives Considered
Sending multiple messages to bypass it? It's ugly and triggers more ratelimits.

Additional Details
I would also request an increase in the description field in an embed, as I use that for quoting other people's messages and the limit makes it impossible to quote a full message.

[GoldenAngel2]

Imo both the content length and description length need to be upped.

Not only for bots that echo another user's message, but also for logging and automod bots.

Currently for logging bots we either have to split up the messages into multiple parts.. or if it's over the 6k embed length you have to send multiple messages. Which isn't good for ratelimits and looks terrible in the logs aswell.

Same thing for automod bots

A good example would be messageUpdate event. Logging both parts it needs to split up a ton for both old and new messages to be displayed in the logs. (as it could be more than 8k characters)
Example of trying to log a 4k message edit: https://i.vgy.me/0eg4C0.gif

Hopefully this adds more use cases for this feature request.

[ghost]

it'd also be good for webhooks to be able to send 4k characters in a message, since webhook messages (both content and embeds) are also used to echo or proxy users' messages

[jpbberry]

I definitely agree with this change, my bot, one that's made to delete messages with swears, would constantly get complaints about it removing long messages like rules before I moved it to use embed description. I can see this happening again for nitro users who send with their nitro 4k messages.

[GoldenAngel2]

Semi-update: description has been updated to 4096 max characters

Nothing for message content yet.

[msciotti]

The description field has indeed been updated to 4096 characters to solve the use case of logging and moderating messages.

We aren’t going to be upping the content length for bots or webhooks at this time, but are considering how nitro features interact with bots more holistically moving forward.

[jpbberry]

Curious what your use case is @muddyfish

I definitely could use it because of sending users messages via webhook. I have a resend feature on my swear word blocking bot, that sends a users message again but with all the curses blocked out, 4k messages definitely couldn't do that unless this was applied. And things like tupperbox for example who make fake users, also uses webhooks. Bit complicated.

[muddyfish]

Curious what your use case is @muddyfish

I repost messages other users send and add rich content, such as images, markdown URLs, URL buttons and cross channel replies.
These get reposted using webhooks attributed to the original user, and it would be great for it to work for users with Nitro

Edit: In general, any bot which 'edits' user messages in this way would benefit from this feature

[AnotherZane]

Curious what your use case is @muddyfish

It's also used by bots that proxy messages to assist users with plurality. Pluralkit would be an example of this.

Furthermore, it I think it would make sense that bots and webhooks which have actual practical uses and are meant for automating tasks, etc have a larger content length.

[Rapptz]

Curious what your use case is @muddyfish

It's not uncommon to have input -> output commands currently where you take in input expecting you to be able to mirror it. e.g. tags, echo commands, logs that aren't in embeds, etc. Right now this stuff is now broken and needs to be updated with manual checks when it wasn't necessary before.

[elderlabs]

I would suggest the use-case is logging in a means that isn't "terrible to look at" (my staff team's words, not mine) when reviewing a chain of logs. Not all of us are comfortable or find ease reviewing a thousand embeds at a time. It's wasted "real-estate" in the sense of screen space. As a compact-mode user, I (and most of the moderation teams I work with) find it much easier to scan through a few hundred logs at a time in our large guild for content that needs action, rather than scrolling through a list of embeds that eat at screen space. I've tried both solutions and find it much easier to review non-embedded content.

It's also fairly inconsistent to up one limit, but not the other, when the other has been upped for users (also consistency in the case of bots having access to most Nitro features). Sure, the description limit was upped (which I am grateful for -- though have no current use for), but not doing the same for the content limit would appear to favor embeds. In this case, I'd ask why the the content length shouldn't be equally upped. The immediate argument that comes to mind would be for spam from bots, but that seems like it would be a moot one, as embeds would be equally exploited with the new limit, and so I'm left at a loss.

TL;DR for what reason shouldn't the content length also be upped on the bot API's end? Surely there's no risk involved here. Would someone please enlighten me?