Open Source Software Community - it's about ethics in Code of Conducts

  • 🏰 Deploying update to the Tatarus security page. If you encounter issues, post here.
  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
A lot of larger c*mpanies are concerned more with this faggoty invisible social marketing game than they are about producing quality goods, every employee needs to be a tow-the-line sucky sucky 5 dollar PR goylem first and a productive asset second. Attitude is the currency of choice so 'culture fit' supersedes 'craft quality' any day of the week, especially if you work for one of these zombie corporations that live off of hype and investor funding a la AI frontiersmen. Even past that, everyone is obsessed with image, it is the gayest shit imaginable and it trickles both up and down through the pozloaded negholes of both big corpo drones and individuals at any tier of business be it self owned or employed by another.
This is how Richrd Stallman sees the world lol. Yes, employers want ppl who are able to work in teams and be pleasant. People end up in open source bc they can't play nice with others and that's the exact reason the community is full of petty infighting and drama. People that just want to show up make money and go home are so much easier to deal with than ideologically motivated volunteers
 
Speaking of *BSD, has anyone else noticed how almost everyone on YouTube who talks about OpenBSD is just a poser? For example:
https://youtube.com/watch?v=_RO9beApnecMy assumption is that it's due to OpenBSD being seen as "The 1337 haxor OPSEC demon OS". I have never seen this issue with FreeBSD.
Blame the popularity of openbsd developers' blogs on things like HN and various subreddits (e. g. Ted Unangst).

In their defense they write very well.

This is how Richrd Stallman sees the world lol. Yes, employers want ppl who are able to work in teams and be pleasant. People end up in open source bc they can't play nice with others and that's the exact reason the community is full of petty infighting and drama. People that just want to show up make money and go home are so much easier to deal with than ideologically motivated volunteers
I'd say the opposite, you have to function better socially to contribute to open source than when you have middle manglement and a HR department to herd the cats, especially least in bigger orgs like KDE. Doesn't mean you have to be a social butterfly or not be on some spectrum, but you have to be able to deal with/compensate your own shortcomings if social stuff is difficult in open source.
The difference is that it's rather exceptional to have public posting about issues inside a corporate org, while everything in open source happens out in the open.
And then people never really think about it when social issues don't happen or are handled well (again, KDE's CWG has done a very good job there IMHO).
 
Speaking of *BSD, has anyone else noticed how almost everyone on YouTube who talks about OpenBSD is just a poser? For example:
My assumption is that it's due to OpenBSD being seen as "The 1337 haxor OPSEC demon OS". I have never seen this issue with FreeBSD.
Virtually every software youtuber is a poser, yes. It's not a serious place, I'll never understand what people think they're going to learn watching slop videos.
 
People end up in open source bc they can't play nice with others and that's the exact reason the community is full of petty infighting and drama. People that just want to show up make money and go home are so much easier to deal with than ideologically motivated volunteers

d say the opposite, you have to function better socially to contribute to open source than when you have middle manglement and a HR department to herd the cats, especially least in bigger orgs like KDE.
It's a bit of both depending on the scenario. Places like KDE or Canonical are run like a corporation because of the sheer size of the project. For this reason they also have all the pathologies of corporations, like peak of incompetence (peter principle), infighting, petty office politics and so on.

On the other ens you have extremely specific projects, think about a piece of software developed by 2 or 3 people for the past 20 years. They have no boss or HR departments, so they can behave however they like and the worst thing to happen is that someone will fork their code if they dont agree.

I would say both of these models have an equal tendency to accumulate or promote/protect toxic people. They will find a way to stay.

In a corporation they wont fire you until it's economically viable for them, if you are a one of a kind specialist you really would need to fuck up badly or harass someone to get fired. Similarly, in large open source projects there are irreplaceable people. And in small open source projects there is nobody to fire you.
 
Last edited:
I'd say the opposite, you have to function better socially to contribute to open source than when you have middle manglement and a HR department to herd the cats, especially least in bigger orgs like KDE. Doesn't mean you have to be a social butterfly or not be on some spectrum, but you have to be able to deal with/compensate your own shortcomings if social stuff is difficult in open source.
The difference is that it's rather exceptional to have public posting about issues inside a corporate org, while everything in open source happens out in the open.
And then people never really think about it when social issues don't happen or are handled well (again, KDE's CWG has done a very good job there IMHO).
You're completely correct, this thread is filled with insane lolcows in the open source community, but most communities work reasonably well or fail for lack of interest not drama. I still think that nets out to the lolcows are in open source specifically because of the absence of a profit motive, but that shouldn't besmirch everyone else.
 
And then it's like 40 minutes of video for one short paragraph of information
I have discussed this recently.
There are many, many worse offenders, which create videos which supposedly provide the viewer with valuable information, but instead prioritize entertainment, e.g. "TOP 10 Linux programs you NEED!" (which often times is just rust rewrites of already good programs).
I'm happy that they aren't posers for FreeBSD, and I hope it stays that way. I honestly don't know why one would choose to use OpenBSD for a primary computer, since it is noticeably slower than FreeBSD due to the security measures. For a server it is perhaps understandable, but even then, OpenBSD doesn't have ZFS and jails.
I will close my statement with this picture:
beastieblacksun.webp
 
I have discussed this recently.

I'm happy that they aren't posers for FreeBSD, and I hope it stays that way. I honestly don't know why one would choose to use OpenBSD for a primary computer, since it is noticeably slower than FreeBSD due to the security measures. For a server it is perhaps understandable, but even then, OpenBSD doesn't have ZFS and jails.
I will close my statement with this picture:
View attachment 9450468
With OpenBSD diehards, what I’ve seen is that it’s dogmatic philosophical allegiance overtaking practical concerns.

