Lunduke
News • Science & Tech
The Worst Part of Open Source: The Community
Open Source has a lot of strong points… “The Community” is not one of them.
September 11, 2024
post photo preview

"Oh-muh-gosh!  Community is so important to Open Source!"

How often do we hear that?  How often are we inundated with declarations of how absolutely amazing the "Linux Community" or the "Open Source Community" are?

Constantly.

There are entire conferences dedicated to Open Source "Communities" -- and nearly every company or foundation which is even remotely "Open Source-y" has an official "Community Manager" position.  Sometimes several of them.

 

The Heck With That

 

Well, I'm here to say what most of us are thinking (but are afraid to say out loud):

The "Community" is the absolute worst part of Open Source Software.

Search your feelings.  You know it to be true.

Over the last few years we have seen an onslaught of attacks -- on the software we use and love (and the people that build and use that software) -- perpetrated by that "Community" that is deemed so important and amazing.

Here are 5 quick examples to give you an idea of what the "Open Source Community" does.

The examples go on, and on, and on.  We could spend all day listing recent incidents where the "Open Source Community" has actively brought about significant harm and destruction -- both to the software they claim to support... and to the people who build and use it.

In fact, I would say there is a very strong case to be made that the "Community" is the single biggest problem with Open Source Software.

 

Not All Communities Are Good

 

A "Community" of people can be a fantastic, productive, supportive force.  But, if that was ever the case with the "Open Source Community" -- and, I believe, at one point (long ago) it was -- it certainly is not anymore.

The word "Community" gets thrown around -- rather constantly -- as if it's some magical, always wonderful thing.  When the truth is often the exact opposite.

Case in point: An enraged mob carrying torches and pitchforks.  That's a community.

 

 

A group of zombies, shuffling together towards their next meal (your brains).  That, also, is a community.

 

 

We could list an almost endless number of examples of "communities" which are destructive and, in many cases, downright evil.  But I think you get the point.

The hard reality is that the "Open Source Community" has become something akin to the torch-wielding mob (with a dash of zombie thrown in for good measure).

Destructive.  Angry.  Terrorizing.

And, importantly, striking fear in the hearts of any who dare oppose the mob.

An anecdotal example:

