@newt Yeah, I know about that. There was also a somewhat big drama in FreeBSD about GamerGate I think. Although I don't like the idea of CoCs, FreeBSD at least did not go beyond that and I do not see major shenanigans in it's community every few months like it is on the Linux side. Probably because it isn't as popular and big enough for the corporate sponsors to poison it with their ideology.
@phnt just a reminder, FreeBSD people hired "diversity consultants" to help them draft their CoC and paid them around $30k, while the dude who actually worked on FreeBSD to add AWS support was asking for donations on Patreon.
I doubt it would've been great unless they ditched proprietary bits altogether, which they (much like the rest of BSDtards) insist it's not true, despite the evidence being right there.
@phnt that CoC incident resulted in several old time developers leaving the project, citing that FreeBSD Foundation should spend money on actual development and improvement of the OS instead of stupid virtue signalling. If you think Linux is fucked, FreeBSD is even worse.
But the main problem with FreeBSD is that it's dead and irrelevant.
@zaitcev@phnt it would have tons of drivers and hardware support if it wasn't under a cuck license. Companies using BSD don't have to share the code for their drivers, so they don't. RIP
@PurpCat@phnt@sally THIS FUCKING PIECE OF SHIT AUTOPLAYED WHEN I CLICKED ON THE THREAD FROM ANOTHER REPLY AND I WANTED TO PUNCH THE FUCKING MONITOR I FUCKING HATE HECTOR MARTIN I HOPE HE GET SSTABBED AND RAPED TO DEATH BY A MOROCCAN IMMIGRANT FUCKING NIGGER!!!!! @VIPPER I HATE THIS VOICE CHANGING FUCKING SOYDEV!!
@VIPPER@PurpCat@sally@meso Yes, marcan is Asahi Lina. Not officially, but both use the same hostname on the computer, the same KDE setup with different colors and why would Lina show the voice changer pipeline.
@PurpCat@phnt@sally@meso lol that's even better, because he (as Asahi Lina) recently entered into a relationship with some chinese vtuber (not sure if they're a tranny or not), hope they out him when he inevitably gets creepy lmfao, because you know that faggot can't act like a human being around another person
@phnt@PurpCat@sally@VIPPER >Brodie Robertson I hate that faggot so fucking much the powerful desire to curb stomp him wraps around me every time i see that fucking ugly motherfucker. he's sam hyde tier ugly, maybe worse because he's younger so less of an excuse.
@VIPPER@PurpCat@sally@meso The vtuber would be Cyan. The same vtuber that once did an interview with Brodie Robertson and a year later deleted all content on their YT channel.
@meso@PurpCat@sally@VIPPER I have to give him credit. He holds the second longest subscribe time of any Linux related channels on my accounts. I had to unsubscribe almost a year ago when his content became repetitive. Luke Smith is obviously first.
@meso@PurpCat@sally@VIPPER Like literally almost all content creators on Youtube. I was even subscribed to DT and Nick until I just couldn't handle the bad takes and cringe anymore.
@sally@phnt@newt >most GPUs after 2017 and a lot of NICs surely need proprietary software to work at all Ironically even the most proprietary nvidia GPUs still work without any proprietary software if you're happy with no re-clocking (nouveau can read the option EEPROM in the VBIOS without executing it and init the card to native resolution).
As for AMD cards, you do at least need to execute the nonfree Option EEPROM to get an image, but a similar thing to what nouveau does should be possible and you can often get native resolution by using the ATI driver.
Most wired NIC's just werk without proprietary software, but there are many garbage wireless NIC's and a few garbage (Broadcom) wired NICs.
Yes, that's why chads from FSFSA made Linux-libre.
> Most of the time you don't even have a functioning system without them.
Untrue, most GPUs after 2017 and a lot of NICs surely need proprietary software to work at all, but plenty of hardware still work just fine with Linux-libre, the real problem is that sadly there's not enough functional hardware for everyone, and I understand people choosing bricked hardware when there's nothing else left, but that doesn't mean people doesn't care about it.
This kind of rhetoric you bring here reminds me of the tranny jannies and other OSImps average speech to justify degeneracy, by the way, the people you complained about a moment ago.
> there are no proprietary bits in FreeBSD, as far as I'm aware.
As far as you're aware, exactly.
The problem is they don't have a disclosure policy in place, the only BSD distribution that cares about this is HyperbolaBSD, you need to go checking out their repos one by one to find the licensing nightmare that they are, plus plenty of binary-only software that is mostly part of the kernel, but still proprietary software nonetheless.
Hyperbola exposed how bad it is with all BSDs when they decided to switch away from Linux to OpenBSD, blessed they be for their job.
@phnt >since the Pentiums has microcode burned into the die itself that isn't even source-available That's hardware, not software.
I of course welcome fully free hardware designs and non-proprietary manufacturing techniques, but that does not exist, while fully free software does.
>A trustworthy proprietary-free software means nothing when you have untrusted hardware that can do whatever it wants. Proprietary software is pretty much guaranteed to be malicious due to the typical lack of consequences of malicious software and many cases of proprietary malware has been found.
Some de-capping enjoyers love decapping CPUs and reading out the circuit layout and microcode and so far no malicious circuits in x86 or AMD64 CPUs have ever been found (probably because why bother putting such hard evidence in hardware and having to hide it from everyone who makes and receives the hardware, when you can just do it in software?).
If I was Intel, I wouldn't backdoor the hardware microcode, as that is impossible to encrypt for performance reasons and also how someone is guaranteed to go decap the chip in 20 years - instead I would put a backdoor into the microcode updates and encrypt it and leave the instruction set documented (good luck finding it) and intentionally make the hardware microcode buggy, so almost everyone installs the software update.
>If the certification was written correctly, both of these scenarios would be incompatible >It would mean that almost no hardware would receive the certification It would mean that *no* hardware would receive the certification and a certification that doesn't apply to any hardware at all is completely useless.
It's up to *you* to make hardware up to your higher standard available and then of course the certification will be updated to your higher standard.
>The world where the FSF labels something as "respects your privacy" while it clearly might not simply would not exist. Even a backdoored CPU does respect your privacy until there is an attacker that exploits the backdoor and exfiltrates your private data.
Meanwhile, proprietary software is well known for being spyware that sends a bunch of stuff over the internet.
>In the real world, it means to me, that there's almost no point in trying to go fully free, when the result cannot be fully trusted. "Just give up on freedom as you can't be sure your privacy isn't always being respected".
>I simply cannot do my work on hardware that can even run Linux-libre. You can do work just fine on hardware that runs Linux-libre.
The vast majority of work with a computer only requires a computer with intel integrated graphics, or a 700 series nvidia GPU and a 1000BASE-T NIC, which GNU/Linux-libre works perfectly fine on.
I am confident you could do you work on Trisquel GNU/Linux-libre if you tried.
>I prefer the more pragmatic approach of using free software as much as possible, while also running proprietary software when I need to. Well, there it is.
You gleefully run lots of proprietary malware, but you're critical of people who run no proprietary malware and happen to use proprietary hardware?
>the Linux ecosystem A ecosystem is something that has naturally occurred that you just observe - you don't question if it is right for the owl to eat the mouse, you observe that it occurs.
The kernel, Linux was only possible because of GNU and what free software is built on is the floating island of GNU and how Linux is proprietary software is something I'm not afraid to point out.
>repelent for others that might want to switch to Linux If your mindframe is switching to "Linux" and thinking it will be exactly like windows or macos, rather than having a mindframe of escaping to freedom by switching to GNU, no matter the proprietary sabotage, you may as well not bother.
>using Librebooted ThinkPads is the only right way. Liebreboot is proprietary, so it's the wrong way.
The easiest way to get a system when you install only free software to the BIOS level is a GNUbooted thinkpad, but there are even better KGPE-D16 based systems.
My GNU/Linux recommendation is to install a free distro, but in cases of shit hardware, I do point out which components of the hardware won't operate without proprietary software.
>Yes, that's why chads from FSFSA made Linux-libre.
A deblobbed kernel means nothing to me, because every x86 CPU since the Pentiums has microcode burned into the die itself that isn't even source-available. A trustworthy proprietary-free software means nothing when you have untrusted hardware that can do whatever it wants.
That's what the FSF hardware certification program completely misses. If the firmware (and microcode) is unchangeable, it is defined as compatible with the certification. However if it is loadable on-the-fly, it suddenly isn't compatible. If the certification was written correctly, both of these scenarios would be incompatible, because both can run exactly the same firmware, while one is not compatible and the other one is compatible with some mental gymnastics. It would mean that almost no hardware would receive the certification, but also it would mean that the occasional customer wouldn't be deceived by it. The world where the FSF labels something as "respects your privacy" while it clearly might not simply would not exist.
In the real world, it means to me, that there's almost no point in trying to go fully free, when the result cannot be fully trusted. Yes, it has some advantages, but it is only a hobby project to me. I simply cannot do my work on hardware that can even run Linux-libre. And that's why I prefer the more pragmatic approach of using free software as much as possible, while also running proprietary software when I need to.
>This kind of rhetoric you bring here reminds me of the tranny jannies and other OSImps average speech to justify degeneracy, by the way, the people you complained about a moment ago.
It sort of makes sense, because I hate both extremes of the spectrum. On one side you have the annoying trannies licensing everything under MIT and actively sabotaging the quality of fundamentally needed software with their politics. And on the other side you have the annoying GNU maximalist that annoys everyone around them that isn't part of their group.
The former mostly affects people that already are in the Linux ecosystem by making it worse for everybody and making it harder to recommend to newcomers. And the latter acts as a repelent for others that might want to switch to Linux, but are effectively gatekept or repelled away by a minority screaming at others that using Librebooted ThinkPads is the only right way.
@PurpCat SunOS was always proprietary and distributed only in binary form.
As for Solaris, "opensolaris" had a bunch of proprietary software that wouldn't meet the typical definition of "blobs" (for example, proprietary source-available software is not a blob) and it's discontinued now.
So there will never be a free version of SunOS or anything derived from it.
@Suiseiseki If you read the last three paragraphs of the post you replied to correctly, you would have realized that I simply do not care enough about these opinions of GNUTards to read a wall off text. I do not care if you are right and I'm wrong.
Your opinion, or an opinion of anybody like you, will never have the desired effect on me and sway me into the direction of using more free software. In fact it will do the exact opposite the more people like you push it.