I’ve honestly seen a few decry FreeBSD as being “tainted” because of it being the foundation for NextStep and MacOS.

Even though Apple was a good citizen and advanced the BSD sphere by contributing back, that corporate involvement dirties it to the zealots in some bizarre Stallmanistic zealotry.
 
I just randomly stumbled upon this post again: https://daniel.haxx.se/blog/2026/06/24/a-cve-dispute/

I don't think Daniel realizes that literally everyone he's talking to is an LLM, even the MITRE mail is written by LLM (except the part where they quote Daniel):
1787277365317.png

(All the messages from the "security researcher" who doesn't understand how anything works are of course 100% LLM written.)

He really should set up some local, tiny and dumb LLM to autorespond to security stuff instead of wasting his own time.

The "curl summer of bliss" stuff really showed how overblown the security ramifications of LLM vulnerability discovery is, the marketing for GPT Sol, Mythos etc. has been pretty reckless and harmful (especially in hindsight).
 
I’ve honestly seen a few decry FreeBSD as being “tainted” because of it being the foundation for NextStep and MacOS.

Not quite right. NeXTSTEP (1989) predates FreeBSD (1993), and OpenBSD (1996) for that matter. As it became Mac OS X it absorbed some stuff from both NetBSD and FreeBSD, but it's unfair to say it's a straight lineage from FreeBSD. All the BSDs are pretty incestuous really.

As for OpenBSD, I think its value is not so much in the goofy little OS itself but in the various other programs and projects which have sprung up to support it and have ended up becoming useful if not ubiquitous in their own rights; OpenSSH, tmux, LibreSSL, some low-level networking stuff that only people like Null would ever really care about. When those are taken into account, the project as a whole has a much larger presence on the net than most would expect otherwise.
 
Last edited:
With OpenBSD diehards, what I’ve seen is that it’s dogmatic philosophical allegiance overtaking practical concerns.
You mean like pretending bugs that enable denial-of-service attacks aren't REALLY bugs just so they can continue claiming they haven't had a kernel bug in years?
As for OpenBSD, I think its value is not so much in the goofy little OS itself but in the various other programs and projects which have sprung up to support it and have ended up becoming useful if not ubiquitous in their own rights; OpenSSH, tmux, LibreSSL, some low-level networking stuff that only people like Null would ever really care about. When those are taken into account, the project as a whole has a much larger presence on the net than most would expect otherwise.
pf and iked (ipsec) were what did it for me back when I was using it, but particularly iked since it made setting up an ipsec tunnel genuinely easy. Eventually I got tired of there being large swaths of software that just plain didn't work or wouldn't even compile for it.
 
The "curl summer of bliss" stuff really showed how overblown the security ramifications of LLM vulnerability discovery is, the marketing for GPT Sol, Mythos etc. has been pretty reckless and harmful (especially in hindsight).
another issue is that LLMs can make shit up so if somone just has this shit automated you will eventually have line numbers and files that dont exist
 
I have a theory, or more likely a spergulation
did ai just kill bun?
releases: https://github.com/oven-sh/bun/releases
  • 1.3.5 Dec 17, 2025
  • 1.3.6 Jan 13
  • 1.3.7 Jan 27
  • 1.3.8 Jan 29
  • 1.3.9 Feb 8
  • 1.3.10 Feb 26
  • 1.3.11 Mar 18
  • 1.3.12 Apr 10
  • 1.3.13 Apr 20
  • 1.3.14 May 13
1.4.0 is still in the "oven", full of bugs and mostly developed by "robobun".
I suspect that the diarrhea that the AI shits out actually made the project unmaintainable.
View attachment 9401310
time will tell, but being 3 months without a release for bun doesn't seem good, based on their release schedule so far.
A week and some change later bun 1.4 has been released.
I am not here to "lick my wounds" or to "stand corrected" or some other such bullshit.
people have been upgrading to 1.4 in droves, so let's see some filed issues
RangeError: Out of memory: BigInt generated from this operation is too big — Bun fails on large BigInt multiplication that Node and Deno handle fine
await crypto.subtle.digest("SHA-256", buffer) in a macro cause Bun.build() to hang indefinitely in Bun 1.4
Segmentation fault using Streams wait. segmentation??
Next.js 16 cacheComponents + partialPrefetching: every request leaks unhandledRejection (NEXT_PRERENDER_INTERRUPTED, Date.now() bailout) under bun server.js — Node leaks 0
Heap peaks 1.4x to 2.6x above Node under sustained allocation before collecting
bun build --compile with sourcemaps leaks native (non-JS-heap) memory on every thrown error, proportional to error-path traffic
Bun 1.4.0 bun build --compile binaries are SIGKILL'd on macOS 27; 1.3.14 artifacts still run

uhhh, leaks, segfaults, zombie leftovers...

Bun v1.4 2-22 screenshot.png
 
The hubris of developers like Bun's Jarred, to think of code as pencil strokes instead of carvings in stone, growing their API surface to the size of the observable universe to accommodate shiny new features as required for staying relavent in the JavaScript world, while managing it with a bunch of AI agents...
Does not sound like a sustainable project, more like the software analogue of imperial overreach.
 
Part of growing up in the software engineering business is when you realize adding shiny new features is not inherently a good thing. I'm curious who pays for these happy little accidents because I do not believe there are people who are rewriting Node.js in Rust for pure fun.
 
Part of growing up in the software engineering business is when you realize adding shiny new features is not inherently a good thing. I'm curious who pays for these happy little accidents because I do not believe there are people who are rewriting Node.js in Rust for pure fun.
It's like translating the Bible into the Dark Tongue of Sauron.
 
Back
Top Bottom