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

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.

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.

I know this comment is a joke, but the CA bill requires age bucketing for to be provided by the OS to “covered stores”. Basically, any source of 3rd party programs.

Since TempleOS (at least, the original one written solely by Terry Davis) has no networking stack, no such “covered store” can exist. I think there’s not even support to load external storage drives, so all programs on the machine are either written by the user or provided first-party by the OS. I think TempleOS would be exempt on those grounds.

I could get behind this if there was any actual decoration or community-oriented furniture in the hallway.

Maybe some fake plants, a bench/sofa, vending machines, etc. Any kind of reason to spend time in the hallway.

You make a good point, and one that I didn’t necessarily consider.

Maybe it’s naïveté, but I do still imagine this case could be hypothetically won without trampling section 230. Mostly because we have actual evidence that Meta designs their products to be harmful: Whistleblower leaks and books hace clearly demonstrated that management works to juice profits at the cost of users. Eg: Collecting data about users with body-image issues and selling it to beauty advertisers. When you can point to actual emails between decision-makers saying “Ignore this problem, it makes too much money for us to solve”, I’d hope the case would revolve around not letting people prioritize shitty business decisions at the cost of people. Then theoretically, as long as you don’t have a bunch of lemmy mods coordinating similar practices, the case wouldn’t apply to them.

Hmm, now that I type it out, that’s definitely a naïve take. I don’t expect to see actual justice against corporations in the USA any time soon.

• Customizability (hotline numbers, etc)
• Independence from billionaire-owned supply chains
• Encourages and strengthens local support networks

Seems like the case is about inherently addictive features of the website, and not about hosted content.

the lawsuit claims that this was done through deliberate design choices made by companies that sought to make their platforms more addictive to children to boost profits. This argument, if successful, could sidestep the companies’ First Amendment shield and Section 230

Wizards 1977

I love the cheap rotoscoped WW2 footage. I love the animation (and the backgrounds!). I like the plot, and I disagree with people who think it’s dumb that Blackwolf’s secret weapon for organizing the armies of evil is literal fascist propaganda. I love the scene where all the fairy armies get wrecked in trench warfare.

I also love the ending:

Prerequisites

Those look like build prerequisites. Many decomp projects do not need original game assets at build time, just runtime.

and after that…

cdpath and diskpath registry keys […] point to the correct location for the asset files

I read this as another implication that original game files are required. Otherwise, why would you need a registry key telling the new game engine where to look for assets? The /assets file in the git repo contains only 3 pngs of icon images. There’s no way they’ve secretly bundled a whole game’s worth of models and textures in the codebase.

Implication from the readme is that the lego island decomp does indeed need original assets:

The simplest way to use the recompiled binaries is to swap the original executables (ISLE.EXE, LEGO1.DLL, and CONFIG.EXE) in LEGO Island’s installation directory for the ones that you’ve built from this source code.

In the US it’s up to individual states to set laws that require breaks.

Fucking insane, and very sad.

I recall that during the cold war, US intelligence agencies were worried that American hams might be sending secrets to amateurs in the USSR. They commissioned some report and the findings were basically “The only thing these nerds talk about are signal reports and radio equipment”.