umurmur VS rust

>...its server side is still written on Qt, which requires hundreds of megabytes of additional libraries to build it up.

See:

https://github.com/umurmur/umurmur

I've tried to make this argument in the past and gained no traction. What I did instead was to create self hosted chat things as a fallback for the times when Discord or Slack have a green status page but their applications fail to operate. Even light-weight daemons like uMurmur [1] or devzat ssh-chat can be handy in a time of need if a quorum know to fall back to it. Self hosted tools are also handy when one wants to share links or text that should not be on 3rd party sites forever and for eternity

[1] - https://github.com/umurmur/umurmur/wiki/Configuration

[2] - https://github.com/quackduck/devzat

Adding a more private self hosted option, there is uMurmur [1] which is light-weight enough to run on a Linux router. One of the mobile apps that works with it is Mumla.

There is of course the full blown Murmur [2] install that works a little more like Discord in that people can create channels and there is a permission system.

[1] - https://github.com/umurmur/umurmur/wiki/Configuration

[2] - https://wiki.mumble.info/wiki/Main_Page

For the other layers one can front-end IRC with TheLounge [1][2] or Convos [3][4]. TheLounge only persists history in private mode meaning that users are created in that front-end and chat messages are in Redis. For small networks or groups of friends this is probably fine.

Notably missing is voice chat. I use the Mumble client [5] with the Murmur or uMurmur [6] server which is light-weight enough to run on ones home router. I use it on Alpine Linux, works great. It's not a shiny and attention grabbing as Discord but probably fine for everyone else. For people to create their own voice channels would require the full-blown Murmur server.

[1] - https://github.com/thelounge

[2] - https://thelounge.chat/

[3] - https://github.com/convos-chat/convos/

[4] - https://convos.chat/

[5] - https://www.mumble.info/

[6] - https://github.com/umurmur/umurmur/wiki/Configuration

I suppose people should decide for themselves if they take the word of a centralized service. Convenience is a factor after all.

For those that have small circles of friends they wish to chat with and minimize the number of ISP's their traffic traverses, I would suggest tinkering around with uMurmur [1] There are pre-built packages in several operating systems package managers. The configuration is dirt simple [2] and the daemon is very light weight, designed to run on home routers. Use certbot to generate LE certs or just use self-signed. One TCP and one UDP port must be forwarded to the daemon, default port being 64738. One can set a server-wide password to keep strangers off of it, or set passwords per-channel.

uMurmur is not E2EE but if it is running on your own router and you are talking with your friends that you know and trust then maybe that is less of an issue. The mobile client is Mumla. Just put in the IP or hostname of the uMurmur instance.

[1] - https://github.com/umurmur/umurmur

[2] - https://github.com/umurmur/umurmur/wiki/Configuration

I like https://umurmur.net/ since it can run totally headless at the cost of some of Murmur's features. Mainline Murmur (the Mumble server) requires QT5 and mDNSResponder and various DB drivers and even D-Bus if you look at it crossways

I believe quite a few people use umurmur for stuff like this. Note that it's encrypted and I don't believe that can be shut off, so don't run it over, say, HamWAN, but I don't imagine that was the plan anyway.

If you haven't dipped your touch-typing fingers into Rust yet, you really owe it to yourself. Rust is a modern programming language with features that make it suitable not only for systems programming -- its original purpose, but just about any other environment, too; there are frameworks that let your build web services, web applications including user interfaces, software for embedded devices, machine learning solutions, and of course, command-line tools. Since a custom GitHub Action is essentially a command-line tool that interacts with the system through files and environment variables, Rust is perfectly suited for that as well.

Here's an example of someone citing a disagreement between CRT and shell32:

https://github.com/rust-lang/rust/issues/44650

This in addition to the Rust CVE mentioned elsewhere in the thread which was rooted in this issue:

https://blog.rust-lang.org/2024/04/09/cve-2024-24576.html

Here are some quick programs to test contrasting approaches. I don't have examples of inputs where they parse differently on hand right now, but I know they exist. This was also a problem that was frequently discussed internally when I worked at MSFT.

    #include 

> instead of choosing a certain numbered version of the random library (if I remember correctly) I let cargo download the latest version which had a completely different API.

Yeah, they didn't follow the instructions and got burned. I still think that multiple things went wrong simultaneously for that experience. I wonder if more prevalent uses of `#[doc(alias = "name")]` being leveraged by https://github.com/rust-lang/rust/pull/120730 (which now that I check only accounts for methods and not functions, I should get on that!) so that when changing APIs around people at least get a slightly better experience.

Almost fixed the compiler: https://github.com/rust-lang/rust/pull/123325

Rust: A secure, efficient, and modern programming language (omitting ten thousand words). You can simply follow the installation instructions provided on the official website.

Recently did something similar in Rust but for generating SVGs. We've adopted it for snapshot testing of cargo and rustc's output. Don't have a good PR handy for showing Github's rendering of changes in the SVG (text, side-by-side, swiping) but https://github.com/rust-lang/rust/pull/121877/files has newly added SVGs.

To see what is supported, see the screenshot in the docs: https://docs.rs/anstyle-svg/latest/anstyle_svg/

We strongly believe in Rust as a powerful language for building production-grade software, especially for systems like ours that run alongside Kubernetes.

The above Assert<{N % 2 == 1}> requires #![feature(generic_const_exprs)] and the nightly toolchain. See https://github.com/rust-lang/rust/issues/76560 for more info.