Can't enable Privileged Intents on private bots with fewer than 100 guilds

[jagrosh]

Description
Bots that are on fewer than 100 guilds, but have ever been on more than 100 guilds, are unable to enable privileged intents.

Steps to Reproduce

1. Run a bot for 5 years
2. Experience slow natural growth
3. Manually have bot leave all but 99 servers
4. Attempt to enable privileged intents

Expected Behavior
It was expected to be able to enable privileged intents once the bot was on fewer than 100 guilds

Current Behavior
The boxed for privileged intents are still disabled.

Screenshots/Videos

Client and System Information
Firefox/Windows

[night]

To prevent potential abuse, once a bot is required to submit verification it is no longer possible to toggle these flags on the client side. If you have other issues precluding you from verifying I would recommend reaching out to our support team at https://dis.gd/contact

[jagrosh]

Frankly, this information would have been nice to know as soon as the verification system was announced, so that people could have pre-pruned their bots to below the threshold so as to not render the bots useless now. Lots of "hobby-project" bots (that are likely not qualified to be verified) were previously public for ease of adding for friends, but if they happened to hit 100 guilds, they will be permanently broken as of today.

[jagrosh]

As an addendum, there are several reasons why someone might intend to keep a bot unverified:

• They want to be able to change the bot's username
• The bot is not kept online consistently enough to merit verification
• They intentionally want a hard limit on the number of guilds a bot is in (ie keep hosting costs minimal)
• Their bot's feature-set changes or is inconsistent (hobby-project bot)

If a bot that is intentionally unverified, or not eligible for verification, happened to hit 100 guilds before today, that bot will now be permanently unusable.

[Ratismal]

Really? That's it? If the scope of your bot changes to need these intents in the future after verification, you're screwed, thanks for playing? The thought that people might want to reapply for these intents never crossed anyone's mind? This feels like an incredibly hostile decision, and I'd urge you to reconsider.

@Ratismal hmm, what? you can always apply for more intents after you're already verified.

[advaith1]

night's comment is only for enabling limited intents (for small bots); for requesting whitelisting the process is currently making a support ticket and it'll be added to the dev portal in the future

[msciotti]

This is both a migration issue and an abuse issue. On our end, applications are in one of four states when it comes to verification

- Ineligible (have not met the 76 guild requirement)
- Unsubmitted (you, at some point, crossed that threshold)
- Submitted (you have an active application submission)
- Approved

Right now, the code is checking if you are in an ineligible state to be able to flip those toggles. Otherwise, you cannot.

If we were to make it check for unsubmitted as well, it would open up the abuse vector of allowing unverified bots in > 100 servers to keep this privileged data on the v6 gateway, since we are only checking for the flags (intents are not mandatory on v6).

---

This is all a long way of saying that before we go spend a bunch of time changing the system and dealing with the abuse cases that will occur, for how many people is this a problem? I know that your bots are in a unique case. Perhaps we can see if we can just handle this manually, as it won't be an issue for new bots going forward?

---

EDIT: Also,

Really? That's it? If the scope of your bot changes to need these intents in the future after verification, you're screwed, thanks for playing? The thought that people might want to reapply for these intents never crossed anyone's mind? This feels like an incredibly hostile decision, and I'd urge you to reconsider.

No, that's not how that works. You can apply for intents at any point in the future if you need them by following up on your verification request email.

[advaith1]

Can't it just be purely tied to guild count, checking if it's below 100 or not? That's what it was implied to be before

[msciotti]

Can't it just be purely tied to guild count, checking if it's below 100 or not? That's what it was implied to be before

This is an expensive query for us to do. On OAuth pages, we keep an estimated count. An exact count of above/below 100 is expensive to compute, and we have flags specifically for this reason.

[jagrosh]

I agree that this is likely does not affect a large percentage of bot developers, and with the new knowledge of how this works, hopefully it can be avoided in the future. Therefore, handling it manually for existing cases sounds reasonable. For people this affects, should we open a support ticket?

If we were to make it check for unsubmitted as well, [...]

For that case, I'd highly suggest being able as a dev to limit your bot's server count, as to never hit the 76 guild requirement (and cross into the unsubmitted category, thus never being able to enable privileged intents)

[advaith1]

• Unsubmitted (you, at some point, crossed that threshold)

This doesn't necessarily mean they can apply though; if you drop below 76 before submitting, then it will not let you submit the application, but it seems that it also prevents you from enabling limited intents. Someone actually encountered this issue in DDevs (link).