dec05eba
kiwifarms.net
- Joined
- Jul 27, 2022
Why did such a chud even stay in bazzite when this is bazzites mascot?
Last names ending with berg is common in sweden, it's unrelated to jews
Open Source Software Community - it's about ethics in Code of Conducts
- Thread starter CrunkLord420
- Start date
-
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
- Joined
- May 12, 2017
Felicitations, fellow FOSS frens!
I have nothing to contribute insofar as drama discussion is concerned, but I do have wonderful news. I converted an old PC into a home server. For my first self-hosted service, I opted to go with Jellyfin. Fedora 43 has binaries in their repos, but I decided to go with Podman. Hours of troubleshooting obscure SELinux and
Accessible on my phone, laptop, and other computers via web interface and app, I have the Podman container set up as a systemd service to launch on boot, LAN-only, NFS+SSH is a fucking lifesaver. Metadata is a bit screwy at the moment, but nothing insurmountable. The old PC running Jellyfin is totally headless, VAAPI for video transcoding.
Plex definitely looks prettier and probably has some RichardStallmanAbsolutelyProprietary.jpg features that Jellyfin categorically lacks. That said: it looks really sleek and already shows tons of promise. Maybe I'll fiddle with a WireGuard setup to get Jellyfin accessible from cellular data, but for now? I'm enjoying the rush of not giving up and actually succeeding in one of these self-hosted projects for a change.
Now that I have such glowing things to say about the Jellyfin project, now I'm 99.99% sure that they're a project created, operated, or otherwise hijacked by insufferable troons who'll destroy the quality of Jellyfin with meaningless Rust integration that'll bork my system and expose my IP address if I ever set WireGuard up.
I have nothing to contribute insofar as drama discussion is concerned, but I do have wonderful news. I converted an old PC into a home server. For my first self-hosted service, I opted to go with Jellyfin. Fedora 43 has binaries in their repos, but I decided to go with Podman. Hours of troubleshooting obscure SELinux and
firewalld issues later, I finally managed to get it up and running! Accessible on my phone, laptop, and other computers via web interface and app, I have the Podman container set up as a systemd service to launch on boot, LAN-only, NFS+SSH is a fucking lifesaver. Metadata is a bit screwy at the moment, but nothing insurmountable. The old PC running Jellyfin is totally headless, VAAPI for video transcoding.
Plex definitely looks prettier and probably has some RichardStallmanAbsolutelyProprietary.jpg features that Jellyfin categorically lacks. That said: it looks really sleek and already shows tons of promise. Maybe I'll fiddle with a WireGuard setup to get Jellyfin accessible from cellular data, but for now? I'm enjoying the rush of not giving up and actually succeeding in one of these self-hosted projects for a change.
Now that I have such glowing things to say about the Jellyfin project, now I'm 99.99% sure that they're a project created, operated, or otherwise hijacked by insufferable troons who'll destroy the quality of Jellyfin with meaningless Rust integration that'll bork my system and expose my IP address if I ever set WireGuard up.
Last edited:
- Joined
- Jul 1, 2023
Trying to turn this into a binary (ironic, isn’t it?) between Rust and C is your only hope for relevance since you can try and make fun of C for being old. C is already there. You have to justify the enormous effort that will be required to replace it and probably can’t and this CVE suggests the value proposition you offer is even weaker than you claim.
- Joined
- Mar 4, 2019
GPL can't be used to stop nazis and chuds using the software. Any alteration to the terms invalidates the license and makes it incompatible with other GPL software.
- Joined
- Jul 13, 2022
Rust is the first of the new C-killer general purpose programming languages to enter into the running with the knowledge and understanding that successfully killing C requires deliberately attacking the existing libraries and codebases. Useful idiots must be motivated to tear down the white man's statues and infrastructure "rewrite in Rust". Julia and such languages thought it would be enough to just be a nice language in isolation, and that is why they never had a chance.
dame dudi jench
kiwifarms.net
- Joined
- Oct 2, 2023
If stallman had just prioritized LGPL, which forces companies to contribute back without making it impossible to sell software for money, none of this would be happening. GPL is communism, i don't know why people expect software devs to work for free.
Verdant
kiwifarms.net
- Joined
- Jan 21, 2024
For all the platitudes trannies make towards socialism and the like, they are influenced ridiculously easily by corporate propaganda. There's a big overlap between Rust trannies and a certain genre of person you encounter in the 'security' sphere who is obsessed with DRM systems, wants to work on them for a living and 'responsibly reports' exploits they find in them because piracy is bad (ignoring that these are the exact systems leading us towards a dystopia where you aren't allowed to run anything on your own hardware). At the end of the day they are careerists who are more interested in getting a sexy 300k/yr FAANG job than they are in any stated principals, and having popular MIT-licensed open source projects makes you way more hireable.
GPL is also simply 'uncool' due to its associations with the old world of chuddy FOSS, Stallman's bad behavior and the like. Of course corporate propaganda is a big reason why those associations even exist in the first place - the downfall of copyleft pretty much coincided with FOSS becoming more corporatized, full of people working on infrastructure software as part of their day job rather than basement hobbyists working on competitors to popular proprietary software.
- Joined
- Aug 21, 2018
Jellyfin will just werk with every reverse proxy that allows for websockets to be established. Mastering a reverse proxy will make hosting crap so much easier under a domain and behind a single IPv4.
- Joined
- Nov 21, 2020
I'll just assume you mean AGPL which is the one that requires SAAS to release code.
- Joined
- Aug 7, 2024
I thought bazzite seemed familiar to me from somewhere. Now I remembered it was a Lunduke video where he talks about their weird tranny mascot.
dame dudi jench
kiwifarms.net
- Joined
- Oct 2, 2023
No, because this stuff was getting figured out in the late 80s/early 90s and nobody could see where we'd be with SaaS in the 2010s. The point of departure where FSF could have pushed LGPL and deprecated GPL was in the early 90s.
GPL is counterproductive if you actually want software to get made, it results in less free software being made. That FSF hasn't tried to get everyone on AGPL is an implicit concession that the viral communist model has failed, and blowing up the commercial SaaS ecosystem won't magically lead to more open source projects getting built. It'll just create more proprietary software.
- Joined
- May 12, 2017
Excuse you, it's not a "viral" communist model. It's a "spider plant" communist model. RMS himself said as much when Steve Ballmer or some other Microsoft exec claimed the GPL was "viral" decades ago. I won't have you blatantly mischaracterising RMS's autistic jihad when the bloke's enduring cancer.
- Joined
- Nov 11, 2024
I don't demand it, but they seem so compelled to code that they choose to do so anyway. Kind of like writers and musicians - they're putting it out there for free, or without regard to piracy.
- Joined
- Mar 30, 2023
congrats! you will problably rebuild it once or twice as you better learn the sub components. I reccommend using sonarr and radarr to organize the video files, and they can also be used to automate downloading but follow the TRaSH to set up best practices and the rules for determining the best quality torrents or usenet files to choose from
dame dudi jench
kiwifarms.net
- Joined
- Oct 2, 2023
Props to you, not trying to call you out, hope it didn't read that way. But at large people do demand it, like all the wailing about that nginx ingress manager for kubernetes that is going away bc the standard had moved on, and the one guy maintaining it gave up. Or FFmpeg having a meltdown that Google runs automated security scans against it.Lots of entitled whining from GPLniks that large corps aren't supporting it for free and instead are building open source alternatives like envoy gateway.
the people that do this are the ones who are too maladjusted to get paid to make software for money. That's why there are threads full of awful FOSS lolcows and not ones full of for-profit developers. When people work for free it's bc they value power or fame more than money and those ppl are way crazier than someone just trying to pay for their mortgage and clock out. Moot is a great example.
Last edited:
- Joined
- Aug 4, 2019
Think like marx act like pajeet
Tiggie_Tiger
kiwifarms.net
- Joined
- Sep 12, 2020
Fucking preach it! I'm sick of devs jumping to whatever language, framework, or soyengine because some retard says it's good, without checking to know if it's actually good as a replacement. Herd mentality is a real thing in software development, and we're seeing real world issues this mindset causes, such as the broken mess Ubuntu's rustification (enshittification) currently is. It makes no sense to rewrite something in a different language while the already existing solution is lightyears more mature and has already received updates and fixes, over literal decades by programmers who are actually competent. What makes bad code 95% of the time, are bad programmers. The enshittification is amplified when programmers don't have a broad knowledge of the tools they use and the effects they have on systems. Assuming something is better without a solid basis as to why, is a disaster waiting to happen.
- Joined
- Jul 8, 2024
Eh... I don't think it matters what tools they use, they produce garbage anyways. Them using some "new and shiny
" framework just makes it more obvious.
- Joined
- May 12, 2017
I was wrong to cast suspicion at Jellyfin for an uncertain ideological future for the time being. Why? Because apparently, Nextcloud is a pozzed project. I'm sure I'm a few years late to the horrifying revelation, but what the actual shit?!
This is on the friggin personal & administrative settings panel. Right out the gate, you have options for pronouns along with Twitter, BlueSky, and fucking Mastodon handles too. I should've known something was deeply, deeply wrong with Nextcloud on an ideological level because I saw a BlueSky and a Mastodon logo when I first logged in with the admin account on the web interface. I know that NextCloud GmbH leaning heavily into the enterprise sector and basically neglecting home users is a feature, not a bug. That said... I wasn't expecting them to go full-on DEI insufferable HR lady Pride ERG white-collar-smile-while-having-a-stroke-at-work levels of enterprise.
Bruh this shit's so fucking unfair. I remember salivating when I first came across NextCloud in 2022, but I just didn't have anything good enough for a proper home server to run it on. You try running anything stronger than AdGuard Home on a 3B+, and then it makes sense why you're better off buying a mini PC with a Ryzen APU or an Intel NUC. I'm literally repurposing my previous PC, the very first one I ever built, as a headless home server... and it's now where there's a genuine risk of me running some turbotroon's hijacked, now-enshittified project that has a billion fucking LOCs of Rust that'll bork on a memory safety issue. A (presently) low risk... but it's a non-zero risk that's much closer to "1" than I find comfortable.
I'm being a touch facetious here... but just a touch. This is the self-hosted Docker image, this is entirely on LAN, and I did this more for proof-of-concept than "wait, what do I do after setting this thing up? Do I actually use it as a cloud productivity suite?" Furthermore, AGPL licensing is 100% promoted (at least back when this blog was written in 2016)... but then therein lies the problem where they're using the OSD definition, calling it "open source" instead of "Free Software."
I truly wonder if RMS stays awake at night staring into the infinite void above his ceiling, wondering what his lifelong pursuit of free software advocacy will become whenever he's called to dwell in his grave. So much tangible good, yet so much ideological subversion... and all from the people whom he sought to empower the most.
I'm sure I'll scrap and rebuild my home server and its services a billion times over; that's the nature of learning anything tech-adjacent you're enjoying the shit out of. Right out the gate, I'm kinda sorta kicking myself for using Fedora Cinnamon as a home server operating system instead of something like Ubuntu Server, Debian netinstall, or even Fedora Server itself. The Debian/Ubuntu ecosystem is so much more familiar to me because I've been using Debian variants in one form or another for ~15 years at this point, but it must be said... after years of stable comfort and predictability, it gets really fucking boring. Arch variants are for ricing and overcompensating for personal shortcomings than actual, semi-serious home server usage. I'm sure SUSE is great, especially after outliving Novell and coming out the other side independent, but I'm totally unfamiliar with their ecosystem and I've got no immediate incentive to use it. Maybe I'll do something with it in QEMU, but certainly not for a home server right now.
Back in May 2025, I wrote at length about my experiences with Fedora 42. Honestly? With Xorg and AMD hardware, Fedora's actually pretty damn ace. I'm using Fedora 43 Cinnamon as my daily driver OS on the new PC I built, and I also have Fedora 43 running on the boot drive of that same PC I was using back in May. This time, booting off a proper internal SSD while operating 100% headless, I'm actually able to fiddle with Fedora's enterprise, containerisation, and virtualisation technologies. That's something I wanted to try out, but it later occurred to me that booting off a USB hard drive would make testing things much fiddlier on the same PC I binge podcasts and play Dark Souls on.
Podman is excellent stuff, and I vastly prefer running a Docker image rootless in a vein similar to how you can do rootless jails in FreeBSD. It really is a drop-in Docker replacement, and any issues I have stem from either not paying attention to what I was doing or some easily (if painfully) resolved issues with SELinux or Firewalld. Podman services are seamless with systemd. I know, I can't believe it either!
systemd is... systemd, there will inevitably come a regression that borks everything and gets patched two weeks later, but by that point I'd still be pissed. Even so, services are 100% persistent, so Jellyfin is a startup process every single time.
I have no love for Firewalld and SELinux. I'm much more accustomed to ufw and AppArmor. I can appreciate the flexibility and granularity of Firewalld and SELinux as I must continue learning about both if I'm gonna keep doing these self-hosted container services. That said, SELinux's syntax is unbearably and unnecessarily complicated and Firewalld is... admittedly pretty tolerable once you get acclimated to it, but it's nowhere near as nice as ufw allow $insert_port_here.
Fedora Server is technically a more amenable option for my use case, but it really must be said... you don't get any blurbs about why you should use Fedora Server the way you would if you were downloading an image of Ubuntu Server, the official documentation is only good enough to get your feet wet with the basics of stuff like containerisation (only going in detail about systemd-nspawn-containers and not Podman... which is much more immediately appealing). At least with Fedora Cinnamon, I can plug a DisplayPort cable in and get an immediate graphical environment if I need to get more hands-on with BIOS options and stuff along those lines. At that point, might as well just stick with it and and use both SSH and Perplexity to pull answers from proper sources and apply them for troubleshooting or setup purposes.
Cockpit? This is what I have the most praises to sing about. Whenever you log into Fedora via SSH, it'll tell you that you should set up cockpit. Once you set it up and open up the port via
firewall-cmd, you take the server IP and the port you opened (i.e. 192.168.1.XXX:9001), then you're greeted with... and I shit you not... an admin control panel that gives you a birds-eye view of your entire computer. You have live metrics about resource usage, processes loaded in memory, network devices, and stuff along those lines. But that's not where it ends... no, the admin control panel with the fucking terminal emulator available in your web browser isn't even where it begins.
Apparently, Cockpit is also capable of managing accounts and groups, enable/disable systemd services, and even manage virtual machines. You need to install an additional package called
cockpit-machines and refresh Cockpit for it to show up. Provided you have virtualisation enabled on your BIOS, you can set up actual virtual machines entirely from this browser-based admin control panel. This is amazing stuff, there's tons of flexibility and power present. You're staring at the infinite abyss of possibility, knowing that your only limit is bashing your head against a wall because you didn't correctly copy/paste something an hour or two ago. There's just one big problem...The documentation for Cockpit is fucking awful. Not only that, but there's hardly any "mainstream" discussion about Cockpit, let alone Fedora's sheer flexibility as a home server.
a) There are parts of Fedora's official documentation that teach you how to set up and manage various types of virtual machines through Cockpit. There are other odds and ends like that throughout official Fedora documentation. You don't, however, get the "Cockpit 101" rundown anywhere in
docs.fedoraproject.org that tells you what it is, what it can do, how you can do it, and places elsewhere to learn more. As much as I like learning how to set up VMs in Cockpit, I can't help but feel like I'm supposed to hit the ground running instead of getting acclimated.b) Literally every single fucking review of Fedora I've read in the last 15 years from Dedoimedo to Distrowatch to Tuxmachines and everything else in between only focuses on Fedora as it pertains to conventional home use. Browsing the web, multimedia playback, general productivity, stuff like that. It's fine, I get why that is... but do we really need the umpteenth review by Jesse Smith where he ends the review saying something like "Fedora's great once you have RPM Fusion set up, but it's nowhere near as nice as Linux Mint or MX Linux?" Do you expect the usual cavalcade of Linux slop tubers like Linux Experiment, Michael Tunnell, Distrotube, or Brodie Robertson (eugh) to talk at length about this stuff? Or do you expect them to give surface-level "what's new" videos and talk about Wayland gaming, Red Hat's latest controversy of the week, or anything else along those lines? Home lab channels I've looked at like Raid Owl do great rundowns of general purpose "convert this old PC into a home server" and talk about stuff like Proxmox, OpenMediaVault, Docker, and stuff like that. Y'know what they don't touch upon? Headless Fedora where you're controlling your entire system via Cockpit and have the latest and greatest system libraries and packages, and some insanely flexible options right out the gate.
A lot of this is self-inflicted because official Fedora documentation is scattered, variable in quality, and doesn't go into sufficient detail the way something like the FreeBSD handbook does. Even so, there's just so much left on the table when discussing Fedora once you stop beating the dead horse about its ergonomics (or lack thereof) for home desktop use. Would be nice for someone to actually talk about all this enterprise headless home server crap and make worthwhile content for it.
- Joined
- Jul 13, 2022
You know firewalld has failed as a concept when you're entering direct netfilter rules into it anyway. And your first SELinux system, as either a sysdamin or a developer, is an endless gauntlet of things that used to work perfectly, just not doing so anymore. You will literally waste hours trying to fix configuration that should work and has worked, until you learn to always blame SELinux first and check whether it is stepping in.