It looks more like a flatworm than a penis anyway.

Did someone ask for jank, dust, and cables?

This is weird to see, given I just finished watching all the Resident Evil movies the other night.

Your system may be reading the default config from /usr/lib/sddm/sddm.conf.d/default.conf, in which case the config file in /etc will probably be empty. You should not edit the contents of a default config.

The recommended location for sddm.conf is within the /etc/sddm.conf.d/ directory, so also check for files there.

In that case, it looks like you need to edit sddm.conf and set the HideUsers= field. Source.

The answer will depend on which desktop environment or login manager you’re using.

System users are not the right solution. The use-case for such accounts is when you want certain background services to be linked to a non-human account. Eg: Serving web requests from an http user account that only has access to nginx and the /var/www directory. By default, users created in this way don’t even have a home directory.

Bone ash apartments sound cool, no bad weather to spoil your visit. Plus, that’s how we get the Lavender town Pokémon tower IRL.

Why does it need a field for location and email?

https://en.wikipedia.org/wiki/Gecos_field#Format

https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/4/html/introduction_to_system_administration/s2-acctsgrps-files#ftn.idm140081194521120

What are you getting at me for? You asked a question and I answered.

I don’t care about any new gecos fields because they’re optional.

Because back in the 60s and 70s, people wanted to know whose print jobs were running and where the printed documents should be delivered.

My friend stores his drinks in a 30’s era monitor-top fridge. God help him if those chemicals ever escape.

The California bill was approved and signed into law back in October:

https://leginfo.legislature.ca.gov/faces/billTextClient.xhtml?bill_id=202520260AB1043

Actually, purge night would be a great chance to fake your death. Since all crime is legal on purge night, Bob won’t face charges of insurance fraud.

There could be a purge comedy about how boring old Bob from accounting broke into the morgue on purge night to steal a body. His original plan is to leave the body in his house and burn it down, sending the money to his wife who is dying of cancer. But then it turns out that the wife has hired a purge gang to kill Bob for the same reason.

It definitely will be a problem, but it will be a legal problem, not a software problem. Even if the systemd devs decided to revert this commit and never collect age data, the law would still be just a shitty as it is now.

If this law said that everyone needed to provide a phone number instead of a birthday, would everyone here be just as angry at the Bell Labs developers who wrote the GECOS standard?

Has anyone even looked at the PR? Why is there such a big stink about adding an optional birthday field to a JSON schema? It’s opt-in and can’t be validated in any way.

That’s like saying OpenSSL is the thin end of an anti-encryption wedge because they provide FIPS compliant modules. Or complaining that it puts your privacy at risk when you generate an SSH key and it asks for your address.

The problem is the laws getting passed, not with software that gives people a choice about whether to comply.

Home assistant integration saves the day: I built a small remote that lives next to my preferred viewing seat.

With one action, I can turn off the lights and hit play. Playback is then linked to the lights, so it pauses when anyone needs to get up and resumes when the lights go out again.

Not the person you’re talking to, but it seems like a stretch that some little nightclub will want to build and maintain their own smart contract infrastructure. It’s not just issuing the tickets, it’s also building and distributing the tools to quickly validate the hundreds/thousands of attendees every night.

For example, it’s not enough just to validate that everyone at the gate has an NFT. I could enter the venue with a valid token, and then transfer it to my friend still outside once I’m through the door. So now the bouncer needs to track what tickets have already been scanned, and you probably want it to update off-chain (faster and no gas fees).

Not that I can pretend to know what already goes in to a venue supporting TicketMaster, but I figure there’s got to be a reason why these middlemen were wanted in the first place. That reason is probably about venues wanting to do music and not tech support.

People like that have always existed, and always will. They live a life where whatever they ever wanted is right nearby, and they can’t imagine that the place which is good enough for them isn’t good enough for someone else.

I will say this: don’t let his attitude make you afraid of traveling. I’m always a homebody, but even for me there’s an excitement in being a stranger in a strange land every once in a while. Give it a try.

Yes, Todd, we get it.

You’re the one we shouldn’t trust.

I like coffee, and I avoid over-roasted beans and hate especially bitter coffee.

Over roasted: Burn the fuck out of your low-quality beans so that all flavor nuance is lost and every batch tastes identical.

Too bitter: Over extracted during brewing. It’s a skill issue, and even the darkest roasted beans can be prepared without excessive bitterness.

For me, an over-extracted coffee is never acceptable, but I don’t hate over-roasted beans if I’m at a breakfast diner.