Lunduke
News • Science & Tech
Leaked Microsoft documents reveal effort to "Gender Transition" young children
Including toddlers as young as 3 years old
April 14, 2024
post photo preview

The Lunduke Journal has received leaks from a confidential whistleblower, within Microsoft, that show a concerted effort to "Gender Transition" children as young as 3 years old.

Including: Guides for Microsoft employees of trans children, corporate support groups to encourage transitioning children, and mandatory health insurance add-ons which cover "Transgender Treatment and Services" for family members (including children).

This comes from a 2019 report -- comissioned by Micrtosoft -- entitled "Gender Identity and the Dynamic Workforce: Creating an Inclusive Workplace".

The title page of the 96 page report.

The report was written by "WFD Consulting" and paid for by Microsoft specifically for Microsoft's internal use.

According to WFD Consulting:

"Microsoft sponsored this study to better understand and address the needs of employees who identify as transgender and gender nonbinary. They commissioned WFD Consulting to examine the experiences of workers in a variety of industries and provide actionable recommendations that would be useful to all types of organizations."

Sponsored by Microsoft.

This report was not released freely to the public, but was made available to Microsoft employees and management.

While there are several concerning sections of this 96 page report, let's jump to Chapter 6 -- which specifically deals with providing "gender-affirming care" to children... and encouraging Microsoft employees to pursue that avenue with their children.

Chapter 6: Employee Parents of Transgender Children

This section -- focused entirely on "transitioning" children -- is roughly 15 pages long and consists of a combination of quotes from employees along with recommendations.

Including this story of a 3 year old girl who's parents "transitioned" her into a "boy".

3.  Years.  Old.

The report includes stories about children ranging from 3 years old up to the teen years.  The fact that toddlers were included in this is absolutely horrifying.  According to The Lunduke Journal's source, "this report was trumpeted and celebrated by many" within Microsoft.

As the report goes on, it gets into specific recommendations and advice for Microsoft employees on how to assist their children in "transitioning" their gender.

A "sense of urgency" was also applied -- Microsoft employees were warned that they must make decisions about "gender affirming care" quickly... as there is a "ticking clock for puberty blockers".

Act now!  Hurry!

The report also included several recommedations for Microsoft's management: including the establisment of groups and official corporate communication channels for parents of "transgender and nonbinary children".

Official company resources.

It was also recommended that groups for "young transgender kids", under 13 years old, be created.

Facebook.  Under 13 years old.  Talking about genitals.  So many red flags here.

One of the other recommendations -- which Microsoft acted upon -- was to "Remove age restrictions for gender-affirming treatments for children under 18".

Microsoft implemented a company wide, mandatory, supplemental health insurance plan which covered "gender affirming care" for small children (and other family members).

This is known as the "Health Plus Plan".

Additional and non-optional.

According to one source within Microsoft, this report was "used to justify the addition of a new supplemental health insurance plan" which employees "were not given the option to opt out of".

What, specifically, did this non-optional plan cover?

Things like hormone therapy, puberty blockers, and various "sex change" surgeries and medications.  Many of which were made available to small children.

The list of sex change related services provided to Microsoft employees.

What did we learn from the above leaked information?

  1. Microsoft paid for reports which encouraged employees to "transition" their children.
  2. The idea of children, as young as 3 years old, being "transitioned" was presented as a good thing.
  3. Support groups, using company resources, were (according to the report) to be created for "Transitioning" children.
  4. Microsoft added a non-optional health plan which specifically covers "gender affirming care" for small children.

And this is just the tip of the iceberg.

Thanks to brave whistleblowers, The Lunduke Journal has a small mountain of leaked information -- from within Microsoft -- to process, verify, and publish.  Stay tuned.


If you work for Microsoft (or another Tech firm), and have inside information that you feel should be shared with the public, here are instructions on how to anonymously become a whistleblower. The Lunduke Journal will always keep your identity confidential.

