[Intents] More Granular Gateway Intents

[Skillz4Killz]

Hello 👋

Have you guys ever considered more granular intents? What i mean is more control of events like selecting which guilds could send certain events. For example, suppose i want to implement a "VIP SERVER only feature" like Server Logs. I don't necessarily want to enable every intent on every single server on the bot. I just want those events on specific servers that opt into this feature.

Thank You

[cakedan]

I don't think this is feasible at all with discord's current design unless they add a bulk intent update event you can send in. Having 2k guilds per shards, that would mean sending in 2 thousand individual intent override events for this feature. Seeing as how they removed bulk-guild member requests, I don't think they like having an event you can send in with multiple guild ids. A re-identify would refresh the intents as well. Sending in a list of 'guildId: intent' on the identify payload wouldn't work either since you might not have that guild id on that shard.

How would you see if you have intents enabled on a certain guild? They'd have to send you an event with your intents per-guild.

It's a good idea but I don't see a good way, from a users end, for this to be a feature.

[Mehgugs]

I'd like to point out that this use case is possible to implement with proper oauth2 scopes.

With a full oauth2 flow you can implement an initial step to identify your user (i.e log in with discord) then request a bot scope with the optional features (there's still a bit of work to do if they lose VIP status though).

For example, with slack's api sending a user through authorization again to upgrade a bearer token based on some context in your service is a recommended practice.