Expose bot's guild count on /oauth2/applications/@me

[kevinbioj]

Currently, a Discord bot can know its guild count by looking at how many guilds it has in its cache.
However, not all sharded bots are able to communicate (maybe because they don't need it, or there are infrastructure limitations) which makes knowing the global guild count a bit tricky.

It could also be an issue if an external service (dashboard ?) wants to get the guild count without having to communicate with the bot itself (what about possible outages).

We can estimate that count by multiplicating a shard guild count by the number of shards, but that's still an approximation that might be wrong. If for whatever reason a bot has to get an exact count, the shards must be able to communicate between them.

It looks like Discord can get the guild count since it is actually being showed in the bot authorization page, so it could be cool if that property could be exposed in the application object with a parameter like guild_count.

I have not seen any issue about that here so I opened it, hope I haven't missed it if it does exist.
Feel free to debate...

[jhgg]

We can estimate that count by multiplicating a shard guild count by the number of shards, but that's still an approximation that might be wrong. If for whatever reason a bot has to get an exact count, the shards must be able to communicate between them.

We do something similar on our end as well. The exact count of bot guilds is unknown once a bot gets large enough.

We can definitely provide an approximate count, but not an exact count.

[erkinalp]

Did you consider sth like "get current shard's guild count"?

[jagrosh]

Bots that only use interactions (and don't connect to the gateway) don't have shards.

[renhiyama]

That explains why the count shows up as approx lol

[kevinbioj]

We can estimate that count by multiplicating a shard guild count by the number of shards, but that's still an approximation that might be wrong. If for whatever reason a bot has to get an exact count, the shards must be able to communicate between them.

We do something similar on our end as well. The exact count of bot guilds is unknown once a bot gets large enough.

We can definitely provide an approximate count, but not an exact count.

I understand 👌
In that case yeah providing the approximate count could be a good thing since it can be used for many things such as dashboards or bot list updates.

[advaith1]

As an expansion, would it be possible to expose this in the Get User endpoint, so you can get any bot's server count via the API?

[castdrian]

As an expansion, would it be possible to expose this in the Get Bot endpoint, so you can get any bot's server count via the API?

I disapprove. I wouldn't want everyone to just have access to this without me knowing it. Even if it's just a number.

[advaith1]

Users can already access it anyway on the OAuth invite page, this would just be to access it via the API

[castdrian]

That's just you assuming everyone has access to my bots oauth page. Private stuff shall stay private.

…

On Fri., May 15, 2020, 01:14 Advaith, ***@***.***> wrote: Users can access it anyway on the OAuth invite page, this would just be to access it via the API — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1628 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFI3T7UPGMMDLVS4H327F73RRR3NHANCNFSM4NA3GW2A> .

[Taarek]

You only need the client ID to get to your bot's oauth page. Which would a get bot endpoint require too.

[TheArcaneBrony]

Extension to Taarek's comment: this also works with bots that are set to private!

[MeguminSama]

I'm going to +1 this. Exposing approximate_guild_count like on /oauth2/authorize would be extemely useful for bot lists.

[renhiyama]

While Discord is trying to kill bot lists, you're suggesting ways to help them lol

[jagrosh]

With the upcoming partial deprecation of message content, many bots are switching to a rest-only system. Right now, it seems impossible to get this number without connecting to the gateway; can adding this be re-evaluated? An approximate count would be good enough for most use-cases.

[renhiyama]

It seems the api part has been already created by the discord team. But it is user scoped only, thus making it impossible for bots to view this non-personal data.
(/api/oauth2/authorize?client_id=${bot.id}&scope=bot)
If and only if discord could make this available to everyone...
This endpoint also provides additional bot information such as tags, description too.
But it also provides all the guilds the user is in, in the response, so discord team please don't add the guilds array for bots too, otherwise our public bot would go brrr with long response~

[advaith1]

the current bot's guild count is finally exposed, in the new /applications/@me endpoint (#5971)

[cptpiepmatz]

This is sick!