Conversation
Notices
-
@Moon @Zerglingman @jeff ohh yeah i have html formatting outright disabled on mumble.volatile.bz cus i dont trust anyone to do that right, and i already use other shit for text chat and image uploads
i like the mumble voice protocol itself, if anything i'd think to have better integration with other already-existing chat platforms so we all arent bitching about another gui program taking up space. dunno the best approach to that though
- Machismo likes this.
-
@opal @jeff @Moon They'd rather integrate jitsi instead apparently.
Honestly I think the solution to mumble is to just remove everything except the voice chat, you want to be in a different channel on the server? You reconnect on a different path.
UI is literally just a settings page and current connection status.
-
@opal @Zerglingman @Moon the protocol can be the literal immaculate work of god but as long as the UI is dogshit no one will care.
-
@jeff @Moon @opal THAT IS BECAUSE OF NIGGER MENTALITY
-
@Zerglingman @jeff @Moon end users should not have to care and the user experience should just work. i write my own stuff with this philosophy in mind, it's important to keep in mind your target audience for software
-
@Zerglingman @jeff @Moon eh the concept of channels is sound, especially since mumble's ACLs couple tightly with that model, but the good thing is that we can at least repurpose murmurd and create a new frontend that does something more sane, if we want to be absolutely lazy about it
-
@opal @Zerglingman @Moon yea. the only place i'd use mumble proto is for the federated backend. remote users would proxy mumble via their local instance when they join but the clients would all be using webrtc at the edges to their home servers
-
@jeff @Zerglingman @Moon which is why im here to piece together how protocols can be hidden away by good UI/UX, i think you underestimate my willpower here