Skip to content
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

Single-channel Chat Focus #264

Open
vegeta897 opened this issue Dec 24, 2020 · 2 comments · May be fixed by #276
Open

Single-channel Chat Focus #264

vegeta897 opened this issue Dec 24, 2020 · 2 comments · May be fixed by #276

Comments

@vegeta897
Copy link
Member

In my experience, I have noticed that D-Zone is best enjoyed when a group of people are looking at it together and chatting about it. This typically happens in a single channel.

Instead of D-Zone displaying chat messages from all channels in a server, it should instead be designed for that single channel experience. This will be "the D-Zone channel" in the server. Whether the channel's topic is exclusively D-Zone or not doesn't matter.

This removes the myriad design issues with handling multi-channel chatter in the client. We don't have to deal with huge lists of channels in big servers, and we don't have to deal with confusing cross-talk.

But a server full of people chatting outside of the D-Zone channel should still feel alive in D-Zone. So we can show the cubes visibly chatting, but not show the messages they are sending.

Maybe eventually we provide users an option to "tune in" to a different channel in the D-Zone client, but the main idea is the single channel experience.

@SagnikPradhan SagnikPradhan added this to To do in Rewrite via automation Dec 24, 2020
@yellowberryHN
Copy link

I agree that this is a good idea. However from what I understand, it can already somewhat be achieved by limiting the bot to viewing one channel, correct?

@vegeta897
Copy link
Member Author

I agree that this is a good idea. However from what I understand, it can already somewhat be achieved by limiting the bot to viewing one channel, correct?

That is correct! The motivation behind opening this issue is a matter of design and intended experience rather than what is possible through the config.

@SagnikPradhan SagnikPradhan linked a pull request Jun 6, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Rewrite
  
To do
Development

Successfully merging a pull request may close this issue.

2 participants