I find that move extremely funny, since it’s purely made for sensationalism and nothing else. I mean, if you hate how systems implemented age verification, then why don’t you remove its identity verification too, i.e. also optional fields for stuff like your address an e-mail that most users don’t even fill out.
There is no mechanism verifying what birth date you type in - you can type whatever date you want and systems doesn’t care.
I’d say no matter where you stand with age verification, this is the best solution to handle the situation. After all, any and all age checks we have nowadays are a black box anyways. There is no real knowing how other systems are checking ages, and there is AFAIK no real government mandated rules on how it is verified. They could make you scan your ID’s front, back, nuclear composition and dietary preferences and give you a result that is almost, but not quite, entirely unlike a proper age verification procedure.
If the government wants to introduce age verification, they have to do it themselves - build an API that handles the age verification, similar to how the digital ID in Germany works, as an example. If they want proper age verification, they also have to take the blame themselves if things go wrong.
This. And forking is easy. Maintaining a big piece of software is not. This is why every popular repo has hundreds of forks, but non of them are active or in sync with upstream.
You know I remember when age verification was a thing on porn sites.
No big deal, I was like 12 and could easily say “yupp, I was born April 20th, 1969” and there was no problem.
Now, in several states that has escalated to you showing your ID.
Do you think this is the end game? Systemd made it clear with this move that any kind of US law passed will be able to be honored by their architecture. They didn’t take a stand that you would expect from pretty much the entire Linux community as a whole.
And see the funny part is where you talk about “if the government wants age verification they have to do it themselves” they pretty much do in USA its called your social security number. Banks, auto dealerships, landlords etc use it all the time and its very effective.
By not taking a strong stance against what is happening here you are paving the road brick by brick to having to provide full on SSN and very plausibly retina scans or something similar in the not so distant future before you can even login to your computer or phone.
I don’t understand, how people here are missing that. Fuck we are on Lemmy because we see how shit worked with things like reddit and others. Things always escalate when control and greed are the primary motivators.
This will escalate. And when it does I want you to remember that people were rightfully making a HUGE FUCKING DEAL about when systemd started doing this because by then you will be able to see clearly how it led to whatever surveillance wet dream they are absolutely going to force on us. It will be clear, and this will be step 1 .
My line in the sand is when a distro/app starts enforcing entry of birth date data. Having a database field to store it, or even an optional prompt for it isn’t the point where I bin it.
This is the most sane take I’ve read in this entire debacle. Between arguing the semantics of attestation vs verification and whether we need five hundred forks and PRs, I’m glad to read this.
The biggest mistake the original PR did was not make it more clear it’s not directly because of the laws themselves, it’s to support higher level systems that may want to or need to comply. Systemd is no more complying with any present or future laws than a keyboard manufacturer is violating the law if the user uses it to type racially motivated hate speech.
That is a valid point. Of course it still would be rather anonymised, but it could always be a ‘frog in the pot’ type situation, where most drastic changes are introduced very slowly. My main concern at the end of the day is how much info will be required to be given to services and how much data will be actually stored. If it’s anonymised, then I don’t see much of a threat. If a service requires me to fully identify for an age check, that’s an entirely different thing, especially considering the last of Discord’s data leaks.
I agree with all that you’ve said. But why add it now? Why haven’t they added it a long time ago? Or if now they remembered, why not other extra optional fields that some people might want, like gender, sex, any other field? Oh, it would be too political? I see…
I mean, the introduction of the date of birth field is obviously done to make it easy for distros to comply with age verification by simply saving the birth date and nothing else.
As for the other fields: what use would it have to have such info at OS level? What application would use these fields and how? I mean, some fields, like the ‘location’ one, already are pretty useless, as, for example, the ‘location’ field doesn’t seem to bhave any firm consensus on how it should be formatted. Even the documentation lists both “Berlin, Germany” as well as “Basement, Room 3a” as valid values.
So I doubt not introducing such fields has any sort of political agenda to it, but just raises the question on why such fields would be useful to begin with.
I’m thinking the same. I understand the people saying it’s no big deal, it’s just an optional field. But the existing optional fields (GECOS) have been there since the beginning of time. The original Unix user database (/etc/passwd) was created in a different time. Things have changed in the last 50 years and we now know that a simple field in an OS level database is not really an appropriate place to store PII. I don’t know what the solution is, as these laws are coming and there will be some people that need to comply, but I don’t think the current change to systemd is the right approach.
On the plus side - this controversy has prompted me to look into other options for my home servers and I’m loving the minimalism and simplicity of Alpine. (This isn’t a knee jerk reaction - I’ve been frustrated by the bloated feel of mainstream distributions for a while - more the straw that may break the camel’s back)
Oh, definitely I’m not saying people should just jump the gun and replace their distro for one without systemd immediately. I certainly won’t, at least not without thinking about it for a while. But I also think that denying the controversy exists is not good. This is definitely controversial, for some people even a deal breaker and there are valid, real reasons why. For the rest, it’s good to look at what options there are, see that there really isn’t an appropriate alternative for systemd in some cases and realizing that a successful fork would be a good thing. Also, a long time criticism of the community has been that systemd does too much and it being against basic Unix philosophy. I always thought of it not being a big deal, given its modularity. But I now realize that it centralizes control and design decisions to a single org and that is certainly a weak point IMO. So a fork makes a lot of sense, but it is at this point a mammoth of the project, so it will be really hard to maintain.
I find that move extremely funny, since it’s purely made for sensationalism and nothing else. I mean, if you hate how systems implemented age verification, then why don’t you remove its identity verification too, i.e. also optional fields for stuff like your address an e-mail that most users don’t even fill out.
There is no mechanism verifying what birth date you type in - you can type whatever date you want and systems doesn’t care.
I’d say no matter where you stand with age verification, this is the best solution to handle the situation. After all, any and all age checks we have nowadays are a black box anyways. There is no real knowing how other systems are checking ages, and there is AFAIK no real government mandated rules on how it is verified. They could make you scan your ID’s front, back, nuclear composition and dietary preferences and give you a result that is almost, but not quite, entirely unlike a proper age verification procedure.
If the government wants to introduce age verification, they have to do it themselves - build an API that handles the age verification, similar to how the digital ID in Germany works, as an example. If they want proper age verification, they also have to take the blame themselves if things go wrong.
This. And forking is easy. Maintaining a big piece of software is not. This is why every popular repo has hundreds of forks, but non of them are active or in sync with upstream.
You know I remember when age verification was a thing on porn sites.
No big deal, I was like 12 and could easily say “yupp, I was born April 20th, 1969” and there was no problem.
Now, in several states that has escalated to you showing your ID.
Do you think this is the end game? Systemd made it clear with this move that any kind of US law passed will be able to be honored by their architecture. They didn’t take a stand that you would expect from pretty much the entire Linux community as a whole.
And see the funny part is where you talk about “if the government wants age verification they have to do it themselves” they pretty much do in USA its called your social security number. Banks, auto dealerships, landlords etc use it all the time and its very effective.
By not taking a strong stance against what is happening here you are paving the road brick by brick to having to provide full on SSN and very plausibly retina scans or something similar in the not so distant future before you can even login to your computer or phone.
I don’t understand, how people here are missing that. Fuck we are on Lemmy because we see how shit worked with things like reddit and others. Things always escalate when control and greed are the primary motivators.
This will escalate. And when it does I want you to remember that people were rightfully making a HUGE FUCKING DEAL about when systemd started doing this because by then you will be able to see clearly how it led to whatever surveillance wet dream they are absolutely going to force on us. It will be clear, and this will be step 1 .
Yup. All this crying about the field is a big nothing burger.
My line in the sand is when a distro/app starts enforcing entry of birth date data. Having a database field to store it, or even an optional prompt for it isn’t the point where I bin it.
This is the most sane take I’ve read in this entire debacle. Between arguing the semantics of attestation vs verification and whether we need five hundred forks and PRs, I’m glad to read this.
The biggest mistake the original PR did was not make it more clear it’s not directly because of the laws themselves, it’s to support higher level systems that may want to or need to comply. Systemd is no more complying with any present or future laws than a keyboard manufacturer is violating the law if the user uses it to type racially motivated hate speech.
Good distros will push default a dob of 1970-1-1, mark my fucking words.
That’s still forcing a DOB, which is the line I won’t cross.
When you make a new user using
adduserdo you leave your full name, number, and room number?Blank is blank, epoch is functionally the same as leaving it blank. Especially if it becomes industry standard.
I would but I’ve always been opposed to systemd anyway.
But for me it’s a slippery slope I don’t think we should even get on.
Yeah I hated systemd since before it was cool to hate systemd again.
I agree. But the start of the slope isn’t my exit point. My exit point is just before the slope gets too steep to get off.
That’s the thing about slippery slopes. You don’t really know where the point you slip is.
I’m curious about GNU Shepard but still haven’t gotten around to swapping. Does anyone have experiences to share?
That is a valid point. Of course it still would be rather anonymised, but it could always be a ‘frog in the pot’ type situation, where most drastic changes are introduced very slowly. My main concern at the end of the day is how much info will be required to be given to services and how much data will be actually stored. If it’s anonymised, then I don’t see much of a threat. If a service requires me to fully identify for an age check, that’s an entirely different thing, especially considering the last of Discord’s data leaks.
I agree with all that you’ve said. But why add it now? Why haven’t they added it a long time ago? Or if now they remembered, why not other extra optional fields that some people might want, like gender, sex, any other field? Oh, it would be too political? I see…
I mean, the introduction of the date of birth field is obviously done to make it easy for distros to comply with age verification by simply saving the birth date and nothing else.
As for the other fields: what use would it have to have such info at OS level? What application would use these fields and how? I mean, some fields, like the ‘location’ one, already are pretty useless, as, for example, the ‘location’ field doesn’t seem to bhave any firm consensus on how it should be formatted. Even the documentation lists both “Berlin, Germany” as well as “Basement, Room 3a” as valid values.
So I doubt not introducing such fields has any sort of political agenda to it, but just raises the question on why such fields would be useful to begin with.
I’m thinking the same. I understand the people saying it’s no big deal, it’s just an optional field. But the existing optional fields (GECOS) have been there since the beginning of time. The original Unix user database (/etc/passwd) was created in a different time. Things have changed in the last 50 years and we now know that a simple field in an OS level database is not really an appropriate place to store PII. I don’t know what the solution is, as these laws are coming and there will be some people that need to comply, but I don’t think the current change to systemd is the right approach.
On the plus side - this controversy has prompted me to look into other options for my home servers and I’m loving the minimalism and simplicity of Alpine. (This isn’t a knee jerk reaction - I’ve been frustrated by the bloated feel of mainstream distributions for a while - more the straw that may break the camel’s back)
Oh, definitely I’m not saying people should just jump the gun and replace their distro for one without systemd immediately. I certainly won’t, at least not without thinking about it for a while. But I also think that denying the controversy exists is not good. This is definitely controversial, for some people even a deal breaker and there are valid, real reasons why. For the rest, it’s good to look at what options there are, see that there really isn’t an appropriate alternative for systemd in some cases and realizing that a successful fork would be a good thing. Also, a long time criticism of the community has been that systemd does too much and it being against basic Unix philosophy. I always thought of it not being a big deal, given its modularity. But I now realize that it centralizes control and design decisions to a single org and that is certainly a weak point IMO. So a fork makes a lot of sense, but it is at this point a mammoth of the project, so it will be really hard to maintain.
you mean like adding it to a bunch of optional details already?