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

  • 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
My mistake; I thought articles were released from subscriber-only distribution after 7 days, not 14.

Couldn't even send a proper 402 code.

For what it's worth LWN is one of the few news outlets in the $current_year that still holds on to its reputation and integrity.

Here's a link that bypasses the paywall: https://lwn.net/SubscriberLink/1061534/792ad3b59c3dc8c9/

It's just coverage of the same python library relicensing event, but instead of a soylent youtube thumbnail it's a proper technical article.
 
My mistake; I thought articles were released from subscriber-only distribution after 7 days, not 14.



For what it's worth LWN is one of the few news outlets in the $current_year that still holds on to its reputation and integrity.

Here's a link that bypasses the paywall: https://lwn.net/SubscriberLink/1061534/792ad3b59c3dc8c9/

It's just coverage of the same python library relicensing event, but instead of a soylent youtube thumbnail it's a proper technical article.
I then started in an empty repository with no access to the old source tree, and explicitly instructed Claude not to base anything on LGPL/GPL-licensed code. I then reviewed, tested, and iterated on every piece of the result using Claude. You can see the history of all the design and implementation plans that were used to create 7.0.0 here. I did not write the code by hand, but I was deeply involved in designing, reviewing, and iterating on every aspect of it.
I hate these people. HATE them. I can smell the stench of nigger cum and double mocha chai latte on this fucking faggot's lips as he blurts out "deeply involved in designing, reviewing, and iterating every aspect of it" as if it is anything more than a tacit admission that he's taken a steamy dump all over the project. Beyond writing slop that he """"iterated on"""", laundering this project into an MIT license states clear as day that he is an untrustworthy, faggot soy dev that should have the project forked out from under him ASAP. Fuck these stupid retards into the dirt.
 
You should never dumb down software so that it can be used by troglodytes. This is exactly how windows was created. GUI is bloated.
snobbish elitism gets no one anywhere in the end, if the hope is to elevate all peoples into being able to use computers in a non-niggerliscious and goy way, then making tooling easier without compromising core goals of decentralization and freedom are imperative.

Honestly, you can honestly follow this idea reductively down even back to the stone age: "You should never dumb down farming so that it can be done by troglodytes. This is exactly how industrialized farming was created. Hoes are bloated". It doesn't make any sense to be against progress merely because it makes things easier, especially if that progress can maintain respect for the end user's freedom.
every other Guix dot I see these days is Niri and I'm god damned tired of it. FOTM niggers, not even once.
infinite scrolling seems neat for my workflow thoughbeit.
Like a non-binary .CHM file on Windows? That would be nice.
looking into it, yeah. That system looks to be the best available comparison.
HTML doesn't need a web browser and it's a better fit for the underlying format at least, in my opinion. An info page needs to be hyperlinked throughout to be useful. Markdown can be transpiled to HTML by whatever you're writing it in.
I'm not opposed to HTML being the language that's ultimately read from, so long as there's an easier-to-use formatting mechanism that you can use instead. Markdown transpiling to HTML by a documentation system would be rather ideal. Combo that with a very easy-to-use reader and you'd have a very neutral format.

The only thing I'd put as a restriction is that the markdown has to be in pure HTML, or maybe even just a subset of it, so you can't have cancerous CSS and Javascript crap bloating up the docs. So long as each viewer just interprets the HTML in a consistent way for the viewer, it'd be a fine format to work with.
 
SCSI, which was intended to be pronounced "sc-si" like "sexy" but ended up being pronounced "scuzzy" by everyone.
Always wondered how he got his name.

Screenshot_2026-03-16_02-21-34.png
 
snobbish elitism gets no one anywhere in the end, if the hope is to elevate all peoples into being able to use computers in a non-niggerliscious and goy way, then making tooling easier without compromising core goals of decentralization and freedom are imperative.

Honestly, you can honestly follow this idea reductively down even back to the stone age: "You should never dumb down farming so that it can be done by troglodytes. This is exactly how industrialized farming was created. Hoes are bloated". It doesn't make any sense to be against progress merely because it makes things easier, especially if that progress can maintain respect for the end user's freedom.

To me this seems like a sliding scale. I can understand the argument that making software more accessible and usable is bad, especially given that the mdern attitude towards software seems to be one where everything should "just work by magic", no knowledge required. This is a deeply unhealthy attitude to have, as it renders the entire concept of learning and exploration meaningless or, even worse, a source of frustration.

How many people do you know in real life who simply get angry and go "Stupid thing doesn't work!" whenever some piece of software doesn't automatically do exactly what they want at all times. People don't troubleshoot, they don't reason around why something might not be working, and they don't want to LEARN how to use a piece of software. They simply want it to work by magic.

This is a really consoomer-focused and childish mentality and will keep them dependent on software vendors in the worst possible way. Helpless, controlled, and dumb.

I think a lot of people see this and conclude that the issue is GUIs, that we need to go back to good old command lines, and that making computers normie-friendly was a mistake.

