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

spacer channels #3384

Open
cknost opened this issue Mar 27, 2018 · 3 comments
Open

spacer channels #3384

cknost opened this issue Mar 27, 2018 · 3 comments
Labels
client feature-request This issue or PR deals with a new feature good first issue Good for first-time contributors

Comments

@cknost
Copy link

cknost commented Mar 27, 2018

Hello,
i wish spacer channels like on Teamspeak for example: [cspacer]

image

@ghost ghost added the feature-request This issue or PR deals with a new feature label Mar 27, 2018
@cknost cknost changed the title [cspacer] channels spacer channels Mar 27, 2018
@toby63 toby63 mentioned this issue Mar 23, 2020
@maxhambraeus
Copy link

I think this feature, and a few others mentioned in #3608, would do a lot for the general usability and user-friendlyness of mumble. To me this seems pretty straight-forward to implement, but I don't know anything about the codebase.

@Krzmbrzl Krzmbrzl added the good first issue Good for first-time contributors label Apr 2, 2024
@Krzmbrzl
Copy link
Member

Krzmbrzl commented Apr 2, 2024

I think this could likely be achieved by creating the channel with ACLs configured such that nobody can enter it and (optionally) with a predefined name that visually marks the channel as a spacer channel.

Effectively, this should already be achievable without code changes but having UI support for setting everything up as required with one click seems desirable.

If someone wants to give implementing this a shot, let me know and I could elaborate a bit more.

@Hartmnt
Copy link
Member

Hartmnt commented Apr 2, 2024

Effectively, this should already be achievable without code changes but having UI support for setting everything up as required with one click seems desirable.

True, but I would argue that this feature would be a lot nicer to use, if there were code changes. Let's say there are some hard-coded channel names for space channels e.g. [cspacer]
In the client, we could use an item delegate thingy to draw a nice line or whatever without necessarily depending on fonts or Unicode. Instead of not having the permission to enter, the client would not even give the user the option to join the channel. With regards to accessibility, the clients using screen readers could read "spacer channel" instead of "dashdashdashdashdash" ;)
There are probably some server side things to consider, too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client feature-request This issue or PR deals with a new feature good first issue Good for first-time contributors
Projects
None yet
Development

No branches or pull requests

5 participants