Some kind of alternative to @url{https://www.mumble.info/, Mumble}.
@float
-@image{screenshots/example,,,Server and 2 clients,.webp}
-@caption{Server and two clients}
+@image{screenshots/example,,,Server and two clients,.webp}
+@caption{Server (above) and two clients (left and right) in a terminal multiplexer}
@end float
But why? SIP-based solutions are pretty complicated to setup, because
Mumble tends to output no information, sometimes hiding the fact of a
problem and that everything stopped working.
-@item No NAT-traversal possibility. Its 2024 year already, stop trying
+@item No NAT-traversal possibility. It is 2024 year already, stop trying
to use and revive legacy obsolete IPv4. Or use some overlay network on
-top of it, VPN. Just stop using that piece of shit with all complexities
-it brings you to.
+top of it, VPN, whatever.
@item Mono-cypher, mono-codec protocol. @url{https://opus-codec.org/, Opus}
audio codec is perfect for VoIP tasks. ChaCha20-Poly1305 is more than
@end itemize
-Current biggest drawback is lack of audio mixing on the server side.
-Each client's voice traffic is just copied by server to every other
-client. Hopefully that is temporary solution.
+TODO: server should verify symmetric authentication tags on incoming
+traffic, before copying it to everyone. Look at latest Opus'es neural
+network abilities.
@include install.texi
@include usage.texi