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.
Every single one of these will fail. Every single one. Because none of them need to exist. The only purpose these serve is harassing the systemd devs for nothing.
These people are pathetic.
Removed by mod
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.
That’s what I was wondering as someone from another country. The answer is ofc because Americans are dumb af and constantly shooting themselves in the foot when fighting against “big” government. SSNs were supposed to be for just one thing, but because there weren’t unique identifiers for other things (healthcare id, tax id, welfare id, etc) every one just started using SSNs as a kind of defacto national id when it was never designed to be that. SSNs lack biometrics like photo verification for example.
To fix this they either have to actually create a more robust national id, or break it up into a bunch of area specific ids. Americans would likely complain about either option. My country does the latter, I imagine a lot of other countries do so as well.
Vertex explosions. Also some weird shader compiling stuff that I was able to solve.
For DD it’s actually fine but there’s this hilarious bug where the very last Cutscene causes the game to crash. I’m not even mad enough to try and fix it tbh, it’s just funny.
RE engine games like monster hunter and dragons dogma are a mess. I blame Capcom and NVIDIA, but because not everyone is having the same issues I do it’s safe to assume there is some Linux solution out there that isn’t documented. So I guess my pain point is lack of good documentation, a tale as old as time tbf.
Check the log
I was just about to comment on the page name glitch effect being pretty cool. Did you use some off the shelf solution for that or make it yourself?
I assume cinnamon uses the kind of methods talked about here: https://www.freedesktop.org/wiki/Software/systemd/inhibit/
I don’t know anything about freedesktop and I refuse to learn, but give it a read and see if you can use it for anything.
The systemd-suspend.service also runs any scripts it finds in /usr/lib/systemd/system-sleep/, which might also be respected by whatever cinnamon is doing, or not. You can read more about it here https://man7.org/linux/man-pages/man8/systemd-suspend.service.8.html
For that you’d basically put a shell script in that directory that checks if the $1 variable that is passed to it is either “pre” or “post” for suspending or waking up respectively and running whatever command you want. Again, this is hacky and might not work in all environments.
To add to the great response from @confusedpuppy@lemmy.dbzer0.com, amber would address one thing only: writing the syntax.
Most people don’t need it, and even if they had it would break the compliance in other ways besides syntax, but I’m sure there are people out there that know what they are doing who would appreciate amber.
Amber will still support bash stuff, or perhaps even other non-posix shells through the use of flags.
I get why this is useful, and it’s useful for me as well, but the perfectionist in me asks why target bash instead of posix?
deleted by creator