I don’t support the change. That’s not my point. My point is that if we’re going to argue the dev being threatened isn’t a victim because he’s actively harming privacy, we should be aware that the changes he proposed are not actually harming privacy at all.
Age verification laws: slippery slope. Sure. I agree.
Adding optional age field to systemd userdb: not slippery. Systemd isn’t being weaponized as an age verification suite. It’s just not happening.
You don’t, and you don’t have to fill them in with accurate information, so it isn’t.
It’s mostly not going to be used at all.
As I said, I also object, but you have to realize you’re literally just doing the slippery slope meme unironically. The part that makes it a fallacy is the unjustified assertion that more egregious changes are the inevitable result of the first one, except the first one is materially harmless and in line with existing PII fields in userdb. It’s completely reasonable to expect systemd to go no further than it already has.
No, it literally just can’t violate your privacy in any way. You have complete control over what, if anything, is placed in that field. No information about you can be gained or disclosed by virtue of the systemd change alone. You can think it’s a bad change because it signals intent to follow a trend of supporting privacy-invading age verification, but you can’t say this specific change in itself is privacy-invading.
“user is likely accessing service from a *nix device” isn’t PII. of course anything can be used for fingerprinting, but this type of “leak” is about as insignificant as it gets. It’s not what most people would consider a violation of their privacy.
It may be inconsequential in a literal sense if the law isn’t enforced meaningfully, which is probably pretty likely. I don’t really care what California law says and I doubt they’ll try to convince me.
I don’t think the changes in question are “upholding” any law, but rather giving system admins and software devs a convenient/predefined way to attempt to comply with the law if they choose. “Upholding” the law would be requiring the field to be filled or checked.
That said, to your point, if someone proposed a race field “so that devs can implement segregation if they choose,” I’d find that reprehensible even though it doesn’t do anything on its own. Similarly, I object to the systemd change.
Do you think that would prevent or discourage age verification software from existing? It’s not as if a systemd user field is the only place a user’s birthday could be stored.
Realistically, age verification software that is seriously attempting age verification isn’t even going to touch the systemd field, because why would it? The field could only be trusted if it is managed by an age verification service anyway, in which case the service could just as easily store the data outside of systemd.
what is stopping him
The pull request approval process? It’s quite easy to recognize that one change is harmless and another is not. The slope is not THAT slippery.
I completely understand objecting to the systemd change, I also object, but acting like the fascists have already won is a bit crazy.
Adding birthday fields is not privacy invading in itself.
It is, but the amount of math that relies explicitly on ZFC without being about ZFC is relatively little. Most people don’t think about a particular formalism and the shift to a new one would likely be transparent
For video, bitrate is definitely king. 4K high bitrate just gets insanely large. I opt for 1080p bluray quality when available over 4K usually. I looked into AI upscaling for video recently and it can be pretty good, but it’s a technology that changes fast so I’d rather store the original resolution and upscale in real time later (if at all).
For games, I find even FSR2 upscaling from 1440p to 2160p is excellent as long as it’s implemented properly (i.e. scaling the 3D world and not the UI), and FSR3/4 even better.
27" 2K is a good DPI. I personally only went up to 4K 27" because I also wanted OLED, and the 2K OLED panel I was using had some noticeable text fringing because of the subpixel layout. At 4K it’s not noticeable anymore.
You’re probably aware of this since you mentioned bitrate, but a lot of 4K streaming services use bitrates that are too low to capture much more detail at 4K compared to a lower resolution. A lot of games will recommend/effectively require upscaling (DLSS/FSR/XeSS) to achieve good performance at 4K. All of this is still maybe better than 1440p, but it shows 4K is still kind of hard to make full use of.
It’s very noticeable at the DPI of a 27" screen from arms’ length. Or maybe not if you can’t see very well. But on a TV from 10 feet away, I dunno if I could differentiate 1440p from 4K personally.
Thinking has nothing to do with it. The positive context in which the bot was trained made it unlikely for a sentence describing a likely negative reaction to be output.
People on Lemmy are absolutely rabid about “AI” they can’t help attacking people who don’t even disagree with them.
LaTeX spitting out an immaculate pdf with carefully calculated text distribution and vectorized fonts just to have it printed and scanned by the camera on a razr flip phone:
People are using LLMs to diagnose disease, write prescriptions, deny health care claims, deny loans and grants, write scientific papers, review scientific papers, draft engineering and architectural documents, and talk to their loved ones
Despair