Guess why it's called Mumble? TBH, on contemporary hardware it is so minimal, that I don't see a problem in using another program for texting in parallel that is more fitting for your needs, if those of Mumble don't suffice.
Guess what people do in voice chats. They come and go, post links or sometimes write when not being able to talk right now. Privately and in the current channel (seperate things).
Having server messages combined with user messages and channel messages is not sane. This has nothing to do with "better suits your needs". Teamspeak (and others) solve this with tabs.
I didn't use TS because at the times I compared it with Mumble, it looked better(but only initially), but also felt more heavy. Both client and server. Also not open-source, so no go for exotic platforms. What I can say for Mumble is that you can customise it. I couldn't care less about redundant server messages spamming me with the rejoins from someone with a bad connection, for instance. Furthermore you can have different users colored differently. Emulation layers for running TS would have eliminated Mumbles rather minimal resource usage.
Maybe you should stop nagging. My initial question was why?
You said because text chat sucks in comparison to TS which has tabs.
I said I don't care because "works for me", and anyways you can configure it to be less annoying.
You accused me of moving goal posts while I didn't even feel like having joined your game, not to speak of not even caring about rules, thus total disregard for position of goals.
Furthermore I suggested just using another text chat option parallel to Mumble which better suits your needs, because why not?
I know. But then I wonder why you ask the question if you don't care about the answers.
>and anyways you can configure it to be less annoying
which was and is plain wrong. Since it doesn't change the textbox behaviour at all. It's still all in one box. That makes me wonder if you even use Mumble.
>Furthermore I suggested just using another text chat option parallel to Mumble which better suits your needs, because why not?
Because running multiple programs is not the solution to this. Say somebody wants to join your Mumble server. Now in order to send text messages, that person also has to join/download/install another application. While Mumble itself could be sufficient.
Maybe we have different usage patterns? For instance the main thing is an IRC client connected to several servers and channels, while voice chat is only optionally in use? "On demand", so to speak.
As a user of mumble I care about waste of limited developer (time) resources spent for features I don't need, and maybe even degrading performance.
edit: ...makes me wonder... makes ME wonder if you ever used custom layout? OFC still no tabs, still single box, but filtered/disabled almost all server messages/rejoin spam.
>As a user of mumble I care about waste of limited developer (time) resources spent for features I don't need, and maybe even degrading performance.
You don't, but many others do.
>edit: ...makes me wonder... makes ME wonder if you ever used custom layout? OFC still no tabs, still single box, but filtered/disabled almost all server messages/rejoin spam.
I have. I don't want to have to filter them. Sometimes they are useful.