Personally I think there are some jobs that are absolutely best done with a terminal, and seeing people trying to do them with a GUI always gives me a laugh (like batch image processing. Really awesome with imagemagick, hilariously bad trying to use Photoshop's or GIMPs built-in image batching wizards), and sometimes I get annoyed when I can't just batch-process things the way I want because a given piece of software ONLY offers a gui version, the best example in my case being Steam. I can mass-download steam games using steamcmd, which is good, but I have to deal with the slow, clunky, bloated steam UI if I want to actually do anything on the platform, including things like managing games, selecting controller configurations, etc. Why? I should be able to run it as a silent daemon using almost no system resources and call into it when I need it.

Anyway, to stay on-topic, it's imperative that we improve tooling in a way that encourages LEARNING, but unfortunately I think the current generation of computer users are too far gone and too stupid to actually learn anything about technology, so maybe the war is already lost. For over a decade now, the prevailing attitude among software developer and managers has been "make it so stupid a monkey could use it", and now all computer users have basically become as stupid as monkeys.
 
While systemd is retarded and also censors dissent, is there no reason I can't just lie about my date of birth?
Yes, thats the core reason the entire age verification idea is retarded and evil. If you do validation of the date of birth client side its all declarative. You cannot reliably determine the users age without a trusted third party because the user can lie. And if you use a trusted third party then in most implementations it can also censor and collect data about the user.
 

I'm honestly horrified there's zero push-back until the System76 guy, followed by a thread-lock. Just straight up implementation and compliance. Just one more reason I'll never go back to a systemd distro on any of may main boxes.

How would this even work on embedded systems? Are you going to be required to put in your age to setup a shitty Linksys router?

And to everyone saying "How is this enforceable? I can just put in Jan 1st, 1910," it's the first step. It starts with this retarded foot in the door. Once you have it, you'll be at full-on 'scan-your-government-id-to-use-your-phone' within 8 years or less.
 
Yes, thats the core reason the entire age verification idea is retarded and evil. If you do validation of the date of birth client side its all declarative. You cannot reliably determine the users age without a trusted third party because the user can lie. And if you use a trusted third party then in most implementations it can also censor and collect data about the user.
I'm not worried about date of birth because like people have said, anyone can just lie. My DOB on steam is 1901 i think.

What's more concerning is the can of worms this opens. When there's a serious push into this kind of things people will look to things like systemd who already gather a little bit of info and think, "well they're already doing this, lets just ask them to verify their age next". It's the 'boiling the frog' metaphor.
And what if i choose not to verify my age, or if i can't? Does my server just not boot? It's leaving a lot of questions unasked and unanswered.
What about where i live versus where the server is? Will californian laws force igor in uzbekistan to gather, verify and report my info?

What if i set my age to 9? Will debian maintainer Jeremy Bicha hunt me down and rape me? :stress:

Anyways, there's always devuan https://www.devuan.org/
 
Last edited:
How would this even work on embedded systems? Are you going to be required to put in your age to setup a shitty Linksys router?
No, not at all, because these laws are all drafted in such a way that they're required only if your operating system vendor provides for a covered application store, where a covered application store is one that distributes applications from third-parties. I doubt very much your router has a copy of fucking apt-get (or whatever) installed.... but even if it does, as long as you're using an OS where they simply fork what everyone else is using and take responsibility for it then they're not running a covered application store and the law doesn't apply to them.

Honestly, I wish more people would read the actual text of these laws. There's way too much bullshit circulating about them.
 
No, not at all, because these laws are all drafted in such a way that they're required only if your operating system vendor provides for a covered application store, where a covered application store is one that distributes applications from third-parties. I doubt very much your router has a copy of fucking apt-get (or whatever) installed.... but even if it does, as long as you're using an OS where they simply fork what everyone else is using and take responsibility for it then they're not running a covered application store and the law doesn't apply to them.

Honestly, I wish more people would read the actual text of these laws. There's way too much bullshit circulating about them.
2026-03-18_15-38.png
So, yes, my PFSense router likely counts.
2026-03-18_15-40.png
They run an application store(packages) and include horrific applications like Squid that shouldn't be used by anyone, of any age.
2026-03-18_15-42.png
 
Not trying to completely negate the worries over government overreach and spying, but it seems that Meta are biggest ones lobbying for these bills. The biggest push for this are from the likes of Facebook and their banal desire to avoid liability for things like collecting ad data on underage users or kids seeing porn by pushing it onto places like app stores and OS publishers. Plus it probably makes it easier to collect data on users without the liability even if there's nothing stopping you from lying about your age, since most normalfags would probably just enter their actual data of birth into the machine.
 
Who the hell picked that verbiage. Every electronic thing since 2000 is a computer, you can't say that the law applies to computers and also to more specific types of computers. That doesn't make sense, they're already covered by the base case.

Whoever wrote that probably meant to say "(...) to users of a personal computer, a mobile device, or any other general purpose computing [device]". Now that starts to make some sense, since this would exclude routers and servers, since they're not personal computers or general purpose. Yeah, I know you can do general purpose computing with a router or server if you really want to, but that shouldn't count, since it's like saying that a drill is a hammer because you can hit nails with it.
Who do I contact to make it so that even if they put a stupid law in, at least it makes logical sense as written

I don't like the term "mobile device" tho, it sound meaningless if you go all pedantic lawyer on it

Another thing to ponder is, whether software packaged by the distro maintainers is first-party software. I'd argue that it is, since it's picked by the maintainers who are part of the operating system distribution provider organization, who then fuck with the code a bit and package it and not uploaded by some random unrelated guy to the Debian Apt Store™.

Flatpaks also don't count since they're "software applications that run exclusively within a separate host application", even though they are uploaded by some random guys.

But if they really meant just "computer" then that's retarded
 
Back
Top Bottom