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

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.
Bollocks. Every Mikrotik router supports package installation and has user accounts for administration (standard practice is to create a new user for administration and disable the default user account named "admin"), so obviously that equipment is covered. Also probably every router made after 2000, TBH.
 
Bollocks. Every Mikrotik router supports package installation and has user accounts for administration (standard practice is to create a new user for administration and disable the default user account named "admin"), so obviously that equipment is covered. Also probably every router made after 2000, TBH.
Does it pull from the OS vendor's package servers? If not then they/you could argue that they forked everything for purposes of shipping that router, thus everything is first-party, and they don't have to comply. However, at least in the case of the California bill, there's already another out for this case:

1798.504(f) This title does not apply to any of the following:
(1) A broadband internet access service, as defined in Section 3100.
(2) A telecommunications service, as defined in Section 153 of Title 47 of the United States Code.
(3) The delivery or use of a physical product.
Finally, even if none of the above seems persuasive, you can always purchase or build your own hardware and put whatever you want on it. This law doesn't stop you from doing that.
Yeah so this guy claims to be 40, but all he does it watch that childrens' show My Little Pony (are Bronies even a thing anymore?). This is clearly a suspicious user; lock the account.
Let's be real: They're probably right and I for one fully support bronies being found out and sent to the glue factory.
 
I'd like to congratulate all the Arch, Catchy, Debian, Ubuntu, and RHEL users on getting what they fucking deserve. You earned it.

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.
I don't see how that negates the worries about government overreach and spying at all. Meta shares data with the feds that the feds could not legally collect themselves and further willingly censors viewpoints for the administration in power at the time. Meta being involved should increase worries about government overreach and spying.

I am considering making the switch as well, what is the best version of Artix for normal every day use?
I am in the same boat, just gonna choose openrc since I remember being told it is good.
I use OpenRC (with XFCE+Xlibre+Pipewire) because at the time it seemed like it had the most support + documentation (e.g. the gentoo wiki) and figured that was going to be the biggest issue. The only real issue I've run into is packages that don't have openrc init scripts. I've gotten okay at writing them myself and sometimes you can find a *-openrc package in the AUR that'll have it. I can't speak to the others as I never tried them.
 
Does it pull from the OS vendor's package servers?
They can, yes. They also provide package files to download locally for offline installation (via USB or just local LAN in case you're dealing with a router with no internet link).
 
I was considering Cachy, EndeavourOS or just straight Debian but after watching SystemD bend the knee to toothless legislation, I might actually consider Artix as a daily driver.

How inconvenient is using runit/openRC compared to SystemD for a daily driver? Do either grant any major improvements?
I'm using Artix OpenRC after switching from Arch and one of the things I hated the most about SystemD was that there was multiple ways of doing anything.

Like you COULD add something to .profile, OR you could make a systemd user service for it. Etc. systemd services were particularly annoying because it meant finding what was being run required looking in multiple places.

Honestly I might switch to runit because I just want Linux to get the fuck out of my way as much as possible and let me simply and easily manage stuff via a few files.
 
Pipewire is just a frontend to pulseaudio.
Actually it's a front-end to ALSA and merely compatible with pulseaudio shit.

I think what is needed is a complete scrapping of all these frameworks currently built over alsa. We just need to start fresh, and hopefully end up with something that works well.
To think, if Linux devs had just forked OSS like the BSDs, we'd never have systemd fucking everything up. Instead, someone decided they could just do it better and created the abortion that is ALSA, which poettering then couldn't make work on his laptop, and the rest is history.
 
Didn't know where else to post this:
1774022139530.png
Source (Archive)
 
Pipewire is just a frontend to pulseaudio.
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.
 
Back
Top Bottom