Make GUILD_CREATE on IDENTIFY optional

[Skillz4Killz]

Hello 👋

Please provide an option on IDENTIFY to disable the mass sending of GUILD_CREATE payloads. The option can be defaulted to enable which would prevent any breaking changes or causing issues for any bots/libs that don't want to support or need this.

Benefits For Those That Opt To Disable

• Potentially remove the 5s delay for each shard to identify because Discord may not need to give its databases time to make all those requests to get guilds, channels...
  • Near 0 downtimes
• Decrease bandwidth usage as some bots may have already stored them and maintain the cache as needed
• Decreased amount of CPU usage on startup as CPU usage compared on startup vs normal operations can vary quite a bit leading to buy more expensive hardware to support the needs for something trivial as keeping a persistent cache. RAM is cheaper than CPU.

Potential Solutions:

• Have IDENTIFY accept a seq similar to what RESUME accepts? If valid seq is provided in IDENTIFY > DO NOT SEND guild creates just send the events from that sequence. this way i think it would be safe even if downtime wasnt 0 per say. Just to reiterate the only benefit out of all this is if getting rid of the GUILD_CREATE events could help remove the 5s delay. If that delay cant be removed, it doesnt make sense to not get these events
• REQUEST_GUILDS (similar to REQUEST_GUILD_MEMBERS) which you can get chunks of guilds coming in. Basically you could pass in an array of ids for which guilds u need. Probably with a low rate limit to prevent abuse

[jhgg]

This is not going to happen. The reasons why it works the way it does is for good reason right now.

We will be sending GUILD_CREATE to bots for the foreseeable future. The 5 second delay is not going away as it's necessary to throttle connections to our internal systems as well.

[erkinalp]

The reasons why it works the way it does is for good reason right now.
We will be sending GUILD_CREATE to bots for the foreseeable future.

Is it because bot and C-S APIs are not completely separate from each other and there is shared infrastructure and codepath handling both bots and humans?

[key2peace]

In my opinion, this isn't even needed, depending on the session timeout, you could RESUME the connection using the session, sequence number and resume_gateway_url, load your guilds from cache and be happy.

[muddyfish]

Having optional initial guild creates and an opcode for requesting guilds would be very helpful for me. Especially after some downtime, but not enough that the cache is completely wrong