I pulled Amutable's corporate filings from the German Handelsregister. Here's what the founding documents reveal about the people who put birthDate into systemd
Posted by Ok_Lingonberry3296@reddit | linux | View on Reddit | 91 comments
A note before diving in/Doxxing Concerns: everything here comes from public records. German commercial registry filings are public by law and free to access anonymously since August 2022 under the DiRUG reform. Employer affiliations come from the individuals' own GitHub profiles and public conference talks. Lobbying figures come from Senate LD-2 filings and OpenSecrets. FTC settlements and nonprofit 990s are government records. No private information, home addresses, personal accounts, or non-public data appear in this post. Every person named here is named in their professional capacity as a corporate officer, open source maintainer, or employee of a public company, in the context of decisions they made in those roles.
The systemd birthDate merge has been discussed extensively, but most of the conversation focuses on the technical and political dimensions. I went after the corporate paper trail instead.
Amutable GmbH is registered as HRB 278404 B at Amtsgericht Charlottenburg in Berlin. I pulled the full set from the Handelsregister: the current register printout, chronological history, the official shareholder list (Gesellschafterliste), and the structured XML data.
Here is what the documents show.
Ownership
Three shareholders. Equal split. No outside investors.
- Christopher Wilson Kühl, Berlin - 8,400 shares (33.33%), held directly as a natural person
- LPLLC Holding UG, Berlin (HRB 277482 B) - 8,400 shares (33.33%), Lennart Poettering's personal holding company
- CBLLC Holding UG, Berlin (HRB 277363 B) - 8,400 shares (33.33%), Christian Brauner's personal holding company
Total share capital is EUR 25,200 divided into 25,200 shares at EUR 1.00 each. Fully paid in cash at formation.
An earlier AI-generated analysis that circulated online claimed AXA Venture Partners, Bosch Ventures, Spark Capital, Unusual Ventures, and 42CAP had invested in Amutable. That claim was fabricated. Zero search results connect any of those firms to the company, and the Gesellschafterliste filed with the court lists only the three founders.
Formation timeline
The Gesellschaftsvertrag (Articles of Association) was signed on August 6, 2025. The notary, Dr. Hans-Michael Giesen in Berlin, certified the shareholder list on August 19. The company was registered on August 21 by Dr. Weiland at the Charlottenburg court.
All three founders were employed at Microsoft when they signed the founding documents.
Poettering and Brauner created their personal holding UGs in July 2025 - also while at Microsoft. Kühl's entity, Assembled Parts UG, was registered back in May 2023, but it does not appear in the Amutable shareholder list. Kühl holds his shares personally.
The US trademark was filed October 7, 2025. AB-1043 was signed into law six days later on October 13. The public announcement came January 28, 2026. The birthDate PR was merged March 18, 2026 - seven months after the company was incorporated.
Self-dealing provisions
All three founders are appointed as Geschäftsführer (managing directors). Each one can represent the company alone. Each one is exempt from Section 181 of the German Civil Code, which normally prohibits self-dealing. That means any founder can sign a contract between Amutable and their own personal entity without needing the other two to approve it at the representation level.
Internally, the Articles require 75% shareholder approval for related-party transactions (Section 6.5(g)). With three equal shareholders, that threshold requires all three to agree. But the self-dealing exemption operates at the external validity level - a director could execute a transaction that binds the company externally even without internal authorization. The other shareholders would have a damages claim under Section 43 GmbHG, but could not void the transaction.
The hidden shareholders' agreement
The Articles reference a separate shareholders' agreement (SHA) in three places. Sections 4.1 and 4.2 allow non-proportional profit and liquidation distributions "if and to the extent provided in any shareholders' agreement which might be in place." Section 6.4 says management authority is governed by the Articles and "the shareholders' agreements."
The SHA is not filed with the Handelsregister. It is not available through the Bundesanzeiger. It is a private contract between the three founders.
In a German startup context, the SHA typically contains vesting schedules, drag-along and tag-along rights, non-compete clauses, and IP assignment provisions. The IP assignment question matters here: if the founders assigned their systemd-related intellectual property to Amutable, that would represent a transfer of community-developed open source infrastructure to a private company.
The notary's disclaimer
The notary explicitly states in the founding deed that he did not draft the Articles. He received "negotiated drafts" shortly before notarization and "was not in a position to thoroughly analyse all potentially relevant aspects thereof, in particular, to explore in detail what the intentions of the parties to this deed are."
That kind of disclaimer is standard for complex formations but unusual for a simple three-way equal-split GmbH. It indicates the Articles and the referenced SHA contain provisions beyond typical boilerplate - consistent with a VC-ready startup structure even though no VC has invested.
The Kinvolk pipeline
Kühl co-founded Kinvolk GmbH in Berlin in 2015. Kinvolk built Flatcar Container Linux, an immutable OS with dm-verity for verified boot. Microsoft acquired Kinvolk in April 2021. The team joined Azure engineering.
Four years later, the same people left Microsoft and registered Amutable at the same Berlin court. Amutable builds "verifiable integrity for Linux workloads." The technology lineage runs straight from Kinvolk through Microsoft to Amutable. Microsoft's acquisition effectively incubated the team and expertise that now runs a company with a direct financial interest in systemd's identity infrastructure.
Same address, same director
Amutable GmbH and Assembled Parts UG are both registered at Bornholmer Straße 80 A, 10439 Berlin. Both list Christopher Wilson Kühl as managing director.
Assembled Parts organizes All Systems Go!, the annual systemd developer conference (successor to systemd.conf, rebranded in 2017). The systemd conference and the systemd startup share a building and a director. In 2019, the conference sponsors included Facebook (Meta) and Kinvolk. The speakers and attendees at that conference now populate Amutable's team.
Meta's personnel pipeline into systemd
Daan de Meyer worked at Meta. He was also a systemd maintainer and the person who presented ParticleOS at FOSDEM 2025. ParticleOS is an immutable Linux distribution built on systemd-homed, which inherits the full user record schema including birthDate.
De Meyer left Meta and joined Amutable. Meta had a direct employee contributing to the systemd project and to the reference distribution that Amutable now commercializes. Meta also spent $26.3M on lobbying that shifts age verification burden from social media platforms onto operating systems. Both competing model legislative frameworks that Meta funded - the DAAA (burden on OS providers, became AB-1043) and the ASAA (burden on app stores) - move responsibility away from Meta.
The Gates Foundation chain
The Gates Foundation funds Common Sense Media. Common Sense Media's political arm, Common Sense Kids Action, was a primary advocate for AB-1043 and KOSA. Assemblymember Buffy Wicks, who authored AB-1043, previously served as Campaign Director at Common Sense Kids Action starting in 2016. Bill Gates chairs the Gates Foundation board.
Microsoft did not publicly support AB-1043. Google and Meta did. But Windows already collects birth dates at account creation. Entra Verified ID already supports ageOver claims with selective disclosure. Xbox UK already deployed Yoti-powered age verification in July 2025. Microsoft faces near-zero compliance cost. Open source competitors face an existential implementation burden. The company that benefits the most from the law stayed silent while funding flowed through the foundation to the organization that employed the legislator who wrote it.
48 hours
The entire sequence took two days. A first-time systemd contributor submitted PR #40954 adding a birthDate field to the user record schema. A Microsoft employee merged it against 37 thumbs-down and 1 thumbs-up. The PR generated 945 comments before maintainers locked it. The community submitted a revert PR. Lennart Poettering - who had incorporated Amutable seven months earlier - closed the revert without merging and locked the discussion, restricting it to collaborators.
From submission to permanent merge with locked revert: 48 hours. No governance review. No conflict-of-interest disclosure. No community vote at any point.
The UAPI Group
The UAPI Group sets Linux userspace API standards. It was founded by three people: Lennart Poettering, Luca Boccassi, and Christian Brauner. The same individuals who controlled the birthDate merge also control the standards body that could formalize it.
I audited every UAPI Group summit (2022, 2023, 2024) and every FOSDEM devroom session (2023, 2025). Identity, age verification, user metadata, compliance, and birth dates were never discussed in any UAPI Group venue. The birthDate field was added entirely outside the standards process, through systemd's unilateral governance - with even less review than the UAPI Group's already minimal process would have provided.
The same small group sets the standards, implements them in systemd, and now profits from them commercially through Amutable.
What this means for the birthDate merge
Three decisions put the birthDate field into systemd. Each was made by someone with a direct financial interest in the outcome:
- Luca Boccassi merged the PR. He works at Microsoft. Microsoft spent $10.35M lobbying on KOSA and COPPA 2.0, already collects birth dates in Windows, and faces near-zero compliance cost from AB-1043 while open source competitors face an existential implementation burden.
- Lennart Poettering blocked the revert and locked the discussion. He founded Amutable seven months earlier. Amutable's stated mission is "cryptographically verifiable integrity for Linux workloads." Every new identity field in systemd strengthens the market case for commercial integrity tooling.
- systemd has no conflict-of-interest policy, no community veto mechanism, no steering committee, and no disclosure requirements. None of these interests were disclosed during the PR review or the revert discussion.
The Handelsregister documents are public records. They can be found at handelsregister.de using the reference HRB 278404 B, Amtsgericht Charlottenburg. The full investigation with primary source PDFs is linked below.
Sources
- Handelsregister: HRB 278404 B (Amutable GmbH), HRB 277482 B (LPLLC Holding UG), HRB 277363 B (CBLLC Holding UG)
- Full analysis and primary source PDFs: https://tboteproject.com/git/hekate/microsoft-systemd-findings-public
- systemd PR #40954: https://github.com/systemd/systemd/pull/40954
- systemd revert PR #41179: https://github.com/systemd/systemd/pull/41179
- OpenSecrets - Microsoft lobbying: https://www.opensecrets.org/orgs/microsoft-corp/lobbying?id=d000000115
- FTC Xbox settlement: https://www.ftc.gov/news-events/news/press-releases/2023/06/ftc-will-require-microsoft-pay-20-million-over-charges-it-illegally-collected-personal-information
- Gates Foundation grant to Common Sense Media: https://www.gatesfoundation.org/about/committed-grants/2021/05/inv031206
- Microsoft acquires Kinvolk: https://azure.microsoft.com/en-us/blog/microsoft-acquires-kinvolk-to-accelerate-containeroptimized-innovation/
- Ageless Linux lobbyist analysis: https://agelesslinux.org/lobbyists.html
hackerbots@reddit
Bro this is how we end up with death threats against Lennart. What the fuck are you doing
Ok_Lingonberry3296@reddit (OP)
Lennart Poettering has received death threats for years over technical decisions in systemd. That is wrong and I condemn it unequivocally.
Nothing in this post encourages or justifies harassment of any kind, however the existence of bad actors who send death threats cannot become a shield against accountability for undisclosed financial conflicts in open source governance.
Poettering is a corporate officer of a registered GmbH who blocked a community revert on a project he commercially benefits from. That is a matter of public record and public interest.
If the standard is that no one can examine the financial interests behind open source decisions because someone might react badly, then open source governance becomes unauditable. The answer to death threats is law enforcement, not silence about conflicts of interest.
robstoon@reddit
Please describe how anyone personally benefits financially from adding an optional fuel to a database.
Idrialite@reddit
Sure. It's not too complicated.
Meta, for one, is funding lobbying of these laws through several PACs. They benefit from the laws because they shift the burden of compliance onto others, saving them money, time, and legal troubles.
eraptic@reddit
Pretty disingenuous to say he blocked a community revert on a project he commercially benefits from.
It's his project. He started the community.
This is all nothing more than a continuation of undue hate and vitriol
lifeintel9@reddit
Wait they BLOCKED a revert for age bracket??
hackerbots@reddit
"Nothing about me laying down a detailed explanation of this person's behaviors, connections, and relationships right next to a gun will lead to any problems" Do you hear yourself right now? Of course not, you want retribution against someone you don't even know, psycho.
Ok_Lingonberry3296@reddit (OP)
The post contains corporate registry filings, lobbying disclosures, and GitHub commit history. If public records about professional conduct read as a threat to you, that says more about the governance failures documented in the post than anything I wrote.
robstoon@reddit
The fact that people put this much work investigating the fact that systemd had the audacity to add an optional birth date field into a database, rather than into whatever distributions might actually decide to make use of this to restrict user access, really illustrates the level of irrational derangement some people have about systemd..
Correctthecorrectors@reddit
they added that birthdate there so that xdg.portal can use systemd to implement age attestation. So saying “its just a birthdate” is a logical fallacy. You’re omitting information about how it will be forced upon people who dont live in the same jurisdiction as the laws that the os provider is supposedly trying to comply with. (which are themselves unconstitutional)
robstoon@reddit
So why are you complaining to systemd rather than those developers - or better, whoever might decide to enable features to make that attestation required? It's because systemd is a more popular target for trolls and conspiracy theorists.
Correctthecorrectors@reddit
because systemD is providing age attestation capabilities to all distrobutions that use it, which is the vast majority of them. If SystemD didn’t implement this, then the operating systems that use it wouldnt have this additional way of gathering that information. So yes, systemd is complicit.
robstoon@reddit
No, it's not. Once again. Optional field in a database.
Do you seriously believe nobody else could figure how to achieve this?
Portbragger2@reddit
are you able to grasp the basic meaning of sentences?
...so they obviously do provide age attestation capabilities.
SafeToRemoveCPU@reddit
ITS OPTIONAL.
YOU DONT NEED TO USE IT.
IF YOU LIVE IN CALIFORNIA OR BRAZIL, THEN MAYBE YOU WILL.
Holy fuck.
Idrialite@reddit
read
Portbragger2@reddit
i'm sorry how does the word optional have anything to do with answering "is providing .... capabilities" with the false statement of "no it's not".
the field can be optional. it can be pink with a blue striped background. it can be round it can be square. what does this have to do with the only point i was addressing...?
robstoon@reddit
Age attestation implies some way to validate the information. If I can not fill in the field or put in a bogus value it's not attesting anything.
BStream@reddit
robstoon@reddit
Neither do the Linux kernel or many other projects. And "Community veto" is a terrible idea.
MitsotakiShogun@reddit
I had/have 0 qualms about systemd, but I see zero (0) reason why this change was necessary in this place/db/repo. Can you explain why this optional field needs to be in that specific place/db/repo, or at least why that's the best place, instead of literally anywhere else?
65jeff@reddit
You're gaslighting.
robstoon@reddit
How so? By pointing out misdirected and most likely disingenuous complaints?
65jeff@reddit
Concerns about real conflicts of interest are not derangement. It's ironic that we have so called FOSS enthusiasts covering for decidedly non-FOSS actions and behaviours.
robstoon@reddit
What you call conflicts of interest, I call conspiracy theory level paranoia.
Again. systemd is not able to do anything specific with this information itself. If someone implements a policy that uses this to do something objectionable then complain to them.
The systemd developers closing down the discussion is not a conspiracy. It's them not being interested in listening to this sort of irrational screeching. They're well used to dealing with that unfortunately.
65jeff@reddit
Yes, don't engage with the concerns. Call it paranoia and irrational screeching. That will help.
robstoon@reddit
That is me engaging with the concerns. What else would you call doxxing people over adding an optional field to a database?
65jeff@reddit
There was no doxxing here.
prone-to-drift@reddit
The point of FOSS is freedom. As much as I hate it, systemd project has complete freedom to merge that code and you or me have complete freedom to take systemd code and remove that patch and compile it ourselves for our systems.
OR, more realistically, just not use that field if we want. OR just put 1/1/1970 as your birthday, who cares.
Ok_Lingonberry3296@reddit (OP)
This post has been automatically removed on other subreddits, and (seemingly) mass reported on this subreddit. You can find the summary and links to the repository files at https://tboteproject.com/systemdfindings
I only ask that you share the website and spread the word of people attempting to censor this kind of content. Thank you.
itssimpleman@reddit
i cant access the site, is it down?
Kuipyr@reddit
Absolute schizoposting. You do know Poettering created systemd right?
Ok_Lingonberry3296@reddit (OP)
Yes. That's the problem. The person who created systemd also founded a company that commercially benefits from expanding its identity infrastructure, and then used his authority over the project to block a community revert of exactly that kind of expansion. Creator status isn't a conflict-of-interest exemption. If anything it makes the governance gap worse, there's no mechanism to check decisions by someone with that much unilateral control when their financial incentives change.
Linus Torvalds benefits financially from Linux through the Linux Foundation, but built governance around himself with time. Poettering's financial interest was not disclosed during the PR review or revert discussion and systemd does not maintain a steering committee or no conflict of interest policty, community veto, or disclosure requirements. Poettering founded a company that benefits from the decision he made and did not disclose as much.
robstoon@reddit
Speculation without evidence.
Speculation.
What project has a "community veto"? Certainly not the Linux kernel, despite your implication.
SpookyWan@reddit
Did you read it?
aioeu@reddit
Do you realise that distributions that don't use systemd will also need to store birthdate metadata, if they want to be compliant with these regulations? Are the developers of all the other projects involved all part of the same cabal?
WaitingForG2@reddit
Look up who technically owns systemd and freedesktop.
Look up allegiance of posters that were against of this post and tried to derail/report it.
OP did not mention RedHat, unfortunately so. It's like a missing link of how it infiltrated every single major distro at same time, with no pushback at all.
robstoon@reddit
You guys that keep screeching about a Red Hat cabal doesn't make it true.
Oh my God, look at how the distros decided to pick up something at pretty much the same time! It's clearly a conspiracy! Couldn't possibly be because it's actually good!
Ok_Lingonberry3296@reddit (OP)
RedHat research will be published soon.
aioeu@reddit
Systemd is a community project; I don't even know if you could say it has a "owner". freedesktop.org is managed by the non-profit X.Org foundation.
Yes, Red Hat have a lot of developers involved in various projects. Why wouldn't they? They are an OS developer. They should be involved in the projects.
WaitingForG2@reddit
My favorite joke
SpecialPreference678@reddit
The argument is that the laws are an overreach and intrude on privacy. By not implementing it, the GNU/Linux community would essentially be calling their bluff: "okay, you want this? then enforce it and ban GNU/Linux".
Having no method of enforcement, the law would either be repealed or toothless.
By complying, the pressure will now be on other members of the community (systemd implemented it, why won't you?) that are easier to pick off than if the entire community had been united.
If OP's allegations are true, that Poettering and other Microsoft employees/alumni have a conflict of interest here, then that is especially concerning.
aioeu@reddit
My point is the developer community is united. All of these are projects are working together, because a solution cannot be implemented by a single project alone.
If the OP's allegations are true, then all of them are complicit. But I do not think they are true. If you look at the commentary on all of the projects' issue trackers you will see that nobody actually wants any of these changes to happen, but while the regulations are on the books it is unfortunately necessary.
SpecialPreference678@reddit
Is the developer community united?
I see:
I think it's overstating to say "the community is united".
I also don't buy the argument that because it's the law, it's a necessity that they capitulate. If passed a law that had the exact same phrasing but instead of age they required to track the user's religion, ethnicity, or a whole host of other things that you would say "Well it's the law, so users must report whether they are Jewish".
aioeu@reddit
I do think it is, yes.
All of the changes are being lined up in multiple projects. If System76's appeals don't help the situation, these changes will actually be deployed to these projects.
Correctthecorrectors@reddit
ok so the ones that don’t stay compliant will break the law against california. The Attorney General of California can suck a big fat cock, and i’ll rip out account services. Don’t give a fuck. That’s the brilliance of open source software; you can do whatever you want with it even if breaks some unconstitutional law in some authoritarian society.
karafili@reddit
wtf: Post is awaiting moderator approval.
dezmd@reddit
It was up for a few minutes before the astroturfers reported it enough, but, 9 hours later, it's still 'awaiting moderator approval'
dezmd@reddit
Get ready for astroturfers to show up and try to turn the discussion against you OP.
Ok_Lingonberry3296@reddit (OP)
The report was mass reported, unfortunately.
robstoon@reddit
Because it's based on rampant speculation with no actual evidence of anything, and is probably AI slop to boot.
BetterEquipment7084@reddit
Why if I may ask
Correctthecorrectors@reddit
because this sub-reddit has been infiltrated by bots that are used for mass-reporting purposes to get threads exposing the truth deleted. And the moderators of this sub are in on it.
WaitingForG2@reddit
It's not bots, it's hardcore RedHat defenders. It's exact same names, that start concern trolling, derailment and reporting the moment anything against the narrative gets posted.
Skaryus@reddit
Bro just said "g0vb0ts (aka g000Yb0ts) are very active in most popular subs" and, r3ddIt r3moved it
Skaryus@reddit
govbots (aka goybots) are very active in most popular subs
Business_Reindeer910@reddit
Do notaries do something different in europe? Why would notaries be drafting anything?
Ok_Lingonberry3296@reddit (OP)
German notaries are not like US notaries. In Germany a Notar is a state-appointed senior legal professional who passed the same exams as judges. They normally draft the formation documents themselves and advise both parties on legal consequences. That is why it matters that this particular notary explicitly disclaimed having drafted the Articles, possibly implicating he received pre-negotiated drafts from external lawyers.
For a straightforward equal-split company that is unusual and signals the founders brought in separate counsel to negotiate complex terms before the notarization.
On the birthDate field you're right that an optional self-reported field that nobody reads does nothing on its own. The issue is what it builds toward. AB-1043 takes effect January 2027 and requires operating systems to prompt for age at account setup and report age brackets to applications.
There's already a KDE xdg-desktop-portal PR (#1922) to expose age ranges to apps based on the stored value. The pipeline is birthDate in the user record, portal exposes an age bracket, applications gate content on the bracket. Each piece is optional in isolation. These together are the compliance stack the law requires.
As kedisdead put it, the deeper problem is that the people building this infrastructure have undisclosed financial interests in it existing, and systemd has no governance mechanism to control or monitor that.
Eu-is-socialist@reddit
LOL . maybe you can tell us what they do in the US ... since you know "they are not the same " :/
Business_Reindeer910@reddit
thanks for the information on the notaries
This doesn't seem that unusual to me if any of people involved are Americans. This is definitely what Americans would do.
Yes, and it's meant to be handled by portals or some other service.
They had very disclosed interest in existing too, but the undicosed stuff just makes it look worse.
I do think it's time for systemd to have a governance structure for sure.
kedisdead@reddit
I think more than the final implementation it's an issue on how fast it got merged and how much money changed hands for this to happen, i.e. systemd no longer seems truly free if it movrs to implement checks that financially benefits private interests
65jeff@reddit
Hilarious to see a bunch of FOSS people screaming and plugging their ears at the idea of transparency in decision making. Reporters and downvoters are basically saying "why no, I don't need to know what's happening and neither does anyone else."
Correctthecorrectors@reddit
yeah then they keep saying “its the law” like the politicians who passed this law didn’t break the law themselves to pass this blatantly unconstitutional law when they accepted money from meta lobbying groups in quid-pro-quo
azurewindowpane@reddit
Ah, we're doxing people - fun!
Ok_Lingonberry3296@reddit (OP)
A note before diving in/Doxxing Concerns: everything here comes from public records. German commercial registry filings are public by law and free to access anonymously since August 2022 under the DiRUG reform. Employer affiliations come from the individuals' own GitHub profiles and public conference talks. Lobbying figures come from Senate LD-2 filings and OpenSecrets. FTC settlements and nonprofit 990s are government records. No private information, home addresses, personal accounts, or non-public data appear in this post. Every person named here is named in their professional capacity as a corporate officer, open source maintainer, or employee of a public company, in the context of decisions they made in those roles.
The systemd birthDate merge has been discussed extensively, but most of the conversation focuses on the technical and political dimensions. I went after the corporate paper trail instead.
Amutable GmbH is registered as HRB 278404 B at Amtsgericht Charlottenburg in Berlin. I pulled the full set from the Handelsregister: the current register printout, chronological history, the official shareholder list (Gesellschafterliste), and the structured XML data.
azurewindowpane@reddit
Posting someone's address is not a necessary step in doxing - admit it or not, you are very deliberately identifying everyone with an ounce of culpability so that they can be harassed.
lopahcreon@reddit
Does doing stupid shit that violates open source standards for private personal gain not deserve harassment?
Note, I’m using the definition of harassment that doesn’t enter the realm of illegality.
jar36@reddit
cry about it as they're doing shadier shit than what you're accusing
Ok_Lingonberry3296@reddit (OP)
Their names are literally involved in the systemd Github.
shikkonin@reddit
Public records are public records. The persons in question decided themselves to dox themselves.
Laws are laws.
LongWillingness9396@reddit
Great investigative work. I am happy we are closer to the truth but I am afraid you may have opened Pandora's Box.
Nobody wants to admit it but this community is volatile, fragile, and will be infiltrated very quickly. I will continue to develop and contribute to the FOSS ethos. I am however removing myself from this community and the implosion that is about to happen.
Good Night everyone. May Torvalds help us lol.
Correctthecorrectors@reddit
don’t be such a drama queen, just disassciate with systemd. It’s not that big a deal; people have been saying that it’s been compromised for awhile ,this is just the wake up call.
robstoon@reddit
People as in brain dead conspiracy theorists?
Correctthecorrectors@reddit
hard to call them “brain-dead” conspiracy theorists when they’ve been proven right.
LongWillingness9396@reddit
I can smell the death threats already.
earthman34@reddit
Has Poettering ever been to Zuckerberg's compound? Inquiring minds want to know.
Correctthecorrectors@reddit
probably has also been to Epstein’s compound.
insanemal@reddit
It's about FORKing time to do some FORKING
AutoModerator@reddit
This submission has been removed due to receiving too many reports from users. The mods have been notified and will re-approve if this removal was inappropriate, or leave it removed.
This is most likely because:
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
blackcain@reddit
Drink some warm milk and go to sleep. Jeezus, Amutable is about attestation. The entire company has nothing to do with laws pushed by Facebook so that they can escape legal issues.
Focusing on Amutable and not Facebook is some bullshit. Plus, these OSes have to align with state law in California. There. Is. No. Choice. The people driving this is Meta. You're focusing on the wrong people.
Correctthecorrectors@reddit
“Ammutableis about attestation” then “OSes have to align with the state law in california [which is about attestation]” , a law that was supported by microsoft? It’s called critical thinking. And yes there is a choice; it’s called preliminary injunction. FIght this in court first, and then appeal. Do whatever it takes to stop it. Sitting here acting like you have your hands tied is not being honest
Ok_Lingonberry3296@reddit (OP)
This post dedicates entire sections to Meta's $26.3M lobbying spend, their funding of both competing model legislation frameworks (DAAA and ASAA), the Digital Childhood Alliance as a Meta-backed advocacy group for a reason; a Meta employee who maintained systemd before joining Amutable. We find that Meta may be a primary driver.
The reason Amutable matters is the governance question; Meta lobbied for the law. That's legal and already both documented and disclosed. What wasn't disclosed is that the people who implemented the resulting infrastructure in systemd had financial interests in doing so. Boccassi works for Microsoft. Poettering founded a company seven months before the merge that commercially benefits from richer identity fields in systemd. Neither said a word about it during the PR review.
You can't examine Meta's influence pipeline without examining where it terminates. It terminates in a 48-hour merge by people with undisclosed conflicts of interest in a project with no governance safeguards.
MelioraXI@reddit
But Lennart bad! /S
65jeff@reddit
In a hypothetical age verification solution, Amutable is in a position to profit by attesting that users have not tampered with the software and data involved in the process.
Mission_Shopping_847@reddit
tldr is actually typical microslop eee but with "think of the children" narrative weight and a smothering barrage of resulting fines.
WaitingForG2@reddit
https://www.reddit.com/r/linux/comments/1rgl4hy/comment/o7u0gmy/?context=3
Glad people started noticing it, it's not too late yet, but all signs were there for a while
This is exactly how every standardization group ends up. A puppet of biggest pockets
jar36@reddit
sadly it seems few in the Linux community give much shit about FOSS. Too many are rushing to defend the very folks who are giving the state the tool against us and are set to profit from it
they think it's just a little file on their computer. it's not and even if was that's not foss. you force me to put in any information and you've killed it. you're probably breaking the license that allows you to reproduce the software that you're using to collect my data. Yes the law requires them to collect the data. that's the word in the law
Correctthecorrectors@reddit
yeah fuck systemd, they’re done. Hope more distros detach; there’s no good reason to stick around and use it; there’s plenty of alternative initializers that are capable, less bloated, and faster let alone this infection with corporate cronyism.
Glittering_Mouse_883@reddit
More people need to see this.
65jeff@reddit
Nice work, thank you.
Latter-Particular440@reddit
holy shit this is some next level investigative work 💀
the fact that they incorporated amutable 7 months before the birthdate pr and then blocked the revert is absolutely wild. like you literally followed the money trail through german corporate filings and found the smoking gun
that 48 hour timeline from pr to locked revert with zero community input is peak corporate fuckery 🔥 and the conflict of interest stuff with the uapi group is just chef's kiss levels of corruption