Improve visibility of button presses, or allow multiple actions in a single HTTP interaction reply

[jagrosh]

Since switching to the HTTP-only system, a massive number of users have complained that it isn't clear if they've pressed a button (for example, this kind of feedback is common). For reference, when a user presses a button, the reply to the interaction contains the updated message content (which shouldn't invoke any ratelimits, as there is no request to Discord being made). The volume of button presses would make creating an additional response (such as an ephemeral message in addition to the original message edit) not feasible due to ratelimits (for example, button presses could easily exceed 50 presses per second). There are a few ways I could imagine this could improve:

Make it more obvious a button has been pressed

For example, when an interaction is successfully replied to, make the button glow, show a checkmark, or other visual indicator that it has been clicked and successfully processed.

Add a new button type

Whether this would be a "toggle" style button, or allow setting the style of the button per-user, changing the button permanently after a click would be beneficial.

Allow including two messages in the reply to an interaction request

A possibly-simpler method would be to simply allow both an edit as well as a new message in a single reply to an interaction. This would allow editing the original message, as well as creating an ephemeral "confirmation" that the button has been successfully pressed.

[AJman14]

I really wish I could give this multiple upvotes. Either we need better visibility of our interactions, or bots need multiple free requests per interaction.

Edit: Lol, I realize I basically just typed out your exact title.

[Zoddo]

The volume of button presses would make creating an additional response (such as an ephemeral message in addition to the original message edit) not feasible due to ratelimits (for example, button presses could easily exceed 50 presses per second).

Interactions/followups are webhooks under the hood. This means they have their own ratelimits and don't count towards the bot's global ratelimit, as documented here.
And I'd like to point that even if they counted against the global ratelimit, GiveawayBot is large enough to request an increased global ratelimit :)

But I agree that there should be a way to retain that a user clicked the button, and show a slight visual indication of that.

[jagrosh]

They may not count against the global ratelimit, but multiple interactions editing the same message via deferred or follow-up interaction requests still will hit ratelimits as far as I am aware.

[TrulyLife420]

This is also a issue for the people who are doing the giveaways knowing who entered as well before the giveaway is done!

[TrulyLife420]

Not knowing who entered means not knowing who to let know that there is a giveaway!

[JetCrooked]

gotta love how this issue is still unanswered after all this time