Edit history

Sequel to https://feedback.fluxer.com/p/1048/bot-sharding-capabilities, which seems to ask for sharding to exist at all. The /v1/gateway/bot endpoint https://docs.fluxer.app/http-api/gateway/#get-gateway-information claims to return a recommended bot shard count. But per https://docs.fluxer.app/http-api/gateway/#gateway-information-object and https://github.com/fluxerapp/fluxer/blob/main/fluxer_api/src/api/gateway/GatewayRequestService.ts#L44, it's hardcoded to 1. https://docs.fluxer.app/gateway/limits-and-rate-limits/#session-lifecycle says a bot shard cannot have more than 2500 guilds, so a 2501-guild bot that follows the recommendations just gets an infinite reconnect loop. Linearly interpolating https://web.fluxer.app/channels/1427764813854588940/1427764813854588943/1561156058397802496 and https://web.fluxer.app/channels/1427764813854588940/1483532018185537313/1565010595109928960 (both in Fluxer Developers guild) says that if the Vinto bot was in 1971 guilds on October 18, and 2127 guilds on October 28, then it will reach 2500 in 24 days, on November 21. (The bot could ignore the Get Gateway Information endpoint and hardcode a shard count, but that's not gonna scale well once other bots reach 2500, or when Vinto reaches 5000.)

/v1/gateway/bot should return a shard count dependent on bot guild count. (The obvious answer would be guild count divided by 1000 or 2000 or 2048 or whatever, rounded up.)