Bonum Certa Men Certa

Guest Article: Are We Still Removing Problems, or Removing Options?

By figosdev

Windows options
Windows options



Summary: Monoculture in GNU/Linux as explained by figosdev

To avoid a misunderstanding, here are two things this article is NOT referring to:



1. I'm not referring to situations where there is too much extra trouble to create an option. In other words, if you switch to (or from) elogind to another method of removing a systemd dependency, I'm NOT saying that you need to make both methods an option. That would lead to a potentially infinite amount of maintenance when applied across everything.

(Don't forget though, that a similar argument is made against providing alternatives to systemd. And maintaining alternatives to that is important.)

2. I'm also NOT saying that it is important to include "the option of having handcuffs." This is not about supporting non-free software.

"When I do promote FSF-endorsed distros, I focus mostly on Hyperbola and Guix -- Hyperbola is particularly important in that I feel Guix is more highly technical, and Hyperbola is necessary for the mainstream."So with that out of the way, I think a lot of the fully-free FSF distros fall short when it comes to user freedom. I'm referring of course, to newer problems like init freedom. When I do promote FSF-endorsed distros, I focus mostly on Hyperbola and Guix -- Hyperbola is particularly important in that I feel Guix is more highly technical, and Hyperbola is necessary for the mainstream.

So I support Hyperbola about as much as any FSF-approved distro. I'm still very happy that Hyperbola was accepted to the list (it's a huge step forward for the FSF.)

My critique is based on something someone has told me, which I will treat as a mostly-hypothetical problem that I hope Hyperbola devs will either mitigate or avoid.

Essentially, it's how we go about liberating the user. There are (at least) two ways we can make the user more free: We can become nannies, or we can assist the user in their freedom. I consider these two different approaches, and the difference is the point.

"There are (at least) two ways we can make the user more free: We can become nannies, or we can assist the user in their freedom."If we choose to be nannies, we make all the decisions, we enforce those decisions, we might even (and this is the worst of it I think) choose to enforce those decisions in a way that there is little recourse for the user if "we" (developers) make a mistake in our judgment.

Here are some things I would like to have removed:

* Gnome: As much as possible. I guess we are stuck with GTK at least -- I LOVE leafpad. I use IceWM as well. Year after year, it's the best. Qt is good, but will there ever be a Qt IceWM or Leafpad?

* Pulseawful: Not enough is done in other distros to make this monstrosity optional.

* Systemd: Obviously. I refer to it as a weapon against free software.

"Some of these technologies are bad for the user and don't even belong in the free software ecosystem."And I know the blacklist Hyperbola uses -- there are a lot more things.

Some of these technologies are bad for the user and don't even belong in the free software ecosystem. If they are under a free license, they are free software at least. If they are designed deliberately to limit what else we can do, perhaps the term "Open Source Proprietary Software" (OSPS) applies. I am also ready to promote the term "Punix" for, a reduced-modularity, reduced-user-respecting corporate overthrow kind of design.

Some of these technologies make it really difficult to remove them once they are entrenched. Many of us already agree that this is a major problem.

Getting back to the critique, the longer the blacklist gets, the higher the odds that we will make "a mistake" in what we should remove. And as much as other people are making mistakes about what to include, mistakes about what to remove are just as important.

"Because there are more users than developers; we want the user to have as much say as possible."It's very important that we not become nannies -- it goes against the entire spirit of free software in my opinion. I've spent a while now complaining that the distro concept itself is ripe for user abuse and limits user autonomy.

We should always have user autonomy as our goal -- a goal that is higher than autonomy for developers only. Because there are more users than developers; we want the user to have as much say as possible. The freedom isn't just for us, we are trying to bestow it on everybody.

That means the decisions aren't just for us.

So I think it's great that we provide services to remove harmful software. It's all about how we do it, and what the user is left with in terms of options. Yes, our first priority should be to minimise the impact of (OSPS) software designed to take freedom away. But as we remove more and more we should always try to empower the user in making their own decisions, and not to simply be protective.

I'm not saying distros are evil -- they can help a lot. There was a time when a distro was the only efficient way to provide freedom to the user. In an age of automation, we will find the distro is not the most liberating thing possible. We should transcend the distro, and consider options that are distro-agnostic when possible.

That's a long road ahead, and in the meantime we should never take too much power for ourselves.

I'm in favour of the blacklist, I think it's a great idea.

I'm not saying that everything on the blacklist should be hosted in the repos either. Perhaps some of it should be. I don't know if it is -- this is partly hypothetical, so the current status is partly irrelevant to what I'm saying.

"Defaults are defaults -- the very nature of a default is that it is a choice made for everybody. That's alright."What I am saying is that freedom is more important than choice, but choice matters as well. We cannot support every possible example of choice, but we can keep some choices open. That should remain the default, except when we honestly can't do everything.

