HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
mumble-voip
mumble
C++2012–2023
mumble-voip / mumble

mumble

Mumble is an open-source, low-latency, high quality voice chat software.

20Distinct people
23Mentions
0Explicit recommenders
8.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Mumble is an open-source, low-latency, high quality voice chat software.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year23 dated mentions

Observed mentions: 2012-06-15 10:12:14 UTC to 2023-06-23 03:27:28 UTC.

024682012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC110
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC000
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC000
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC101
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC514
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC514
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC808
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101

What Hacker News says

23 sources
Mumble's latency is unbeatable imo, it's basically their main focus and shows. The sticking point for me is the lack of persistent messages, something the devs strangely think is a privacy plus. Issue open since 2016: https://github.com/mumble-voip/mumble/issues/2560 If you drop out for a minute you won't have access to anything that was posted in chat, which makes it useless for anything other than voice only comms, that might suit some business purposes but I've always needed to post links or screenshots in chat during meetings.
In Revolt: FOSS Discord Alternative
I have suggested integrating with Mumble before, it would be a great way to interact. Add a "info.mumble.servers" or "info.mumble.channels" state event, some magic on murmur's side to authenticate using Matrix, and roll with it in your own Matrix client. Pinned messages with mumble:// URIs could be used as a fallback. One of the issues is that upstream mumble lacks support for websockets, so web clients are impossible. Otherwise, it sounds quite promising. I even suggested something along these lines, but haven't had time to cook up a prototype: https://github.com/mumble-voip/mumble/issues/1813#issuecomme... (there seems to have been some back-and-forth on that idea since then).
In Spaces launch in Element
For Mumble in particular, the devs had their heads in the clouds for so long that it is no surprise that it is no longer relevant. If you had a mic that had issues in any way (buzzing, volume, balance), "The Wizard" and "AGC" were supposed to fix it for you. Do not fret little one, for you do not need nor want to manually fiddle with settings, The Wizard will make everything right [1]! The pivotal feature that was the reason so many people I know stopped using it is the ability to change the volume of an individual person [2]. It has been a requested feature since the beginning of time, yet it took until 2016 to implement in dev branch and didn't actually make it into a release version until 2020! Too little, too late. [1] https://web.archive.org/web/20200223143654/https://wiki.mumb... [2] https://github.com/mumble-voip/mumble/issues/1156
In How Discord Stores Billions of Messages (2017)
I checked and they do have 2 types of echo cancellation (mixed/mono and multichannel): https://wiki.mumble.info/wiki/Audio#Echo_Cancellation But looks like they maybe still have blockers that prevent them from enabling it by default: https://github.com/mumble-voip/mumble/issues/4178 Normally I would attribute this to these types of libraries evolving from the UNIX mindset, which almost always lacks sane defaults. But in this case, it looks like it has more to do with difficulties around maybe Apple's secrecy and patents around their own echo cancellation implementation. Hopefully I'm wrong about that. When I was working on a networked game around 2005, I dabbled with Speex and Vorbis. I found the Ogg maintainers to be rather hostile to my suggestions around echo cancellation. I suggested some stuff with autocorrolations to find the echo d
Read the rest
elay offset, since I had used them quite a bit as a contractor at hp. I was thinking that maybe they would let it dynamically adjust with little overhead, rather than needing a fixed delay between the microphone and speakers. I wanted this for the Mac, where there was no low-level way to access the mic and speaker hardware like on the PC, so I was concerned that there wouldn't be a fixed time offset available with Apple APIs. At the time, I thought they were just dismissing me as a n00b, but now I understand that they were just terribly overextended. These libraries are difficult to maintain, not because of any technological reason (this stuff was well-understood by the mid 1990s), but because of hardware/driver errata, constant undermining by big established OS players caving to entertainment lobbyists like the RIAA, and the constant threat of lawsuits by patent trolls. I would say the same thing about mesh networks or BitTorrent or Skype before Microsoft bought it or TikTok any of the other faces of the "real" internet that routes around censorship and inconveniences those who profit from the status quo.
In Mumble: Open-Source, Low Latency, High Quality Voice Chat
> That fight was long long lost. We will never ever make things like video games open source. I don't share your pessimism. Yes, it is harder to exploit users with [FLO] software; so there is less profit to be made; and that will discourage some companies from making it. But I can easily imagine that with a modest income from donations, a project like [Black Mesa] would be happy to make their game open source. Also yes, most software projects today cannot make a living off of donations. But there's no inherent reason this has to be so. People have shown they are willing to pay money for software; in principle, it is ["just"] a matter of redirecting that money from proprietary software to FLO software. And yes, solving the free-rider problem is a very ambitious "just". But addressing a collective action problem like this requires a coordin
Read the rest
ation mechanism, and the [existing crowdfunding platforms] don't have that. So, I am actively working on one that does — [Snowdrift.coop] — and am not yet ready to throw in the towel. > But we can sandbox them. Even open source tools could do with being sandboxed. I agree, but I don't think the operating system is the right level of abstraction to do this. Sandboxing is complex. Implementing it in the OS pushes that complexity on every program, which makes tinkering much harder. I absolutely do not want to have to deal with sandboxing and permission prompts in my .bashrc aliases and shell scripts. I write shell scripts to make my life easier by automating common actions, and having to set flatpak/SELinux type permissions every time I do that would defeat the purpose, or at least substantially raise the bar for how much friction is required before I turn to a script. Writing a simple program on Android/Linux is soo much more work than writing one for GNU/Linux, and soo much less accessible. Also, we already have an excellent application sandboxing platform for running untrusted and borderline malicious programs — the web. The result of that sandboxing is incredible complexity which makes it a herculean task to develop a web browser. That's a real shame; I'd love to see the "web of documents" split off from the "web of applications" (e.g. to a different protocol, like gopher). I don't want to see desktop environments go the same way. When I install and run a program natively, I am indicating that I trust it and want to leave the restrictions and complexity of the web sandbox behind. I do see a case to be made for a sandboxing tool for graphical applications specifically. Because building a GUI is already a lot of work compared to writing a CLI, so the relative effort to handle permissions, etc is not as large. But this should be built into and enforced by the packaging tool (e.g. flatpak permissions), not the operating system. And, to bring this discussion back on topic, not by the display manager. Here's a concrete example: I use Mumble for voice chat. I use push-to-talk. [PTT on Wayland] doesn't work, because the display server only sends keyboard events to the client that has focus. You can look at the linked issue and see all the complexity that results. So for now I am still running X. Yes, there are workarounds. No, I don't want to have to deal with them. Not having to deal with them is the kind of nice thing we can't have if we accept sandboxing by default, rather than sandboxing only the few programs that we cannot trust to run directly on our machines. --------------------------- [FLO]: https://wiki.snowdrift.coop/about/free-libre-open#flo [Black Mesa]: https://store.steampowered.com/app/362890/Black_Mesa/ ["just"]: https://blog.snowdrift.coop/crazy-ambition/ [existing crowdfunding platforms]: https://wiki.snowdrift.coop/market-research/other-crowdfundi... [Snowdrift.coop] besides the main site, our wiki has more/better information: https://wiki.snowdrift.coop/ [PTT on Wayland]: https://github.com/mumble-voip/mumble/issues/3243
In On the Graying of Gnome
Mumble / Murmur [1][2] is a nice self hosted alternative to Teamspeak and there are also many public servers. Rock solid, great voice quality, UX is still being refined, not as frictionless as Discord for new users, but I keep one running for family to fall back to. The server is just routing text / voice, so it scales to VERY large numbers of users with little resource usage. [1] - https://wiki.mumble.info/wiki/Main_Page [2] - https://github.com/mumble-voip/mumble
In Dark Horse Discord

Showing the 15 most recent of 23 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.