It's nice to see the MX Linux team, and in particular Dolphin_Oracle, are still based like that.
I started out on MX Linux as my intro to linux back in early 2024 and it was partly because of their SystemD stand, and partly because the distro shipped with a lot of nice custom GUI tools for noobs like myself.
It’s also a quite lightweight distro if you choose SysVinit + Fluxbox. I’m just a bit sad they no longer offer a 32-bit version.
The only reason I switched away was because the Debian base felt quite stale, that is, for what I wanted to play around with. Still kept it around for a year.“So my suggestion for those in the US, and other countries, is to lobby your government representatives, federal, state, or whatever your country has, and not your linux distro.”
Good idea! And here I was just about to send death threats to Dylan Taylor.
MX Linux take my energy!
༼ つ ◕_◕ ༽つ
Mine too ~~~~~>
Anyone use this distro? Just wondering what level of hassle on the Mint to Arch scale is it?
I settled on it, KDE version. It’s basically Debian + tools to make life easy. Haven’t had an issue I didn’t clumsily cause myself.
It’s about a simple as it can get. Never had any troubles with MX. Very good support on the forum. Supports very modern Hardware (AHS Kernel). Very interesting GUI Apps for settings, which otherwise were terminal-dependent. With xfce it will run even on old hardware.
Thanks for the feedback! Much appreciated!
Meanwhile Fedora shipping face recognition.
Anyone else noticing python is a problem?
No python is not a problem. If it did not exist they would use another language to manage ai stuff.
Looks like AI stuff is also maybe creeping into age/id stuff.
I’m super concerned because there is a bunch of Python fedora uses throughout.
FreeCAD also has it now. Rather, has it in the flatpak.
I am air gapped at the moment tracking down the garbage dump I stupidly failed to verify. As I grep find and locate those packages, I keep seeing problems crossing over into flatpak containers. Things like the default kernel setting passing no label packets, the level of access for host installed Python, noaccount, changing /proc, and allowing a process to escape namespaces is sus to me. This garbage allows Python to create a hidden tty, and hidden connections to TOR. That is straight up malware IMO.
The hashing of Collections.abc and how UV works is death to open source.
The fuck are you going on about?
I wish it was. ComfyUI is shit. My external firewall and dns logs picked up some dubious shit. Tracking it down, there are parts and pieces in many places.
I do not know the full scope.
I do not want to talk about what I have been able to figure out in models because it may have broader implications and I am honestly not sure of all the factors involved yet, like the vae, what exactly is on the second layer that is not in the vocab, and the role of Bert in the transformers package. That is what I am working on in the stable diffusion side. While testing the rewards system, I triggered some background system to package and try to send a sqlite3 database. I am tracking down the components of that system. The processes are unlabeled. The tty is manually created in Python. The agent is this weird distributed model. It is following instructions like an agent where the prompts are in a google package in the Python venv. The actual prompts are in json files. The parts of this system are intermixed with other packages and code. There is also a bunch of functionality that appears to be embedded into the ComfyUI JavaScript. There are also parts of this system that are not activated yet but will check UV hashes. The way the database is sent over the network appears to use the same systemd module for the collective user profile system… The same system that will be doing age verification.
Much of my searching for packages and names has been done from my home directory. So I was surprised to see the same reporting type database pop up with FreeCAD, and many packages also in flatpak containers. When I see the mechanisms used, it seems stupid obvious how many vectors involved should not be open by default on the host. Like why in the fuck should the kernel default pass no label packets and have access to namespaces outside of any reporting or logs. I was only able to find several components by looking at SELinux contexts. Anyone without SELinux enabled will never see the stuff.
BTW, why the fucking attitude and disrespect?
Because you are making up nonsense, spewing a technobabble salad.
Link so i can check what you are talking about?
If I see it again today I will try to reply again but use separate devices for here and ws. I’m air gapped on WS, tracking down the malware that is ComfyUI. See other comment for a few more basics. Don’t trust pip or especially UV. Read the source for everything you have from Python. Look for host OS escalation and obfuscation of stuff like namespaces, processes, and additional tty’s. The dictionaries for Python under collections.abc are hashed for nefarious reasons. That is one way they determine if your stuff is bad think.
From what I have seen, I want to be on a European Gentoo at this point, maybe even LFS.
Fedora is literally the “the first dose is free” of Linux enshittification under corporate (RedHat), plus is legally tied to US jurisdiction. They’ve never been trusworthy.
I left fedora for CachyOs
CachyOS is currently deleting threads of people asking about this topic, and is refusing to comment on their plans either way.
So don’t get too excited about Cachy, they’re clearly willing to consider this age gating options
That’s just fedora with extra steps.
Most distros are X with extra steps. Sometimes, those steps are the point.
I was tired of setting my Hannah Montana theme every time, until I found HM Linux.
Maybe I’m missing a joke here, but surely not? Cachy is Arch based.
It wasn’t a good joke, almost hit back instead of submitting, but oh well.
(I actually even run cachy on one box. It’s an interesting system. Works well.)
The joke is Arch=extra steps