We don't have to make every decision for the user. Defaults are defaults -- the very nature of a default is that it is a choice made for everybody. That's alright.

The decisions made that go beyond defaults, we need to be careful not create another distro that tells the user what to do by doing everything for them, and denying them recourse against our own decisions.

We really have to trust the user more than that, and not devalue their judgment.

This doesn't necessarily mean making systemd an option; this is about other things than systemd. Systemd itself is an endless growth of problems -- plural.

But we definitely can't treat every option we consider a problem, the way we treat systemd. We can't enforce every choice of ours as though "we know best." We have to leave distros more open than that, or we are ultimately making ourselves a slightly improved version of Lennart himself.

"What I do know, is that apart from Hyperbola, other distros are making mistakes like these."There are no accusations here. This is a comment on concerns brought to me personally, that I have not yet verified. I hope those concerns are unfounded.

What I do know, is that apart from Hyperbola, other distros are making mistakes like these.

So my advice to the Hyperbola team, and my advice to the entire culture of free software is: Let's do better than that. It's not about perfection, it's not about making "every single possible choice" an option.

It's just about our attitude towards users, and how highly we think of our own decision making and value theirs.

Let's abandon all the hubris that we can -- not just for Hyperbola, but as a higher goal for all free software development: to create freedom wherever we are able as a higher goal, and make our job go beyond removing things we consider a threat.

Finally I will, as an example, put to you a matter related to linux-libre.

"Many of us don't really care about non-free kernel modules, as we don't think it's good to load them in the first place."Linux-libre has a bug related to its loading of non-free kernel modules.

Many of us don't really care about non-free kernel modules, as we don't think it's good to load them in the first place.

But we don't work to forbid people from loading them -- not even in the FSF distros; meaning, we don't create whitelists or use DRM-like measures to stop people from loading non-free code on their computers.

Linux-libre has had a bug for years, that prevents it from loading non-free modules.

I used the word "bug" because that's the word the linux-libre developers use. It's actually not a desired effect that linux-libre prevents loading non-free modules. It is an unwanted side-effect, according to the developers.

They have sought a fix for years, and consider it unfixable. But it is a shortcoming.

We don't want to be in the business of creating shortcomings like that when they're avoidable. Linux-libre has that shortcoming because of its goal of not "enticing the user to install non-free software." It is related to an error that shows up during boot. In fixing that problem, linux-libre creates an unwanted side effect.

"Having this goal requires an entirely different attitude to one of a nanny. It requires the attitude of a devoted civil servant -- devoted not to institutions, but to everyday people."The point here, is that linux-libre does not have a goal of creating such side effects. They are not considered desirable and it may not be fixable for linux-libre, but when it is possible we should avoid such effects.

Having this goal requires an entirely different attitude to one of a nanny. It requires the attitude of a devoted civil servant -- devoted not to institutions, but to everyday people.

To the Hyperbola team and anybody who takes up a similar list of goals, keep up the good work. I realise you are volunteers -- this consists of a think piece stating opinions, there are no demands being made here.

Licence: Creative Commons CC0 1.0 (public domain)

Recent Techrights' Posts

A Week After a Worldwide Windows Outage Microsoft is 'Bricking' Windows All On Its Own, Cannot Blame Others Anymore
A look back at a week of lousy press coverage, Microsoft deceit, and lessons to be learned
 
