Expose Role Endpoints to Bots

[Jupith]

It would be super handy if bots could use /guilds/../roles/member-counts and /guilds/../roles/../member-ids, the client already uses these endpoints in the roles UI, but sadly bots cannot access them. I don't see any downsides to giving bots access.

[RedDaedalus]

I believe the stance on these endpoints was that they were performant enough for client use, but at the scales bots operate on they're too unstable.

[ilxlodev]

👀 #2610 (comment)

[Jupith]

👀 #2610 (comment)

Key word being yet, february was a while ago, I hope things have perhaps changed

[joe27g]

Have there been any changes regarding this (in the past 1.5 years?)

I think there are many strong arguments for implementing this:

• The bots team supposedly wants this to happen already (per this comment on Endpoint to get Role Members #3269)

• To avoid performance issues on the /member-ids endpoint, it could simply be paginated with a small limit (i.e. 50 or 100 members per page.)

• As an alternative to exposing the /member-counts endpoint, perhaps Add memberCount in the Role #3306 could be implemented with little performance impact by caching the count upon member role updates.

• The addition of privileged intents since these issues were created means /member-ids could be restricted to prevent malicious use cases.

• Fetching all members in some/all guilds is objectively bad for both the Discord API and bots themselves, but it's necessary for certain use cases.

It seems especially odd to bury this feature due to performance concerns considering that the /guilds/:guild_id/prune endpoint has, in my limited experience, much worse performance than both of these proposed endpoints, yet is available to bots. In my server with 5k members, getting the prune count takes about 5-8 seconds depending on options, while getting role member counts takes between 100-250ms.

[ecrocombe]

Plus 1;

Use case:
We have an economy system, and we want to give points to all members in a role.
Currently using /guilds/{guild.id}/members and filtering the list client side by role id, which is surly more of a performance hit, on both server and client than /guilds/{guild.id}/roles/{role.id}/member-ids