gtrcoi
I'm not concerned with the wider response, I'm concerned with this specific response to systemd which isn't motivated by any noble goal. These unwashed simpletons have coalesced into a smelly mob that needs to be quarantined. Maybe we can find a way to herd the sheep towards the thing they are actually mad at, but until that finally makes it through their thick skulls I'm fine with mocking them.
The slurs the forkers included in their descriptions would suggest that. I don't suppose you actually looked at them tho, performative outrage can't motivate that kind of minimal effort.
Where was your performative outrage when systemd added the full name data field in the same place? That is far more invasive information. Oh wait, they don't require that data field to contain a value either. It's almost like none of the technical details of the PR have anything to do with your stance on it and you're just big mad about something unrelated to systemd.
Oh wow, you don't even have a lie to pretend you're angry about, you just go straight to the slippery slope. Your entire outrage is based on something that doesn't exist.
Well yea, the people complaining about systemd are morons. They don't even know what they are angry about so they make shit up, and when their lies are exposed they hand wave at some vague slippery slope fallacy and cry. They deserve to be locked out of the discussion on official channels because they offer nothing but ignorance.
Again, it has nothing to do with systemd, and they aren't enforcing anything. You're just making shit up to get angry at. They are only providing a place to put the information that users (distro providers) can collect (or not collect) and use however they want. You should be grateful systemd is doing this because I can't imagine how ridiculous whatever solution all the lazy activists complaining about it would think up. It would ofc be no solution because the only thing those people can do is performative outrage from the top of the Dunning Kruger curve. If the next law enforces verification it still won't be systemd's problem because the only thing forcing end users to provide that info will be the distro providers, not systemd.
Also just because it's such an hilariously vapid argument against this PR, I fully endorse and support systemd adding a skin color data field. No distro will ask me to set it, no program will try to read it, and I will make it "kumquat".
It's funny seeing the few people who came in and started evangelizing about it get muted and booted, they completely deserve to be ignored and mocked alongside anyone bitching about this PR here.
Nothing about this looks bad, they are putting an optional dob right next to an already optional full name and email. People are losing their mind about it when an even more intrusive piece of data already exists in the same place. Idk about any of you losers, but I can't think of any time I've been asked to provide my actual name or email on a systemd machine. Maybe some optional field from a distro installer that the distro decided to ask for, not systemd itself. Their only concern with this is giving it a place of live that's appropriately secure, but you'd think they were the bad guys reading people yapping about it.
As soon as this actually becomes a thing I'm setting it to April 1st year zero like everyone else with a functioning brain will and not crying about it in a PR like some no-life activist.
You realise what you linked says the opposite right? That it says the dev of hyprland has been responsive to criticism of the community and that omarchy isn't hyprland and dhh isn't one of its devs?
Also that article doesn't give any information about what the hyprland Devs have actually done, just vaguely mentions past controversy in the same breath as saying things are better now and that the framework endorsement of hyprland is a minor issue for most people.
A) upload all of that to virustotal.com
B-Y) use a free alternative
Z) stick it in a VM, or wipe your entire system clean before and after using it.