Links 26/07/2024: Tesco Cutbacks and Fake Patent Courts
Links for the day
Links 26/07/2024: Grimy Residue of the 'AI' Bubble and Tensions Around Alaska
Links for the day
Gemini Links 26/07/2024: More Computers and Tilde Hosting
Links for the day
Links 26/07/2024: "AI" Hype Debunked and Elon Musk's "X" Already Spreads Political Disinformation
Links for the day
"Why you boss is insatiably horny for firing you and replacing you with software."
Ask McDonalds how this "AI" nonsense with IBM worked out for them
No Olympics
We really need to focus on real news
Nobody Holds the GNOME Foundation Accountable (Not Even IRS), It's Governed by Lawyers, Not Geeks, and Headed by a Shaman Crank
GNOME is a deeply oppressive institutions that eats its own
[Meme] The 'Modern' Web and 'Linux' Foundation Reinforcing Monopolies and Cementing centralisation
They don't care about the users and issuing a few bytes with random characters costs them next to nothing. It gives them control over billions of human beings.
'Boiling the Frog' or How Online Certificate Status Protocol (OCSP) is Being Abandoned at Short Notice by Let's Encrypt
This isn't a lack of foresight but planned obsolescence
When the LLM Bubble Implodes Completely Microsoft Will be 'Finished'
Excuses like, "it's not ready yet" or "we'll fix it" won't pass muster
"An escalator can never break: it can only become stairs"
The lesson of this story is, if you do evil things, bad things will come your way. So don't do evil things.
When Wikileaks Was Still Primarily a Wiki
less than 14 years ago the international media based its war journalism on what Wikileaks had published
The Free Software Foundation Speaks Out Against Microsoft
the problem is bigger than Microsoft and in the long run - seeing Microsoft's demise - we'll need to emphasise Software Freedom
IRC Proceedings: Thursday, July 25, 2024
IRC logs for Thursday, July 25, 2024
Over at Tux Machines...
GNU/Linux news for the past day
Links 26/07/2024: E-mail on OpenBSD and Emacs Fun
Links for the day
Links 25/07/2024: Talks of Increased Pension Age and Biden Explains Dropping Out
Links for the day
Links 25/07/2024: Paul Watson, Kernel Bug, and Taskwarrior
Links for the day
[Meme] Microsoft's "Dinobabies" Not Amused
a slur that comes from Microsoft's friends at IBM
Flashback: Microsoft Enslaves Black People (Modern Slavery) for Profit, or Even for Losses (Still Sinking in Debt Due to LLMs' Failure)
"Paid Kenyan Workers Less Than $2 Per Hour"
From Lion to Lamb: Microsoft Fell From 100% to 13% in Somalia (Lowest Since 2017)
If even one media outlet told you in 2010 that Microsoft would fall from 100% (of Web requests) to about 1 in 8 Web requests, you'd probably struggle to believe it
Microsoft Windows Became Rare in Antarctica
Antarctica's Web stats still near 0% for Windows
Links 25/07/2024: YouTube's Financial Problem (Even After Mass Layoffs), Journalists Bemoan Bogus YouTube Takedown Demands
Links for the day
Gemini Now 70 Capsules Short of 4,000 and Let's Encrypt Sinks Below 100 (Capsules) as Self-Signed Leaps to 91%
The "gopher with encryption" protocol is getting more widely used and more independent from GAFAM
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Wednesday, July 24, 2024
IRC logs for Wednesday, July 24, 2024
Techrights Statement on YouTube
YouTube is a dying platform
[Video] Julian Assange on the Right to Know
Publishing facts is spun as "espionage" by the US government and "treason" by the Russian government, to give two notable examples
Links 25/07/2024: Tesla's 45% Profit Drop, Humble Games Employees All Laid Off
Links for the day
Gemini Links 25/07/2024: Losing Grip and collapseOS
Links for the day
LWN (Earlier This Week) is GAFAM Openwashing Amplified
Such propaganda and openwashing make one wonder...
Open Source Initiative (OSI) Blog: Microsoft Operatives Promoting Proprietary Software for Microsoft
This is corruption
Libre-SOC Insiders Explain How Libre-SOC and Funding for Libre-SOC (From NLNet) Got 'Hijacked' or Seized
One worked alongside my colleagues and I in 2011
Why We're Revealing the Ugly Story of What Happened at Libre-SOC
Aside from the fact that some details are public already
Removing the Lid Off of 'Cancel Culture' (in Tech) and Shutting It Down by Illuminating the Tactics and Key Perpetrators
Corporate militants disguised as "good manners"
FSF, Which Pioneered GNU/Linux Development, Needs 32 More New Members in 2.5 Days
To meet the goal of a roughly month-long campaign
Lupa Statistics, Based on Crawling Geminispace, Will Soon Exceed Scope of 4,000 Capsules
Capsules or unique capsules or online capsules are in the thousands and growing
Links 24/07/2024: Many New Attacks on Journalists, "Private Companies Own The Law"
Links for the day
Gemini Links 24/07/2024: Face à Gaïa, Emacs Timers for Weekly Event, Chromebook Survives Water Torture
Links for the day
Why Virtually All the Wikileaks Copycats, Forks, and Rivals Basically Perished
Cryptome is like the "grandpa" of them all
A Total Lack of Transparency: Open and Free Technology Community (OFTC) Fails to Explain Why Over 60% of Users Are Gone (Since a Week Ago)
IRC giants have fallen
In the United Kingdom Google Search Rises to All-Time High, Microsoft Fell Nearly 1.5% Since the LLM Hype Began
Microsoft is going to need actual products or it will gradually vanish from the market
Trying to Put Out the Fire at Microsoft
Microsoft is drowning in debt while laying off loads of staff, hoping it can turn things around
GNU/Linux Growing at Vista 11's Expense
it's tempting to deduce many people who got PCs with Vista 11 preinstalled are deleting it, only to replace it with GNU/Linux
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Tuesday, July 23, 2024
IRC logs for Tuesday, July 23, 2024