NetworkManager 1.50 Released - Now Ensures Offensive Terms Don't Appear In Settings

[fitzie]

FYI https://mastodon.social/@ffmancera

The commit author is also woke

i love that he think it's winning that people call him a woke joke. he's just like those people sitting in highways or throwing paint at art. the cause is irrelevant, annoying people is why he does it. good luck random networkmanager dev, you have billions of more people to annoy in your life!

[horizonbrave]

Low IQ liberals/progressives. Words are words. It's the intent. The reality is you will always have the need to discriminate between levels. And now you've codified for all the world that you are indeed racist in the way you use words like autoconnect_slaves, connection_master, etc. Congratulations, you played yourself.

Always considered low IQ the right wingers, or at least piece of shit humans. But that's just me

[reavertm]

Finally I can have a solid night of rest in the confident knowledge that RH and IBM are focusing on what is important for networkmanager.

image.png

Do my eyes deceiveth me or it's completely superfluous routing table created by NM I assume? Why does kernel even allow that?

[Squisher]

Most of these language oriented changes actually clarify meaning. Like DSA_conduit is clearer than master. Same in SPI, dev/periph is clearer than master/slave.

Conduit was not part of my simplified english vocabulary, so I had to look it up. But I'm not complaining. Its just that for me a simpler form like controller or manager would have done the trick also. But those tend to be ill-/overused in software.

Like 10 years ago we made a new PLC (those industrial controllers) firmware and it had to support MODBUS. In the MODBUS spec they had changed master/slave to client/server which fits their role perfectly when you look at it from the way the communication happens. But management decided that we should still call it master and slave in order to not confuse our customers.

[Old Grouch]

I know the white part in the logo is supposed to be an ethernet plug, but it looks like an hand.

It looks to me like a letter 'N' throttling itself. Auto-asphyxiation does nothing for me, but it does for some.

[Old Grouch]

Imagine and build a better world in which language evolves to correct the inherent bigotries and biases over centuries of incorrect and destructive thought patterns so ingrained people don't even notice them in said language until they're directed at oneself and people like oneself... then one reads Phoronix's forums and realizes just how very very long we have to go.

Most contemporary linguists disagree with the strong Sapir-Whorf hypothesis.

[deusexmachina]

systemD is extremely offensive to those without D. It is now to be referred to as systemJustABarePatchOfSkinDownThere. Nothing going into the body, nothing coming out of the body. As far as you are concerned my "system" is androgenous!

[reba]

just switched from networkmanager with wpa_supplicant to systemd-networkd with iwd, as I have done some time ago in a virtual machine, and everything works like a charm.

[Old Grouch]

Those terms are not offensive.

They are to some, and the question is whether the people for whom the terms are offensive, or worse, trigger PTSD (modern slavery exists) should be taken into account when code is written/technology is used.

The question is not whether the words are offensive in themselves, but whether other people's feelings and opinions should be taken into account when we do things.

Many people justify their position by using context and intent - the words are not being used in the context of an actual, human, master-slave relationship, and the intent of using them in a technological context is not (usually) one of wishing to upset others, although some people will want to do exactly that.

Unfortunately, not everyone thinks that the context and intent arguments override the feelings and opinions they have, and both groups of people can feel very strongly that they are right. Conflict results.

There are other terms that can be used, which would be helpful to defuse the conflict. My wish is that other terms, when used, should be technically accurate; and unambiguous. For this reason, I don't like 'blocklist', as it can have two distinct meanings (a list of blocks on a block-based storage medium; or a list of things to be prevented - 'blocked') - I would prefer deny-list, paired with allow-list.

Sometimes the right thing to do is to be nice to people.

[Old Grouch]

<Duplicate content deleted>