Recently, I was having a discussion, via E-Mail, with the founder of a prominent Open Source project.  There had been a round of mob-like attacks on some of the members of that project (because that's what happens in Open Source projects with a "Community"), and I was working on an article covering those events.

All very ordinary.  That sort of thing happens weekly.

Then the founder of that project requested -- nay... pleaded -- that I hold off on publishing the article.  And, if I did publish the article, to not include the founders name or indicate that we had spoken at all.

Because, and I quote, "I worry that it will make things *worse* for me."

The founder feared what the mob (aka the "Community" of the Open Source project which that person had created) would do if they found out we had simply spoken.

If you speak out against the mob (the "Community")... the mob attacks you.  Everyone knows it.  And everyone fears it.

 

The Mob Will Continue if We Let It

 

That project founder is not alone.

It is exceedingly rare that more than a few days go by without hearing about similar situations -- people (contributors, founders, and users) bullied and terrorized into silence by a mob hiding behind the moniker of "Open Source Community".

A mob which has been -- often -- granted extreme levels of power over projects, foundations, and corporations.  Power which they use to drive away founders, contributors, and users and -- along the way -- effectively hold the remaining contributors hostage through an environment of terror.

This "Community" is, observably, causing more damage to Open Source than any other single thing I can think of.

Make no mistake... Open Source Software is, in my opinion, a wonderful, positive thing.  Software being "Open Source" allows it to be used and maintained long past the time the original developers may have moved on or dropped support.  It facilitates increased security testing, historical preservation, and so many other benefits.

In short, Open Source -- both the concept and practical implementation -- is worth saving.

The question is: How can this "Community" be stopped?  How can we, effectively, disarm this mob... this "Community"?

I suggest the two following actions.

 

  1. Speak out when the "Community" bullies you (or others).  Directly.  Publicly.  If you fear retribution (as so many do), reach out to the press to discuss how to publish your story while retaining your anonymity.
  2. For project founders: Retain (or re-obtain) absolute control over your project.  Be a dictator.  If the "Open Source Community" is allowed any level of unchecked control over your creation (including something as seemingly simple as "moderation of a forum"), the "Community" will use it to harm you and others.  One person must always have dictatorial control -- the right to over-ride anything -- within a software project.

 

This may sound harsh -- and rather extreme -- to many of you.  Unfortunately, the harsh reality of the "Open Source Community", necessitates these sorts of measures in order to limit the effectiveness of the mob.

The more people that speak out about the bullying and terror tactics of the mob... the safer it gets for others to speak out as well.  Likewise removing power from the mob is always a smart move when dealing with... well... a mob.

Many will criticize the things I am saying here.  They will say that I am "anti-Community" or "anti-Democracy" or the like.  It is a near certainty that members of the "Open Source Community" will hurl a wide variety of insults my way.  That is expected.

Nothing enrages the mob (aka the "Open Source Community") more than speaking the truth publicly.

community logo
Join the Lunduke Community
To read more articles like this, sign up and join my community today
18
What else you may like…
Videos
Podcasts
Posts
Articles
Groupthink, Tech Journalism, & The Lunduke Journal

Why The Lunduke Journal uses the "10th Man Rule" to counter groupthink in the Tech Industry. (And why you'll definitely disagree with Lunduke sometimes.)

Stick it to Big Tech, 50% off everything at The Lunduke Journal:
https://lunduke.substack.com/p/stick-it-to-big-tech-50-off-everything

00:18:10
PSX Emu Dev Forbids Arch Linux Packages

DuckStation developer says, "Next step will be removing Linux support entirely, because I'm sick of the headaches and hacks." Specifically naming Wayland as a source of problems.

00:15:52
The Age of Non-Woke Open Source is Beginning

Non-Woke "Political Protest Forks" like XLibre & Redot are thriving. Non-DEl Linux Distributions like Open Mandriva are as well. But Woke projects? Not doing so well.

The Article:
https://lunduke.substack.com/p/open-source-political-protest-forks

00:21:04
November 22, 2023
The futility of Ad-Blockers

Ads are filling the entirety of the Web -- websites, podcasts, YouTube videos, etc. -- at an increasing rate. Prices for those ad placements are plummeting. Consumers are desperate to use ad-blockers to make the web palatable. Google (and others) are desperate to break and block ad-blockers. All of which results in... more ads and lower pay for creators.

It's a fascinatingly annoying cycle. And there's only one viable way out of it.

Looking for the Podcast RSS feed or other links? Check here:
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

The futility of Ad-Blockers
November 21, 2023
openSUSE says "No Lunduke allowed!"

Those in power with openSUSE make it clear they will not allow me anywhere near anything related to the openSUSE project. Ever. For any reason.

Well, that settles that, then! Guess I won't be contributing to openSUSE! 🤣

Looking for the Podcast RSS feed or other links?
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

openSUSE says "No Lunduke allowed!"
September 13, 2023
"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

This episode is free for all to enjoy and share.

Be sure to subscribe here at Lunduke.Locals.com to get all shows & articles (including interviews with other amazing nerds).

"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044
Reminder: 50% off all Lunduke Journal subscriptions through Friday (Tomorrow)

Just as a reminder, everything is 50% off through end of the day Friday (which… if my reading of the stars is correct… is tomorrow night).

Huge thank you to everyone who has picked up a new Lunduke Journal subscription this week! Couldn’t do this without you!

Here’s a page with all the details on how to snag a discount:

https://lunduke.substack.com/p/stick-it-to-big-tech-50-off-everything

And here’s a video with me jabbering on about how awesome you are (among other things):

https://x.com/LundukeJournal/status/1950400390765125729

And, yeah, the first link is to Substack. The second one is to X. Because… why not? The Lunduke Journal publishes everywhere (Podcast, Rumble, Locals, you name it). You can find all of the other links at:

https://lunduke.com/

Now go snag that subscription. Make Big Tech grumpy.

  • Lunduke

What Good Am I in the Age of GenAI Coding?

I am not an AI skeptic. On the contrary, I welcome the new overlords. (I’m kidding with the last part.) I know some are asking: “If AI is doing the coding, will human coders go the way of typesetters?”

I’d say we coders are going the way of buggy builders who became automobile builders. My metaphor needs work — but I’m trying to say: there will be more work for us, not less.

This week, my employer is training 250k of us on Vibe Coding. I’m ahead of the game, as I’ve been exploring GenAI extensively ever since ChatGPT rocked the world. Let me give a bit of a testimony about my Vibe Coding project — to build an accelerator: “just drop in your data” and have a prebuilt, industry-best-practice dashboard.

Step 1:
I’m not a telecom expert, so I had 4 different AIs do deep research on the topic. Then I had ChatGPT consolidate their findings into a “best of.” Now I have 50 telecom industry KPIs and their definitions to work from.

In a real project, I’d ...

Can I get an "Amen"?!

post photo preview
post photo preview
LibreOffice Developer’s Hotmail Account Locked After LibreOffice Criticizes Microsoft
“Wow that looks bad,” says Microsoft employee.

Mike Kaginski, a LibreOffice developer (who works for Collabora), has had his Microsoft-hosted email account, which he uses for open source development, locked for “activity that violates our Microsoft Services Agreement”.

 

Kaginski discovered this when attempting to send an email to the LibreOffice development mailing list (hosted by FreeDesktop). It remains unclear if that specific email (which he sent via another address and was rather bland and technical) was the reason for the ban… or if attempting to send the email was simply the first time the ban was noticed by him.

This happened just days after LibreOffice officially accused Microsoft of engaging in a “Lock-in” strategy by creating “artificially complex”, XML-based office documents.

Are the two events related? Hard to say with any certainty.

To make matters worse, Kaginski has had no success in getting Microsoft to lift his locked email account — with the company making him jump through numerous, impossible hoops (such as requiring him to sign in to submit an appeal for his account being locked… but not allowing him to sign in… because his account is locked).

You got that? Sign in to fix the account you can’t sign in with.

Gotta love a good Catch-22.

Good job, Microsoft.

The Lunduke Journal reached out to a contact, within Microsoft, who made it clear that their group was not aware of the LibreOffice Developer’s locked account, but they were aware of the LibreOffice complaint article regarding “artificially complex” XML lock-in. Adding, “wow that looks bad”.

The Lunduke Journal’s Analysis

The odds of locking a LibreOffice developer’s email account being an official Microsoft corporate decision seems highly unlikely.

Microsoft, as a company, makes a lot of bad decisions — but this would just be too stupid for words. A massive PR blunder.

But could a single employee, feeling grumpy, have done it on an impulse? As some sort of revenge for LibreOffice’s “harsh” words about Microsoft? Sure. That seems entirely plausible?

Though, it’s also entirely plausible that some poorly designed AI-driven “naughty activity” detection bot flagged his account. Or, perhaps, the developer was reported by some random Open Source hooligan who likes to cause chaos (there’s a lot of those).

Either way, the fact that Microsoft requires people to log in — on accounts which cannot log in — in order to file an “appeal” is incredibly amusing. And is very, very typical Microsoft.

Read full Article
post photo preview
Open Source “Political Protest Forks” Thriving
Many called XLibre & Redot nothing more than “political protests” that would quickly die and be forgotten. Boy were those naysayers wrong.

Over the last year, we’ve seen a couple of high profile forks, of large Open Source projects, which were inspired — in part — by a desire to move away from the political discrimination and Leftist Extremism within the original projects.

At the time, when each of these forked projects were started, many predicted that they would go nowhere. That they were nothing more than “political protest forks” — and they would die out quickly.

Let’s check in on both of those project to see if that has happened.

XLibre - The Xorg Fork

Since officially launching, at the end of June (last month), the XLibre project has published a handful of official releases (now up to version 25.0.0.5)… with a significant number of changes and fixes.

 

In fact, considering the significant new features (such as XNamespace Extensions), the first release of XLibre is larger (in every way I can think to measure) than any Xorg release in the last decade. With the number of contributors growing.

How about Operating System support? Many predicted that XLibre would be ignored by every Linux distribution on the planet. That it would go nowhere and nobody would use it.

According to the “Are we XLibre yet?” wiki, a number of systems have already (officially) adopted XLibre. Including: Devuan, Artix, GhostBSD, and (my personal favorite) OpenMandriva.

 

This is important to note: All of that support has occurred even though XLibre has only existed for one month. Several systems already officially supporting it is nothing short of “crazy impressive”. Borderline unprecedented.

In addition, a number of systems have 3rd party repositories which allow users to install and use XLibre. Including: Arch, FreeBSD, Gentoo, NixOS, Slackware, and (seriously) macOS.

 

In short: Growing group of developers. Rapidly growing platform support. New releases which put the original project (Xorg) to shame.

Redot - The Godot Game Engine Fork

The Redot project — which forked off of Godot back in October of 2024 — had a stable release (4.3.1) back in June, and just had a new test release (4.4 Alpha 2). Both with both new features and fixes.

 

In fact, Redot has had 13 releases since the project started late last year.

With an absolutely massive number of commits since then.

 

In short: Steady, new releases. New features and bug fixes. Both stable and testing releases.

These Projects are Thriving

It’s hard to look at either of these projects and come to any conclusion other than they are absolutely thriving.

At this point, it’s looking like those who predicted rapid failure for these “Political Forks” were not only wrong… but wildly, obscenely wrong.

There’s a lesson in there.

Read full Article
post photo preview
Groupthink & Tech Journalism
Why The Lunduke Journal uses the “10th Man Rule” to counter groupthink in the Tech Industry.

If my audience always agrees with me — 100% of the time — I’m probably doing something wrong.

That’s core to the ethos of The Lunduke Journal.

Any Brand X Tech Journalist can publish articles and shows filled with ideas, and facts, which their audience is known to already approve of. It’s easy to play it safe. To tell people — and corporations — what they want to hear. To pander.

We have enough Tech Journalists who do exactly that. Heck, we’re lousy with ‘em.

Put another way: The Lunduke Journal is not here to make friends. Not here to win some “Tech Reporter Popularity Contest”(tm).

Why The Lunduke Journal Exists

The Lunduke Journal exists to tell the truth about the Tech Industry (and world of Computing) — as I see it — no matter what. To tell the stories the other Tech Journalists are terrified of touching, for fear of losing that afore mentioned popularity contest.

The Lunduke Journal publishes leaks from major corporations — royally ticking off all of Big Tech in the process.

The Lunduke Journal shines a light on the discriminatory, DEI, & woke practices of Tech — causing nearly every Tech Industry person, with a Left-leaning political stance, to label me enemy number one (often attacking me, with wildly vulgar statements, in a desperate attempt to discredit me).

The Lunduke Journal investigates the shady business practices of Open Source Foundations and organizations — resulting in nearly every leader within the Free and Open Source world to either fear or despise me (often both).

In fact, The Lunduke Journal publishes stories — ranging from investigative pieces to pure opinion and analysis — which will, undoubtedly, infuriate (or at least annoy) every single nerd on this green Earth of ours.

Prefer Linux, Windows, or Mac? Left, Center, or Right politically? Pro or Anti-Government control over Tech? Star Wars or Star Trek?

Never fear. There will surely be a Lunduke Journal story which you will strongly disagree with. Just give it a little time.

Let me tell you why.

The Tenth Man Principle

Groupthink can be a very dangerous thing. Especially when you already agree with the consensus of the group.

There is a concept where, if 9 men all agree on something — an idea, a fact, a strategy — it is the duty of the 10th man to take a different approach. To pursue a contrary idea or strategy.

In some ways this is a variation on “Playing Devil’s Advocate”, but I prefer the “10th Man Principle” — it is more focused on challenging an entrenched consensus.

Which is where The Lunduke Journal comes in.

When I sit down and read Tech News — and listen to Tech Podcasts or Videos — and 90% of the coverage is all repeating the same position… whenever an extreme consensus has been reached… a red flag is raised. The 10th Man Principle is triggered.

My job is then to take whatever that topic is — a piece of breaking Tech news, a historical fact, an opinion on how Tech should be governed, etc. — and spin it around. Look at it from a completely different angle — and pursue that new line of thinking.

This isn’t about simply being contrarian for the sake of being contrarian.

I must investigate that topic rigorously. Focus on known, verifiable facts. Challenge any assumptions made (by myself or others) in whatever that consensus is. Dig deep. Dig where others have not. See where that investigation leads.

Sometimes that investigation leads to nothing overly interesting or worth publishing. Other times… the results are illuminating and profoundly valuable.

If you’ve followed The Lunduke Journal for any length of time, you’ve seen the results of this ethos. Over and over again.

And I Love It

There are, obviously, some challenges with this approach. To put it mildly.

Corporate sponsorship is — for reasons I clearly do not need to explain — impossible.

Luckily, The Lunduke Journal has an amazing (and generous) audience which keeps the lights on, making corporate sponsorship completely unnecessary. So Big Tech can kiss my tuchus.

On that note, getting employees of any Corporation or Foundation to talk “on the record” is simply not going to happen. In fact, many organizations have firm (and, often, stated) policies of “Don’t talk to Lunduke… ever”.

But, you know what? The brave whistleblowers within those companies have proven far more enlightening than any official statement from an executive could hope to be.

Oh, and that “Tech Journalism Popularity Contest”(tm)? Pshht. Forget about it. Not a chance. Not as long as I continue with the “10th Man Principle”.

If I’m doing my job right, the list of people who consider me an enemy of whatever entrenched, consensus position they hold… will continue to grow.

While, at the same time, the rag-tag group of Lunduke Journal supporters — those amazing nerds who see the need for this work (even though, on occasion, I publish something which challenges one of their deeply held convictions… or, perhaps, because of it) — will also continue to grow.

You know what? I wouldn’t have it any other way.

Read full Article
See More
Available on mobile and TV devices
google store google store app store app store
google store google store app tv store app tv store amazon store amazon store roku store roku store
Powered by Locals