top 91 comments

sorted by: hot top controversial new old
[–] 28 points 7 months ago

complying with a relatively inconsequential law

This downplays the impact to privacy these laws can have but sure, personal harassment is bad.

  • source
  • [–] 97 points 7 months ago* (last edited 7 months ago) (54 children)

    I’m going to bullet my thoughts on this whole thing because I’m annoyed by the general response, and the implementation as well:

    • I don’t wish harm on the dev and I don’t dislike them. I don’t even know them
    • Death threats are ridiculous; that’s the working class attacking itself again
    • That said, I want to know what compelled this dev to preemptively implement this field not in 1 but in 2 separate PRs
    • Both the field and the law itself do not serve the user at all; it’s a bullshit vague law that is using children as cover—again (I’m old enough to know how this game works)
    • I’ve always viewed Linux as the rebel among all of the corporate slop we have to constantly dodge, so it is super gross when I see changes in Linux that were made to appease laws built and pushed by fascist tech companies and governments
    • Did the dev even open a line of discussion anywhere, or was the PR supposed to be used for that?
    • What’s his motivation? Money? Fame? I’ve been a programmer for 20 years and I’d never jump on a chance to add something that aligns with laws I think are unethical dog shit—especially in the Linux space where the whole goal is to not be Windows
    • I’m a bit frustrated with the casual “what’s the big deal?” mindset that a lot of people I’ve encountered have about this. Are we not living through the same timeline where the US has fallen under the control of a fascist regime that is being eagerly assisted by Meta, Apple, Microsoft and a ton of other massive corporations? How do people not see that this is the beginning of the wedge? And let’s say it peters out and nothing else happens. I’m not going to be ashamed of the fact that I was a squeaky wheel over it because I’ve seen how these things go. You follow the money and suddenly the bigger picture comes into focus. Why on earth a meager single little dev would implement this, unprompted, is just beyond my reasoning.

    This reminds me of when Guillermo Rauch from Vercel praised Trump multiple times. Bro, you’re not Tim Cook. You’re not Ellison, Zuck, or Musk. You’re not even on their level. You’re not going to get on their radar. I have PTSD from fellow tech folks being weirdly aligned with fascism and this whole dumb thing is giving me that vibe again. I don’t think this is that 1:1, but this is like the metal scene. You have to dodge the fascists that seem to weirdly permeate corners of the culture. People that refuse and get annoyed by right-wing labels, but still help right-wing grifters, are their own unique brand of pathetic.

  • source
  • hideshow 54 child comments
  • [–] -1 points 7 months ago (31 children)

    I'll be upset when a cloud-connected Linux component prevents the system from working unless the real name and birth date fields have been verified

    until then, this is just as inert as the real name field which has been there for decades, and far less useful for surveillance than the real name field which has been there for decades

  • source
  • parent
  • hideshow 31 child comments
  • [–] 19 points 7 months ago* (28 children)

    Except this field has been implemented explicitly for this age verification laws. If this was for some random birthday greeting when you open terminal, i think fewer people would be up in arms. context is everything.

    if this moron implements compliance with laws that record a birthday today, what is stopping him adding 3rd party verification of id tomorrow? So far his track record is corporate bootlicker. You cannot trust projects where this guy is a contributer to

  • source
  • parent
  • hideshow 28 child comments
  • [–] -3 points 7 months ago (4 children)

    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.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 5 points 7 months ago (2 children)

    No, let's wait till we're at the bottom of the slope. Then start objecting.

  • source
  • parent
  • hideshow 2 child comments
  • [–] -1 points 7 months ago (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] -1 points 7 months ago (8 children)

    it would be very interesting to see that attempt

    but Poettering has already said that functionality doesn't belong in systemd so I'm not sure where anyone would raise such a PR

    seems like an Ubuntu/RedHat level distribution design to pull in a brand new age-verification / mass-surveillance component, or maybe modify an existing telemetry component

    the birth date field only made it into systemd because it's user metadata that is consistent with what is already stored there, whereas surveillance does not

    for now, at least

    again, I'd be very interested to see what happens with follow-up PRs

  • source
  • parent
  • hideshow 8 child comments
  • [–] 4 points 7 months ago (7 children)

    Poettering closed the pr that was reverting this age field. What happens is adding more and more control in the future to conform to whatever idiotic laws someone might make. Should we then also implement a filter for what you type online to conform with Russian law about calling their war "SVO"? Its their law after all, so why not make the rest of the world conform? Its already years older then this age verification?

  • source
  • parent
  • hideshow 7 child comments
  • [–] 0 points 7 months ago (1 child)

    rejecting the revert is completely separate from accepting additional age-check / mass-surveillance PRs, you know this and you are being willfully ignorant

    I would be very upset and very surprised if hypothetical follow-up PRs were merged into systemd, and I'm betting they will be rejected

  • source
  • parent
  • hideshow 1 child comment
  • [–] 6 points 7 months ago

    How is it different? The ready acceptance of additional fields specifically for age verification is clearly proof enough that any further bullshit will be accepted just as quickly. PR description clearly outlines it is for the sole purpose of age verification...

  • source
  • parent
  • [–] -1 points 7 months ago (4 children)

    What happens is adding more and more control in the future to conform to whatever idiotic laws someone might make.

    Slippery slope

    Should we then also implement a filter

    Also?

    There is no filter here so the comparison isn't valid.

    If we're just playing hypotheticals, turn the situation around. What if some Russian state program was required to run on every machine and if it detected people not in compliance with the law it updated their location field to say 'jail'. Should we then remove the location field?

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 7 months ago (3 children)

    According to the guy doing birth date pr, we should pre-emptively comply, so yeah... how about enforcing bans on promotion of LGBT propaganda that has been law in Russia since 2013? https://en.wikipedia.org/wiki/LGBTQ_rights_in_Russia#National_laws

    The law subjects Russian citizens found guilty to fines of up to 5,000 roubles and public officials to fines of up to 50,000 roubles.[citation needed] Organisations or businesses will be fined up to 1 million rubles and be forced to cease operations for up to 90 days. Foreigners may be arrested and detained for up to 15 days then deported, as well as fined up to 100,000 rubles. Russian citizens who have used the Internet or media to promote "non-traditional relations" will be fined up to 100,000 rubles.

    Oh I know, lets introduce a field that stores an array of your nationalities, so any app developer can request your nationalities and adequately fine you for spreading illegal content online if you are Russian citizen. After all you can do that using a linux machine, so we gotta identify this now too. And the law also applies to foreigners. This law has been in place far longer than California or BR one. Who gets to pick and mix which laws apply and which don't? But wait its okay its just an optional array, you don't have to use it...

    Do you now see how insanely dumb this is? I am neither in Russia or USA, why should I have to put up with a censoring mechanism?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 7 months ago (2 children)

    Oh I know, lets introduce a field that stores an array of your nationalities, so any app developer can request your nationalities and adequately fine you for spreading illegal content online if you are Russian citizen.

    In this hypothetical situation, why are you choosing to install software that does this? This software could just as easily store the data in a flat text file in your .config directory, it doesn't need systemd in order to exist. Systemd choosing to not add those fields would not prevent the software from existing.

    In any hypothetical situation where you're forced to use some hypothetical privacy invading software, that software would still be able to do everything exactly the same even if it has to store your information outside of systemd.

    Not having a field in systemd doesn't mean that the data can't be stored, it just means that the data has to be stored in a text file instead.

    Systemd also has fields to store your realName and location. That same hypothetical situation applies to that data too. Your REAL NAME gives much more information about you than your birthDate and the location field is big enough to store your exact GPS coordinates. Like birthDate, these fields are not a problem (they've existed since the 60s) if you don't install software that uses them.

    If you don't want software that tracks your location, don't install software that tracks your location. If you don't want software that requires your real name, then don't install software that requires your real name.

    If you don't want software that requires your birthDate for age verification, then don't install software that requires your birthDate for age verification.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 7 months ago (1 child)

    In this hypothetical situation, why are you choosing to install software that does this?

    Its not a hypothetical situation, it is happening, although right now to mobile phones and tablets if we stick with Russia example. Il let you envision what direction this is going to. But hey its a law. There are linux tablets out there, should maybe they add this pre-installed app?

    https://brusselssignal.eu/2025/08/russia-orders-pre-installed-app-on-all-domestic-mobile-phones-and-tablets/

    By the way that law is there since 2025. Its pretty obvious that we should pre-emptively comply?

    If you don’t want software that tracks your location, don’t install software that tracks your location. If you don’t want software that requires your real name, then don’t install software that requires your real name.

    That is my plan when we know the position of other distributions, I will be moving to one that does not use systemd. My argument with this is that the reasons for this change are clearly to comply with local laws that don't affect majority of the system users. There is no need in this change to be global. It should not exist.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 0 points 7 months ago

    Its not a hypothetical situation, it is happening, although right now to mobile phones and tablets if we stick with Russia example. Il let you envision what direction this is going to. But hey its a law. There are linux tablets out there, should maybe they add this pre-installed app?

    You haven't shown how this would be prevented if systemd didn't store birthDate.

    You, and I, are no more affected by this field than we have been affected by the realName or location fields which have existed for decades. The field doesn't do anything unless you choose to run software that uses it.

    If you're going to swap init systems because of this change then you understand my point about choice. If you think this field is bad, you can choose to not install systemd. If you use systemd and think the field is bad you can choose to not install software that uses the field.

    I think the age verification laws are pointless and damaging, but systemd isn't the battleground to fight that battle and, most importantly, people who are engaged in a harassment campaign against this developer are completely in the wrong.

  • source
  • parent
  • [+] -13 points 7 months ago (13 children)

    Whats wrong with Age verification? its fine to verify age, the problem with the age verification laws is the issue of how age is being verified. In this case its fine because its local first and privacy respecting.

  • source
  • parent
  • hideshow 13 child comments
  • [–] 15 points 7 months ago (3 children)

    Age verification requires doxxing yourself in order to actually work, and if it doesn't require doxxing yourself then it won't work and it can be bypassed, so pointless capitulation granting ease into more authoritarian forms in the future. You don't see why any actually functional age verification is a problem while fascists are trying to control all the digital architecture?

  • source
  • parent
  • hideshow 3 child comments
  • [–] -5 points 7 months ago (2 children)

    No it doesnt. If I ask are you 18 and you reply no/yes that is verifying your age without doxing you. This field is for when the user is NOT admin on the machine. This field would be filled out by the parent when they're setting up their kids machine.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 8 points 7 months ago (8 children)

    Its not suitable for proving your age. Its adding a field which is a stepping stone to future gating and more control over something that isn't even applicable to most of the users of the system.

    Why not then add a live filter to ensure that you don't call Putler's war in Ukraine and call it "SVO" as you are supposed to? Its the law over there and many years older than this one. People already have gone to prison for not complying with it. But hey lets make that a part of linux too. Its law after all... Do you see how stupid it is to blindly comply to something that doesn't even apply to you?

  • source
  • parent
  • hideshow 8 child comments
  • [–] -3 points 7 months ago (7 children)

    How is it not suitable? If I setup my kids age and an app wants to use the portal to check if he is over 18 and it returns no. That suitable age verification and its privacy respecting. Which is what is being suggested.

  • source
  • parent
  • hideshow 7 child comments
  • [–] 7 points 7 months ago* (last edited 7 months ago) (6 children)

    There are already parental control packages exist in the Linux infrastructure which are not tied to low level modules such as systemd https://github.com/biglinux/big-parental-controls if you want, you can install it. Its fork is available in the Arch ecosystem for example that mentions it complies with the BR implementation (https://github.com/jersobh/arch-parental-controls)

    • This is entirely optional package that claims to be privacy orientated (I haven't tried it) that a system administrator can install if they wish.
    • My router, an Asus one has parental controls settings already
    • My ISP router, bog standard one has parental controls settings already
    • My ISP account has parental controls settings already at account level, if Ia m not technical enough, I can call them and ask them to set it up
    • My phone provider has parental controls

    Why do I need MORE parental controls shoved down my throat when I do not desire it nor wish for it? But this time in a core component of alot of linux distributions.

    Oh and before you tell me "but ExoticCherryPigeon, its an optional field", sure, but here is the example of the slippery slope curtsey of UK:

    Take a look at the history of this act https://en.wikipedia.org/wiki/Online_age_verification_in_the_United_Kingdom
    We are now at the point where I need to use a CC to tell some 3rd party that I want a wank.

    And what else is happening now? They are suing websites not based in UK! https://en.wikipedia.org/wiki/Online_Safety_Act_2023#Enforcement, but that's not all, although not at the law stage, there are some talks about also now restricting VPN's https://www.techradar.com/vpn/vpn-privacy-security/uk-government-says-it-may-age-restrict-or-limit-childrens-vpn-use-following-new-consultation.

    A lot of websites also not based in UK jurisdiction have simply self censored UK users before they get ISP level blocked.

    If this is not an example of a slippery slope, I don't know what is!

    TL;DR tools already exist, we do not need more tools that will be a privacy nightmare

  • source
  • parent
  • hideshow 6 child comments
  • [–] 3 points 7 months ago (4 children)

    Why do I need MORE parental controls shoved down my throat when I do not desire it nor wish for it? But this time in a core component of alot of linux distributions.

    You don't and you don't have any parental controls being shoved down your throat, you have a JSON field that you can choose to enter data in or not. It does not control anything, it is not validated by anything (outside of compliance with ISO 8601) and it is not required to be set to anything.

    Who controls what is installed on your system? If it is you, then you can save yourself from parental control software by not installing parental control software.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 7 months ago* (3 children)

    So when application developer such as Discord (an example) builds on top of these age controls and decides to not allow access to channels which are marked 13+?

    What do you expect will happen?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 7 months ago (2 children)

    I expect that they will store your birthDate in their own way and not use systemd as they are not a Linux native application.

    You get to choose if you install Discord and you get to choose if you are going to submit to their age verification.

    This is true if the birthDate field exists in systemd or not.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 7 months ago* (1 child)

    They DO have a linux native client though, and the whole idea of using systemd according to the PR author IS because application developers can then request this information from user profile

    https://github.com/systemd/systemd/pull/40954

    The xdg-desktop-portal project is adding an age verification portal
    (flatpak/xdg-desktop-portal#1922) that needs a data source for the user's age.
    userdb already stores personal metadata (emailAddress, realName, location)
    so birthDate is a natural fit.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 7 months ago

    Discord does not use Linux user metadata to store information about your Discord account. Because the application is cross platform, they store information about you in their own systems, not in systemd. Their age verification is implemented completely independent of systemd and doesn't rely on the birthDate field.

    It's also software that you can choose to not install.

  • source
  • parent
  • [–] -5 points 7 months ago* (10 children)

    What’s his motivation? Money? Fame?

    Why does anybody submit changes to any project? Probably a wide variety of reasons.

    I’ve been a programmer for 20 years and I’d never jump on a chance to add something that aligns with laws I think are unethical dog shit—especially in the Linux space where the whole goal is to not be Windows

    I hope that you can see that there are people who see this addition as being not a big deal: optional field, no verification, GECOS fields already storing 'realName', 'location', etc.

    It doesn't seem like a huge stretch to understand why a person would submit a simple update when they don't think it's of world changing significance.

    I’m a bit frustrated with the casual “what’s the big deal?” mindset that a lot of people I’ve encountered have about this.

    I'm one of those people so maybe I can help.

    Are we not living through the same timeline where the US has fallen under the control of a fascist regime that is being eagerly assisted by Meta, Apple, Microsoft and a ton of other massive corporations?

    Yes, we are. That's why I don't use their software or services. The major, and most important, reason why this isn't a big deal to me is that Apple, Meta and Microsoft don't choose the software that is part of my system. We're not in commercial software land, this is the FOSS world. Here, I get to choose what happens on my system because I am the one in completely control.

    If a project decides that I have to submit to age verification then I simply won't use their project, it's just that simple. But, that is not what is happening here. There is no verification of any sort, nor is the operation of systemd affected by this field in ANY way.

    I don't buy the slippery slope argument that's being presented around this topic which makes the change seem like the beginning of fascisim or the end of privacy or whatever other hyperbolic situations that people are breathlessly inventing to justify their outrage.

    We already have fields to store personal data and those fields are optional and rarely used. They exist because they are needed in some cases and in the cases where they are not needed they do not do anything. The birthDate field is exactly the same as the realName field in that sense. It only does something if you choose to install software that uses it.

    This field will NEVER affect you unless you choose to install software on your system that requires it.

    What's happening here is that people are treating this single JSON field as a stand-in for age verification. It is not. If someone wants to meaningfully fight age verification laws then they need to involve themselves in politics instead of social media brigading and harassment campaigns against developers.

    In my view, this 'situation' exists because it allows hoards of people to appear to be 'doing something' without actually doing anything. It's low effort activisim. People find it much easier to write self-righteous and hyperbolic comments and to get into internet fights than to do the hard work required to affect the politicians and laws that are passed.

    On top of this we have the signal boosting effect of trend following, clickbait-driven sites and content creators looking to boost ad revenue by playing up outrage and drama.

    I disagree with these laws, but this is not the hill where the battle is being fought. It is a pointless distraction and one that is being used to actively target a person for harm.

    Nothing is going to happen on your system unless you choose to let it happen. No software update by any project will ever change this.

    The only thing that will change it, and the thing that people should focus on, are the laws in the places where they live.

    🍓 2
  • source
  • parent
  • hideshow 10 child comments
  • [–] 13 points 7 months ago (9 children)

    This field will NEVER affect you unless you choose to install software on your system that requires it.

    If the field did not exist software could not be made to utilize it.

  • source
  • parent
  • hideshow 9 child comments
  • [–] 3 points 7 months ago* (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 7 months ago

    It would still exist. It would just use different methods. Such as the apps that need it asking for it themselves as they do now and you having to enter it into a prompt rather than querying some data store on your PC without your knowledge. Not that this IS actually age verification anyway so the entire discussion is moot.

  • source
  • parent
  • [–] 2 points 7 months ago (5 children)

    Who gets to decide what software should and should not be allowed to exist?

    If someone wanted to store a birthDate (and, evidence exists to say that they do) then the most logical place to store that user detail is with all of the other user details... in systemd.

    You can choose what you put on your system, that's the Free in FOSS. But, you cannot choose what other people put on their systems.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 4 points 7 months ago (4 children)

    Its not leaving a lot of choice if it's part of systemd and I'd wager far more people do not want this than were asking for it. There's no benefit to it except for the government and corporations that want your data.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 0 points 7 months ago (3 children)

    The field doesn't do anything by itself. There is zero harm inflicted on people using systemd. There are probably lots of features of systemd that you don't want or use and the entire negative effect that you suffer is a few megabytes less free storage space.

    The only way the field would be used is if a person decided to use a different piece of software that wants a birthdate. If they don't choose to install such a program then the field is no more a danger than the realName or location fields. They have scary sounding labels but do absolutely nothing unless the user chooses to use them.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 7 months ago (2 children)

    The only way the field would be used is if a person decided to use a different piece of software that wants a birthdate.

    It leave the door open for this to happen. A malicious software may not advertise that it is harvesting your demographic information. Now that this is in place it's one more thing we have to worry about when evaluating software. There is absolutely no reason to be storing PII in a centralized spot where anything and everything can request it. If I want an app to have any of that shit I'll enter it on a case by case basis.

    You can say "well don't put it in there" but what happens when big monopolistic corporations start requiring it to use some service of theirs that you don't have an alternative for? Now I have to maintain a separate PC for that shit? Fuck that.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 7 months ago (1 child)

    You can say "well don't put it in there" but what happens when big monopolistic corporations start requiring it to use some service of theirs that you don't have an alternative for? Now I have to maintain a separate PC for that shit? Fuck that.

    If you choose to use a service that requires age verification then that service will store your age verification information on your computer somewhere. If it is stored in systemd, malicious programs will be able to access it. If it is not stored in systemd, malicious programs will still be able to access it.

    If you choose to not use a service that requires age verification, then you will not store any age verification information on your computer to be stolen by malicious software. Even if systemd has a birthDate field you will not store any age verification information.

    The difference in these two scenarios is your choice to use age verification or not. The location where the data is stored doesn't change the scenario.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 7 months ago

    The difference is using a centralized point on the OS that is designed to hand that info out to anyone that requests it, vs each app prompting the user and storing that info in a profile that is hopefully encrypted if they are doing things right and NOT designed to hand it out to anything else.

  • source
  • parent
  • [+] [S] -20 points 7 months ago (10 children)
  • [–] 21 points 7 months ago

    It's one battlefront of many, and a fairly significant one. As we've become on online society, computer software has come to encode human rights to expression and privacy. Those rights are worth fighting for.

  • source
  • parent
  • [–] 13 points 7 months ago (4 children)

    What I’ve learned is that it’s basically impossible to convince people that the only real way to solve this is violent revolution.

  • source
  • parent
  • hideshow 4 child comments
  • [–] -2 points 7 months ago (3 children)

    Given your lack of history of violent revolution (I'm assuming), I'd guess it's because you look like a hypocrite for sitting behind a keyboard and telling others to do something you're not willing to do yourself.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 7 points 7 months ago (2 children)

    I’ve already spent years of my life in activism (the actual kind where you do work and try to build community, inevitably get added to watch lists, etc) trying to motivate others. I’ve helped with Food Not Bombs, etc. I’ve done a decent amount of “walk the walk” but I’ve also got a life to live. The US is deep into a propaganda hole that I’m afraid is gonna take a long time to climb out of and people have goldfish brains. I don’t really care how I come off to folks on the internet.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 7 months ago (1 child)

    People protesting (legally and peacefully) have been targeted based on social media accounts. This is closing the gap to allow similar fascist behavior on an even more personal level.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 0 points 7 months ago

    People protesting (legally and peacefully) have been targeted based on social media accounts.

    Yes, this is bad. People should not be targeted because of what they wrote.

    This is closing the gap to allow similar fascist behavior on an even more personal level.

    On a personal level.

    Yeah, that would be bad. Kind of like a targeted harassment campaign of a person because of what they wrote.

    It's one thing to be against age verification or software that does age verification or platforms that require age verification. That isn't what is happening here.

    That fight is political, this is an engineering problem.

    You could argue that this enables age verification, it doesn't. Age verification software can exist without this field, it could store your birthdate in .config/EvilAgeVerificationApp/userinfo.txt.

    The field is an optional entry, systemd doesn't require it or verify it. It is simply the most logical place, from an engineering perspective, to store the data.

  • source
  • parent
  • load more comments (-1 replies)
    [–] 52 points 7 months ago (7 children)

    Don't collaborate with fascists.

  • source
  • hideshow 7 child comments
  • [–] 11 points 7 months ago (5 children)

    systemd maintainers rolling over and complying in advance somehow isn't even that surprising.

  • source
  • parent
  • hideshow 5 child comments
  • [–] -4 points 7 months ago (4 children)

    I don't get the "complying in advance" argument here. What would be an appropriate date for something like this to be accepted?

  • source
  • parent
  • hideshow 4 child comments
  • [–] 8 points 7 months ago (1 child)

    Well, the law doesn't come into effect until Jan 1st 2027, so you could delay until then at the latest. Or you wait a bit longer to see what the enforcement looks like and make the companies/politicians at least sweat a bit from any potential fallout. With GDPR some companies took a long time of dragging their feet to become compliant (partially because initial enforcement was lenient to give them time).

  • source
  • parent
  • hideshow 1 child comment
  • [–] -5 points 7 months ago

    Right. I thin you are ignoring some complexity here. This developer added a field to store some optional data in systemd. That code needs to be tested, reviewed, debated, and eventually needs to be merged in. Those merges, at least with large projects, don't typically get added directly to main they get added to a release branch. That release branch then needs to be completed and merged where it will then be packaged. Then different distributions/installers need to add that field as a requirement to their code which typically goes through the same process. Then all those changes need to be packaged for release by the distros themselves.

    So I'll ask again. Assuming that distros do not want to risk being fined and financially ruined. What is a appropriate time before January 1st 2027 to open this pull request in systemd?

    This would also assume that we would like to propose a solution (for the data storage) early enough that distros do not all come up with their own implementations and leave PII strewn across the system.

  • source
  • parent
  • [–] 8 points 7 months ago* (1 child)

    Never. Let shit hit the fan if it has to. Fight back instead of swallowing the whole boot.

    Legitimately the way various porn sites addressed similar laws is the way to go. Verification required in this state? "Well we're no longer serving this state's traffic at all, and conveniently here's the contact info of the government officials to blame, enjoy!"

  • source
  • parent
  • hideshow 1 child comment
  • [–] -4 points 7 months ago

    Hi. Are you a maintainer of one of the distros that might be affected by this law? If you aren't then you have no standing to blindly tell them that they should not follow the law and risk fines that would ruin the funding for their project(s).

    Bringing up porn sites is a false equivalency. Many of these laws do not require verification of ID or face scans as some are incorrectly claiming. They require a birthdate be entered during installation. The laws surrounding porn sites required 3rd party age verification which many of these sites said would not only crater their traffic from these states but also introduce a privacy nightmare which would also work against their business interests.

  • source
  • parent
  • [+] -8 points 7 months ago

    I imagine it feels quite righteous to drop maxims like this. I too am reminded everyday how glad I am not to have to live in a fascist state.

    That said I think this sort of superficial dismissal is really unhelpful.

    I think the vast majority of Linux users will agree we don't want to have to work with these laws but the reality is that we do. Far better we focus our efforts on minimising harm and promoting alternative mechanisms (e.g. zero-knowledge proofs).

    Further I fear this righteousness actually serves to foster a toxic culture in the free software movement. And do you know what we call belligerent people who want to stifle dissent? Fascists!

  • source
  • parent
  • [–] 17 points 7 months ago

    I think the discussion we should be having instead is engineering ethics.

    I think Dylan's letter clearly showed he isn't really involved in "FOSS radical" circles and has the usual engineering mindset (that was described in the Sam Bent blogpost). Not that I personally blame him, engineering schools raise students for this, and the corporate structure further enforces it with the strict hierarchies where you do whatever management orders you to do. What's important is that there are many devs who clearly aren't tied into the ethics discussion part of engineering. There's even research on engineers' attitudes afaik, and its conclusion was that freshly graduated engineers' first response was to implement changes without thinking about the ethics part, and after further prompting and discussion, they could be convinced that this change was bad and they need to push back.

    I'll leave a two links here so when people iwsh to read, they know where to find good stuff.

  • source
  • [–] 84 points 7 months ago* (8 children)

    On a completely unrelated, off-topic note. Here is the same person talking about Google's new "advanced workflow" for "sideloading apps" on Android.

    The title of his blog post is "Google's New Android Sideloading Flow Is a Fair Trade"...Figures.

  • source
  • hideshow 8 child comments
  • [+] -21 points 7 months ago* (last edited 7 months ago) (7 children)

    You mention the title but not the content of the essay. Did you read it?

    Edit: At first glance, the article seemed actually well-meant. Didn't have the context of how bootlickery it was.

  • source
  • parent
  • hideshow 7 child comments
  • [–] 57 points 7 months ago (6 children)

    TL;DR is that he says his initial reaction was "frustration" but then he goes on to parrot everything Google said to justify this.

    For example,

    57% of adults worldwide experienced a scam in 2025

    It is to protect people from scammers. It isn't aimed at power users (Sounds very much like "It is to protect the children. This isn't aimed at power users").

    There is no mention of https://keepandroidopen.org/ and what it means for developers of free and open android applications.

    There is no mention of statements made by developers of applications like F-droid, Obtainium and Newpipe who have openly said that they do not agree with this step from Google.

    There is no mention of how this can potentially demotivate individual android app developers and drive them away from the platform entirely (here is an example of this).

    There is also no mention of how most of these malware, adware and nagware infested apps used by scammers are ironically on Google's own Play Store.

    Other that that, no. I'm sure I did not read the content of his essay carefully enough. More importantly, my opinion doesn't matter. I'm just a reactionary idiot. But I wonder what the developers of those free and open source applications on F-droid, applications that cannot be installed via the Play Store (but their scammy fake versions can be), will react to this being called a "fair trade".

  • source
  • parent
  • hideshow 6 child comments
  • [–] 17 points 7 months ago

    57% of adults worldwide experienced a scam in 2025

    Sure. I experienced a scam and I told them to "fuck off".

    That's not 57% fell for a scam, or 57% of android users got scammed by "side loaded" software. It's cherry picking a stat just justify a monopolistic practice.

  • source
  • parent
  • [+] -24 points 7 months ago (3 children)

    Typical it doesn't effect me so why are they doing it. You said your selff 57% is a huge number. And they hopefully can reduce that. People on here secerly underestimate the average person let alone the half of the people who are below average.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 52 points 7 months ago (6 children)

    actions done collectively by SystemD

    Nope. It only needs one maintainer to do the PR

    It'll discourage people from becoming open source developers

    You know what will discourage Them more? Id verification

    relatively inconsequential law

    Give me your Id. Seriously, go and give me your ID with nothing blurred.

  • source
  • hideshow 6 child comments
  • [+] [S] -42 points 7 months ago (6 children)
  • [–] 37 points 7 months ago (5 children)

    That's not what they asked

    I also want to see your passport and your original birth certificate

  • source
  • parent
  • hideshow 5 child comments
  • [+] [S] -25 points 7 months ago* (last edited 7 months ago) (4 children)
  • [–] 8 points 7 months ago (1 child)

    You are right that it was a loaded question, and you had a smart answer, but the implication of this "inconsequential" change represented by the current birthdate is of course more invasive identification later.

    Otherwise why would they bother, because as it is now it is useless or inconsequential.

  • source
  • parent
  • hideshow 1 child comment
  • load more comments (-1 replies)
  • load more comments (-1 replies)
  • load more comments (-1 replies)
    [–] 90 points 7 months ago (5 children)

    I don't think enough people realize that this is catastrophically bad. It'll discourage people from becoming open source developers, it'll discourage people from using Linux, and it'll discourage legislators from taking the Linux community seriously.

    Sure, but personally, I don't want a linux community that's driven by corporate needs and governments that have been paid off by them. I don't view it as a catastrophe, if that's the version of "the linux community" that we lose.

    None of that is to say that harassing devs is correct. It's not, and never is. Harassing anyone with death threats and dogpiling is not on. But if we take that out of the picture, negative pushback that drives away devs that would otherwise have helped implement universal age gating isn't something I'm terribly upset over, because I don't want the version of community they're taking us towards

  • source
  • hideshow 5 child comments
  • [–] 6 points 7 months ago (4 children)

    this version IS the community and they're not taking us anywhere where we weren't already going.

    linux is a much a product of our society as are other things like pop culture and capitalism. corporations of all sizes and reaches (ie red hat, ibm, google, facebook, etc.) have always steered the path and decided upon the development trends that linux has always taken and the only people who could have prevented or mitigated further centralized enshitification (aka the linux kernel developers group) bent over backwards to comply with the american government's overreach when they kicked out russian developers.

    age verification is just the next step into this overreach and it too is being driving from the same corporate/government source that forced us all to accepting things like systemd or libvirt/kvm (facebook for the former and red hat for the latter) to service their profit motives.

    like american politics, it's still possible to reverse the trend; but also like american politics; it requires a greater deal of collectivist action that westerners are unwilling to risk out of fear of losing their own tiny piece of the pie.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 7 points 7 months ago* (3 children)

    [the linux kernel developers group] bent over backwards to comply with the american government’s overreach when they kicked out russian developers.

    I though that was mostly due to Linus being a typical Russia-hating Finn, but I never investigated.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 7 months ago

    a typical Russia-hating Finn

    Russia seems to have that effect on their neighbours (until those neighbours get invaded, annexed, and the population dispersed, so the area can be called Russia. See Karelia and Ukraine for some recent and ongoing examples). So sure, could be that.

  • source
  • parent
  • [–] 3 points 7 months ago

    i also wouldn't put this past him given the reactionary tendencies he's demonstrated in the past; but i suspect that a threat of non-compliance == treason from the federal government probably had a bigger impact.

    and if you've ever had the displeasure of working for the federal government; you'll hear horror stories of how capricious and draconian the selective enforcement of treason can be.

  • source
  • parent
  • load more comments
    view more: next ›