None of the id fields in the systemd db are required to be filled. This is useless. Simply don’t put any personal info in, and bam, you’re already liberated, from laws that aren’t even in effect yet!
This is perfectly logical and I agree. Except that this controversy has prompted me to go learn about Lennart Poettering. I’ve been using systemd forever and I like it - I like journald and remote journald, I like networkd, I even deleted cron off my systems and use systemd timers exclusively. I knew there was some controversy about Lennart, but I didn’t really care. Now that I’ve read a bit about his background and, maybe more importantly, his new company - I don’t have a good feeling for the future of systemd.
What they’ve done, is in the user info field (which already has a ton of information that almost nobody ever fills out) they added a date of birth field. They do not control what it’s used for, who’s going to use it, or if the user will ever bother filling it out. Perhaps nobody will ever implement a use for it, it’s really nothing.
Context matters. Systemd did this as a reaction to frankly insane laws. They didn’t have to do anything like this, yet they did and comparing this to changing and creating files manually in vim misses the point entirely. Intentionally doing something is very different from a feature being natively present.
YOU control what info goes there, if any. It mandates NOTHING.
Until closed source or even open source programs demand an ID verified age from the OS. When that happens you are forced to unmask yourself and the systemd shit is the first step to making such an API possible. It normalizes genuinely insane demands that add nothing for the users except compliance.
This is pretty key. If they had added this field 8 years ago, absent any context of swarms of lawmakers salivating for personal info so they can find more children to fuck, or data to sell to their donors, then I wouldn’t have thought much of it. The timing is absolutely a critical element of the discussion. Heck, wait until CA has repealed its law, and admitted in embarrassment it was a terrible implementation of child protection, and maybe I’d even be okay with adding the field.
Putting it in now is very much like the nazi standing at your door, holding a hand close to your knob, insisting “I’m not actually searching your house and breaking your 4th amendment rights! I’m just standing here, for no particular reason!”
None of the id fields in the systemd db are required to be filled. This is useless. Simply don’t put any personal info in, and bam, you’re already liberated, from laws that aren’t even in effect yet!
This is perfectly logical and I agree. Except that this controversy has prompted me to go learn about Lennart Poettering. I’ve been using systemd forever and I like it - I like journald and remote journald, I like networkd, I even deleted cron off my systems and use systemd timers exclusively. I knew there was some controversy about Lennart, but I didn’t really care. Now that I’ve read a bit about his background and, maybe more importantly, his new company - I don’t have a good feeling for the future of systemd.
Finally someone who’s read into the issue
Will you still say that when they implement ID checking functionality?
Obviously not, that would be something very very different than what they’ve done.
What systemd has done is the following: They went “we speak for the distros utilizing our program now”
What they’ve done, is in the user info field (which already has a ton of information that almost nobody ever fills out) they added a date of birth field. They do not control what it’s used for, who’s going to use it, or if the user will ever bother filling it out. Perhaps nobody will ever implement a use for it, it’s really nothing.
No, what they have done is kowtowing.
What? It’s like saying systemd is handing the government your info because they have a field for your real name and address.
YOU control what info goes there, if any. It mandates NOTHING.
You may as well be mad at vim because your text editor is capable of storing your birthdate if you go in and type it and save it to /public/myInfo.txt
Context matters. Systemd did this as a reaction to frankly insane laws. They didn’t have to do anything like this, yet they did and comparing this to changing and creating files manually in vim misses the point entirely. Intentionally doing something is very different from a feature being natively present.
Until closed source or even open source programs demand an ID verified age from the OS. When that happens you are forced to unmask yourself and the systemd shit is the first step to making such an API possible. It normalizes genuinely insane demands that add nothing for the users except compliance.
This is pretty key. If they had added this field 8 years ago, absent any context of swarms of lawmakers salivating for personal info so they can find more children to fuck, or data to sell to their donors, then I wouldn’t have thought much of it. The timing is absolutely a critical element of the discussion. Heck, wait until CA has repealed its law, and admitted in embarrassment it was a terrible implementation of child protection, and maybe I’d even be okay with adding the field.
Putting it in now is very much like the nazi standing at your door, holding a hand close to your knob, insisting “I’m not actually searching your house and breaking your 4th amendment rights! I’m just standing here, for no particular reason!”
when that happens, I’ll build my own ISO with that part stripped out, or just move away from systemd
Will you still say that when aliens from the 19th Dimension verify your age rectally?
I don’t know what this derailment is ultimately trying to say honestly.
Yes, because I won’t be using their distribution.
deleted by creator
Yupp 100% optional.
for now