Discord bot used for Quilt's day-to-day tasks. Discord avatar based on Feuerfuchs blobfox emoji at https://www.feuerfuchs.dev/en/projects/blobfox-emojis/
I forgot to make an issue for this, so let's make one now.
As discussed in a Discord suggestion, I believe we can do better with our voice channels. Voice channels are often made use of for a specific purpose, but many people make use of them in different ways - and often not in the ways that the group originally using the channel expects. This can result in users disrupting the conversation or activity, and generally causing problems unintentionally.
I proposed that this is a function of how we handle voice channels, and I think we can work around it by creating a Cozy module to automatically handle voice channels. It should work something like this:
User joins a "Lobby" voice channel. Cozy creates a voice channel for them, and moves them into it.
The user that created the channel is given access to logged management commands that allow them to set the name, prevent non-staff users from joining them, manage simple permissions, set limits on the number of users allowed to join, change the region, disconnect other users, and so on.
Users making use of the channel may use Text-in-Voice to chat without using their microphones.
When the channel becomes empty, Cozy temporarily archives it, generates a file containing all of the messages and information sent in the thread, uploads that file to a log channel, and deletes the channel.
Approaching voice channels in a dynamic way like this should result in less general voice disruption and a better way to signpost what a channel is for.
I forgot to make an issue for this, so let's make one now.
As discussed in a Discord suggestion, I believe we can do better with our voice channels. Voice channels are often made use of for a specific purpose, but many people make use of them in different ways - and often not in the ways that the group originally using the channel expects. This can result in users disrupting the conversation or activity, and generally causing problems unintentionally.
I proposed that this is a function of how we handle voice channels, and I think we can work around it by creating a Cozy module to automatically handle voice channels. It should work something like this:
Approaching voice channels in a dynamic way like this should result in less general voice disruption and a better way to signpost what a channel is for.