Allow bots to disable themselves

[erkinalp]

As simple as allowing them use the already existing /users/@me/disable.

[advaith1]

...why?

[splatterxl]

I would assume adding a simpler way to disable the bot based on tokens spotted in the wild instead of "this token was found in a random cryptic github repo"

[ftilly]

The proposed here would end up to always use the users and low latency with username and/or user could cause much stricter, preventing the teams. Reuses existing data mining by granting ADMINISTRATOR.

[AEnterprise]

if this is for token leaks this sounds like it will cause more confusion then help people. how would re-enabling it work? would this prevent users from adding the bot to the server? what would that error look like without making those users think the bot no longer exists or isn't coming back?

having a dedicated endpoint for users to submit leaked tokens and trigger a token reset and alert the owner sounds like a much better developer and user experience to achieve this

[erkinalp]

how would re-enabling it work?

That one could be done from the developer panel instead.

trigger a token reset

The thing is disabling the bot as proposed here would also revoke the token without generating a new one.

would this prevent users from adding the bot to the server? what would that error look like without making those users think the bot no longer exists or isn't coming back?

Yes it should. "This application is temporarily disabled for an unknown period, hence it cannot join any guilds at the moment. If you have questions on why this application is disabled, contact the maintainer at {support.guild.invite}." (?)

[AEnterprise]

this sounds needlessly complex when just a token reset (like already exists, they would just have to expose an endpoint for it) can achieve the same goal with less confusion. it would only require an amended/clarified system dm template rather then all of the above and be much simpler for both bot developers as well as bot users