-
Notifications
You must be signed in to change notification settings - Fork 4
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
More automatic voice channel management #70
Comments
Having all occupied voice channels public means they're going to clutter up the sidebar, even more than text channels because of listing the people in them. And it will make it harder to find the voice channel for the puzzle I'm working on (I often misclicked on wrong voice channels when I was subscribed to multiple puzzles at once). I like the idea of somehow knowing where people are in voice channels, because I do miss being able to have puzzle solving background noise, even if I'm working on something else. But I think this would not be the most usable solution. Also, if all occupied voice channels were public, I don't think I'd want to automatically be added to the text channel just because I happened to click the voice channel. |
I agree with Sparky on this one. But I do understand the desire to want to know at a single glance what's actively being worked on. I don't think the current |
I don't know what the metric currently used by the activity tracker on Herring is, but possibly if there were something like that per-puzzle that showed me which ones had people in voice channels would be good? |
I tried to talk about this in #52 but the whole way we expose presence is basically nonsense. The dark "people" icon in Herring represents people who have typed in text chat in the last two hours. The little sparkline also represents activity in text chat and also activity on spreadsheets (I think). #52 addresses adding voice chat membership to these, but it has a different model so it was harder than it looked and I didn't do it. |
Proposed:
The text was updated successfully, but these errors were encountered: