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

Anecdotal experience is not enough to say this is a broad issue, but my point is that when an average user encounters graphical issues within 60 seconds of using it, maybe it's not ready to be made the default! It was only within the last 6 months that OBS stopped segfaulting when trying to launch on Wayland.
Its weird to me how he talks about OBS segfaulting until 6 months ago and yet he does not mention once what enviornment or distro he is using. For me OBS has worked fine for 3+ years now on Arch Linux both under SwayWM and KDE wayland, only segfaulting when I was having driver issues or plugin issues. As much as Anecdotal shit is fine in an opinion piece at least provide basic info besides "this happened to me!!!!!" because the environment where it happens matters more than just pointing the blame on Nvidia or Wayland as a whole. Also I think his title is shit and really should be changed to "Wayland is a heap of garbage I cant stand, and is probably the same for many others" :reply:
 
Its weird to me how he talks about OBS segfaulting until 6 months ago and yet he does not mention once what enviornment or distro he is using. For me OBS has worked fine for 3+ years now on Arch Linux both under SwayWM and KDE wayland, only segfaulting when I was having driver issues or plugin issues. As much as Anecdotal shit is fine in an opinion piece at least provide basic info besides "this happened to me!!!!!" because the environment where it happens matters more than just pointing the blame on Nvidia or Wayland as a whole. Also I think his title is shit and really should be changed to "Wayland is a heap of garbage I cant stand, and is probably the same for many others" :reply:
>It's just a protocol
This was addressed in the piece
 
False. Pipewire contains a superior Pulseaudio implementation to the official PA release and has a fully functional PA server implementation. My preferred UI, python-pulsemixer, works better for my use cases on pipewire-pulse than native PA. Integrates with EasyEffects, even. It's redeemed Pulseaudio as a protocol because Pipewire makes it bombproof.
But how well does it hold up as a JACK implementation?
 
Holy gem. It really is a shame that the core devs of Wayland are such unabashed faggots, there's tons of good Wayland-specific software out there that would benefit from fully decoupling them, i.e. Hyprland.

Edit: peep this https://gardenhouse.pinkro.se/, its a guy making reconfigured systemd elements for standalone use. Saw it in the Guix mailing lists in reference to Gnome's ever-hardening systemd dependencies with the implication that the dev for this may be able to put together shims and such for avoiding further enshittification, both for Gentoo and Guix. Might be an interesting thing to keep an eye on as things develop.
 
Last edited:
Doesn't even mention Xlibre lol. Impressive archives. Very nice.

Good news! More Potteringware!
This time he's working on Trusted Computing for Linux.
Oh boy, I can't wait to be refused access to my bank account because I'm not using a Trusted™ GoyTerminal™. Don't worry, they've got GoyLinux™ by Micros- I mean Amutable for all of us power users out there.
I somehow missed this until now but I am gracious so I will be accepting apologies for not believing me about secure boot until the end of next week.
 
I somehow missed this until now but I am gracious so I will be accepting apologies for not believing me about secure boot until the end of next week.
No, you don't get it - that gun they're assembling against your head doesn't have a firing pin in it right now so it's OK.
Plenty of very lucrative slave farms are using compliance headsets. They just need to put them in every model for your safety.
Yes, Microsoft put firing pins in the Windows 8 ARM ones. They probably won't do it again.
 
8949 - soybooru.com - stubble nucob headphones closed_eyes poyopoyo animated soyjak cobson smi...gif
 
Rare high-quality schizopost from our friends at /g/

It's a surprisingly well-sourced and exhaustive paper on the subversion of the OSS world by bad actors (the rise and fall of coraline, the nixos putsch, the LLVM purge) who try and run it into the ground with HR and compliance bullshit.
 

Attachments

Rare high-quality schizopost from our friends at /g/

It's a surprisingly well-sourced and exhaustive paper on the subversion of the OSS world by bad actors (the rise and fall of coraline, the nixos putsch, the LLVM purge) who try and run it into the ground with HR and compliance bullshit.
I'm about to read this but... duh? Obviously? They did the same thing to occupy wall street. Is this really a controversial position?
 
Cynically, there's a breed of person who can't accept anything as truth, not even the input of their own senses nor their own faculties of reason, until it is presented to them in the form of a scholarly paper.

Less cynically, it is healthy to be skeptical of claims of conspiracies of subversion and want to see some evidence backing up those claims.

This paper looks like it will be useful for both cases.
 
Last edited:
Rare high-quality schizopost from our friends at /g/

It's a surprisingly well-sourced and exhaustive paper on the subversion of the OSS world by bad actors (the rise and fall of coraline, the nixos putsch, the LLVM purge) who try and run it into the ground with HR and compliance bullshit.
Thread tourist but why can't the "evil chud nazis" just make their own software without the trannies?
 
Thread tourist but why can't the "evil chud nazis" just make their own software without the trannies?
Boil the frog principle more often than not.

You let in some people to help with good intention, they let in some people with less than good intention who let in people with no good intention and before you know it it's Joever.
 
Thread tourist but why can't the "evil chud nazis" just make their own software without the trannies?
This is asinine. Who knew Null's problems with payment processors would be solved by making his own payment processor? Frankly I'm surprised no one has suggested this yet. You should @ him and tell him (I wouldn't want to take credit).
 
You let in some people to help with good intention, they let in some people with less than good intention who let in people with no good intention and before you know it it's Joever.
It's more methodical than that. It starts with a PR to introduce a code of conduct. If it goes through, maintainers are picked apart looking for any little thing. Discord messages, tweets, comments on github issues. When there's leverage, suddenly the project needs a "community moderation" board, basically an "elected" group of a few people to weed out problematic users. Truthfully though, they don't even need this. They can just look at other people being mean and that's enough too. Can't be mean on github! You MUST implement the COC or people will feel unsafe!
Have a COC already? Tough shit, that one sucks and we want this one instead.. Anyone that doesn't suck down the new COC or is problematic in any way is unceremoniously cast aside.

If the PR doesn't go through, the project is clearly ran by nazi chuds and any collaborating companies or sponsors are suddenly having girltalks at 2am.

The COC is a trojan horse to smuggle in trannies and faggots under the guise of "this project needs to be welcoming to everyone!" - however the people that are made welcome don't ever contribute anything. Unless you count moderating a discord server or posting tweets as contributions.

edit; I say elected but they're not really elected. Can't have a board without a tranny right. They need to feel represented. Add in a woman, a POC or 2 and suddenly you already have enough people to police the project. You get the gist, they're just seeding people who'll tow the line.
 
Last edited:
It's more methodical than that. It starts with a PR to introduce a code of conduct. If it goes through, maintainers are picked apart looking for any little thing. Discord messages, tweets, comments on github issues. When there's leverage, suddenly the project needs a "community moderation" board, basically an "elected" group of a few people to weed out problematic users. Truthfully though, they don't even need this. They can just look at other people being mean and that's enough too. Can't be mean on github! You MUST implement the COC or people will feel unsafe!
Have a COC already? Tough shit, that one sucks and we want this one instead.. Anyone that doesn't suck down the new COC or is problematic in any way is unceremoniously cast aside.

If the PR doesn't go through, the project is clearly ran by nazi chuds and any collaborating companies or sponsors are suddenly having girltalks at 2am.

The COC is a trojan horse to smuggle in trannies and faggots under the guise of "this project needs to be welcoming to everyone!" - however the people that are made welcome don't ever contribute anything. Unless you count moderating a discord server or posting tweets as contributions.
Exactly why BDFL is the only remotely successful governance method when it comes to any Free Software or Open Source project. It takes a dedicated hand to keep malignant agents away from the governance of a project. And it rings true constantly, the Nix guy failed to exert power, now Nix is Troonix. Same with Void, head dev ousted, trannies move in. Ian dies, Debian becomes Ranjeetian. Slackware, OpenBSD, even arguably the Linux kernel itself, are all still in a decent state thanks to their respective BDFLs.
 
Back
Top Bottom