Thank you to the whistleblowers who have come forward so far -- and thank you to the supporters of The Lunduke Journal for making this work possible.

Interested in other recent Big Tech leaks?  Check out The Lunduke Journal's mountain of leaks from within Red Hat and IBM.

community logo
Join the Lunduke Community
To read more articles like this, sign up and join my community today
0
What else you may like…
Videos
Podcasts
Posts
Articles
PSX Emu Dev Forbids Arch Linux Packages

DuckStation developer says, "Next step will be removing Linux support entirely, because I'm sick of the headaches and hacks." Specifically naming Wayland as a source of problems.

00:15:52
Groupthink, Tech Journalism, & The Lunduke Journal

Why The Lunduke Journal uses the "10th Man Rule" to counter groupthink in the Tech Industry. (And why you'll definitely disagree with Lunduke sometimes.)

Stick it to Big Tech, 50% off everything at The Lunduke Journal:
https://lunduke.substack.com/p/stick-it-to-big-tech-50-off-everything

00:18:10
The Age of Non-Woke Open Source is Beginning

Non-Woke "Political Protest Forks" like XLibre & Redot are thriving. Non-DEl Linux Distributions like Open Mandriva are as well. But Woke projects? Not doing so well.

The Article:
https://lunduke.substack.com/p/open-source-political-protest-forks

00:21:04
November 22, 2023
The futility of Ad-Blockers

Ads are filling the entirety of the Web -- websites, podcasts, YouTube videos, etc. -- at an increasing rate. Prices for those ad placements are plummeting. Consumers are desperate to use ad-blockers to make the web palatable. Google (and others) are desperate to break and block ad-blockers. All of which results in... more ads and lower pay for creators.

It's a fascinatingly annoying cycle. And there's only one viable way out of it.

Looking for the Podcast RSS feed or other links? Check here:
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

The futility of Ad-Blockers
November 21, 2023
openSUSE says "No Lunduke allowed!"

Those in power with openSUSE make it clear they will not allow me anywhere near anything related to the openSUSE project. Ever. For any reason.

Well, that settles that, then! Guess I won't be contributing to openSUSE! 🤣

Looking for the Podcast RSS feed or other links?
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

openSUSE says "No Lunduke allowed!"
September 13, 2023
"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

This episode is free for all to enjoy and share.

Be sure to subscribe here at Lunduke.Locals.com to get all shows & articles (including interviews with other amazing nerds).

"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

There's a new conference in town. And it seems it's already sold out!
#VibeCoding

For all you Commodore fans…

If you've done 6 impossible things this week, why not round it off with a trip onboard "thE grAvY trAIn" TONIGHT at 21:00 BST! (1pm PST/4pm EST)

https://erb.pw/y/tgt20250802

post photo preview
IBM Taking DEI “Under the Radar”
Whistleblowers provide details on how IBM & Red Hat are simply renaming “Diversity” programs, as the company continues discriminatory hiring practices.

Back in April, The Lunduke Journal broke the story of IBM “ditching DEI policies” company wide — including at their subsidiary, Red Hat. This change was announced in the wake of multiple lawsuits against IBM (for their DEI policies) and executive orders against DEI from President Trump.

At the time, activist employees at Red Hat / IBM were not happy (to say the least). Encouraging and planning protests, “raising hell”, and even “killing fascists”.

But, now that a little time has passed, let’s take a look inside at IBM and see how their “ditching DEI” change is actually going.

DEI Staying “Under the Radar”

Thanks to whistleblowers within IBM, we know that employee groups focused on DEI still, in fact, exist. They are simply changing names in order to “stay under the radar” and avoid having “a target on their back”.

 

The “diversity-inclusion” corporate Slack channel, for example, is now named “inclusion-at-ibm”. They simply dropped the word “diversity”.

The DEI Department is Still There

Employees are using that IBM DEI Slack channel to clarify corporate changes to DEI policy. Which, again, thanks to whistleblowers… we have screenshots of.

A few key items:

  • The “DEI Department” has been renamed to “Inclusion” — and now reports to Kitty Chaney Reed (the Chief Leadership, Culture and Inclusion Officer).

  • IBM is no longer part of the Human Rights Campaign — “the HRC no longer align with IBM priorities”.

  • “People can still identify their preferred pronouns in all of IBM systems.”

  • The game-ified “Allyship Badge” system has been removed.

 

As we can see, some DEI policies and programs are gone, while others remain. And IBM is making a point of renaming their DEI Department within HR.

We gain these insights thanks to Ruth Davis — an IBM Executive and who currently identifies as a “DEI Advocate”.

 

These clarifications were published by a current member of the IBM HR team… who was originally hired as a “Diversity and Inclusion Intern”.

 

In short: DEI advocates continue to control IBM HR, and DEI departments continue to exist.

IBM / Red Hat Discriminatory Quotas

Up until recently, both IBM & Red Hat had discriminatory hiring policies — including sex and skin color quotas and even rewards for executives for hiring fewer white men.

We learned, as part of the original leaks supplied to The Lunduke Journal back in April, that “diversity goals are no longer part of the executive incentive program”.

 

Which begs the question, now that a few months have passed, is IBM still discriminating against White Men?

Getting hard numbers on the demographics of new IBM / Red Hat employees is not likely to happen for quite some time — if ever. But here is a picture, posted yesterday, of new Red Hat interns.

That might give us some indication of where things are heading.

 

Well. Huh.

Finding the “White Guys” in this photo of Red Hat interns isn’t quite as challenging as a round of “Where’s Waldo?”… but it’s close.

Now for me, personally, I truly don’t care what the demographic ratios are of employees & interns within a company. Hire the best people for the job, regardless of their sex or ethnicity. Meritocracy is a good thing.

That said, considering the multiple pending lawsuits against IBM and Red Hat — specifically regarding their discriminatory policies towards White Men (and their previously stated goals of hiring less of them) — it is more than a little interesting that their latest crop of Red Hat interns is almost entirely… people who are not White Men.

Results Are Mixed

There are a few good signs in here of IBM dropping DEI related policies — including no longer being involved in the Human Right Campaign and the removal of the (rather repulsive, anti-White) “Allyship Badges”.

Unfortunately, most of the rest of what we’re seeing is less encouraging.

  • “DEI” groups simply being renamed to “Inclusion” in order to stay on the right side of the law.

  • What appears to be continued discriminatory hiring at Red Hat (despite lawsuits and stated policy changes).

  • Executives and HR still heavily controlled by “DEI Advocates”.

  • Corporate systems still using “preferred pronouns”.

While making significant changes to corporate policies can take time — especially across large organizations like IBM — some of these internal reports indicate an unwillingness to drop DEI policies on the part of key IBM leadership.

The Lunduke Journal will continue keeping tabs on both IBM and Red Hat.

Any employees looking to become whistleblowers can find whistleblower resources at Lunduke.com.

Read full Article
post photo preview
LibreOffice Developer’s Hotmail Account Locked After LibreOffice Criticizes Microsoft
“Wow that looks bad,” says Microsoft employee.

Mike Kaginski, a LibreOffice developer (who works for Collabora), has had his Microsoft-hosted email account, which he uses for open source development, locked for “activity that violates our Microsoft Services Agreement”.

 

Kaginski discovered this when attempting to send an email to the LibreOffice development mailing list (hosted by FreeDesktop). It remains unclear if that specific email (which he sent via another address and was rather bland and technical) was the reason for the ban… or if attempting to send the email was simply the first time the ban was noticed by him.

This happened just days after LibreOffice officially accused Microsoft of engaging in a “Lock-in” strategy by creating “artificially complex”, XML-based office documents.

Are the two events related? Hard to say with any certainty.

To make matters worse, Kaginski has had no success in getting Microsoft to lift his locked email account — with the company making him jump through numerous, impossible hoops (such as requiring him to sign in to submit an appeal for his account being locked… but not allowing him to sign in… because his account is locked).

You got that? Sign in to fix the account you can’t sign in with.

Gotta love a good Catch-22.

Good job, Microsoft.

The Lunduke Journal reached out to a contact, within Microsoft, who made it clear that their group was not aware of the LibreOffice Developer’s locked account, but they were aware of the LibreOffice complaint article regarding “artificially complex” XML lock-in. Adding, “wow that looks bad”.

The Lunduke Journal’s Analysis

The odds of locking a LibreOffice developer’s email account being an official Microsoft corporate decision seems highly unlikely.

Microsoft, as a company, makes a lot of bad decisions — but this would just be too stupid for words. A massive PR blunder.

But could a single employee, feeling grumpy, have done it on an impulse? As some sort of revenge for LibreOffice’s “harsh” words about Microsoft? Sure. That seems entirely plausible?

Though, it’s also entirely plausible that some poorly designed AI-driven “naughty activity” detection bot flagged his account. Or, perhaps, the developer was reported by some random Open Source hooligan who likes to cause chaos (there’s a lot of those).

Either way, the fact that Microsoft requires people to log in — on accounts which cannot log in — in order to file an “appeal” is incredibly amusing. And is very, very typical Microsoft.

Read full Article
post photo preview
Open Source “Political Protest Forks” Thriving
Many called XLibre & Redot nothing more than “political protests” that would quickly die and be forgotten. Boy were those naysayers wrong.

Over the last year, we’ve seen a couple of high profile forks, of large Open Source projects, which were inspired — in part — by a desire to move away from the political discrimination and Leftist Extremism within the original projects.

At the time, when each of these forked projects were started, many predicted that they would go nowhere. That they were nothing more than “political protest forks” — and they would die out quickly.

Let’s check in on both of those project to see if that has happened.

XLibre - The Xorg Fork

Since officially launching, at the end of June (last month), the XLibre project has published a handful of official releases (now up to version 25.0.0.5)… with a significant number of changes and fixes.

 

In fact, considering the significant new features (such as XNamespace Extensions), the first release of XLibre is larger (in every way I can think to measure) than any Xorg release in the last decade. With the number of contributors growing.

How about Operating System support? Many predicted that XLibre would be ignored by every Linux distribution on the planet. That it would go nowhere and nobody would use it.

According to the “Are we XLibre yet?” wiki, a number of systems have already (officially) adopted XLibre. Including: Devuan, Artix, GhostBSD, and (my personal favorite) OpenMandriva.

 

This is important to note: All of that support has occurred even though XLibre has only existed for one month. Several systems already officially supporting it is nothing short of “crazy impressive”. Borderline unprecedented.

In addition, a number of systems have 3rd party repositories which allow users to install and use XLibre. Including: Arch, FreeBSD, Gentoo, NixOS, Slackware, and (seriously) macOS.

 

In short: Growing group of developers. Rapidly growing platform support. New releases which put the original project (Xorg) to shame.

Redot - The Godot Game Engine Fork

The Redot project — which forked off of Godot back in October of 2024 — had a stable release (4.3.1) back in June, and just had a new test release (4.4 Alpha 2). Both with both new features and fixes.

 

In fact, Redot has had 13 releases since the project started late last year.

With an absolutely massive number of commits since then.

 

In short: Steady, new releases. New features and bug fixes. Both stable and testing releases.

These Projects are Thriving

It’s hard to look at either of these projects and come to any conclusion other than they are absolutely thriving.

At this point, it’s looking like those who predicted rapid failure for these “Political Forks” were not only wrong… but wildly, obscenely wrong.

There’s a lesson in there.

Read full Article
See More
Available on mobile and TV devices
google store google store app store app store
google store google store app tv store app tv store amazon store amazon store roku store roku store
Powered by Locals