"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.
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.
I'm aware. You seem to be equivocating on the word "emulate." Nobody called WINE an emulator. The design and behavior of NTSYNC is meant to mimic that of NT synchronization primitives.
Assuming this "AI NPC" is a functionally useless jelly blob that says jelly-blob things on occasion, "smoke and mirrors" may be good enough. I don't think it's supposed to be gameplay-driving or deep, just amusing.
Okay. Parts of WINE emulate parts of Windows in order to function. The NTSYNC driver emulates NT synchronization primitives.
Can't speak for this person as I wouldn't have volunteered to make these changes myself, but it's possible that he thinks implementing "harmless" versions sooner can provide a legal basis to decline to provide "harmful" versions later.
I'd personally wait for the legal challenges against non-compliant systems before moving into malicious compliance if necessary.
- Data: utterly OP, can't not take Data
- Troi: always helpful when people are involved
- Riker: good leadership while being more physically capable than most captains, bold enough to endanger himself and his crew if necessary but smart enough to avoid it if not
- Bashir: Can handle any medical emergencies and, again, highly physically capable compared to other medical experts
This is true and expected, the point of NTSYNC was to be a more faithful emulation of Windows synchronization primitives, so increased compatibility and correctness. If it's ever faster than esync or fsync it's just a bonus. It's on par generally, though.
YoRHa is the military organization consisting of androids (humanoid machines like 2B) which exists to fight the Machines (robots constructed by aliens) on behalf of humanity.