-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document Stage Instances. #2898
Conversation
|
||
## Auto Closing | ||
|
||
When a Stage channel has no speakers for a certain period of time (on the order of minutes) it will be automatically deleted. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For some extra color, this should be on average 10-15 minutes. The exact time is an implementation detail and will not be documented. (Since we might tune it without warning.)
The goal for us here is to not have lingering stage instances with basically no one in them. We found that for large Stages listeners just go AFK. In the future, we plan that ending a stage instance will kick everyone out of the stage.
fe44299
to
99d10c2
Compare
* feat: implement stage instances Reference: discord/discord-api-docs#2898 * feat: implement stage instances * Update src/types/misc/stage_instance.ts Co-authored-by: ITOH <[email protected]> * Update src/helpers/misc/delete_stage_instance.ts Co-authored-by: ITOH <[email protected]> * Update src/types/misc/stage_instance.ts Co-authored-by: ITOH <[email protected]> * Move stage instances related modules to channels module * Move to channels * Move to channels * Add permission checks * Add permissions checl * Ad inhibitors * style: fix lint warnings * Do not throw & add import type Co-authored-by: ITOH <[email protected]>
This commit adds support to creating, editing, getting, and deleting stage instances. See discord/discord-api-docs#2898 and discord/discord-api-docs#2933
Now presenting the sequel to Stage channels documentation, Stage instances!
Summary
Status: APIs are already available.
While developing, you may notice some more fields than what are documented. This is because we're still working on this stuff right now. We'll be incrementally documenting more and more fields as they become finalized and production ready. Please ignore every un-documented field.
Our main motivation of getting this PR out early is that we've started noticing bots changing the Stage channel's topic to programmatically edit the Stage topic. This is currently fine*, but it will probably break in the near future (on the order of weeks? I know this is a super fast change). So if you're doing that, we would much prefer people hack on this API instead. FWIW this is the reason why I didn't document topic behaviour in the Stage channels PR.
* We currently have compatibility code which means changing channel topic <-> changing stage instance. And that's the thing we're looking to remove soon.
Future stuff