Bonum Certa Men Certa

Comes Antitrust: Microsoft's Attack Plan on GNU/Linux and Today's Lessons

Summary: Beyond the Halloween Documents (Comes vs Microsoft exhibits)

TODAY's Comes vs Microsoft post is a particularly long one, so we attempted to shorten it so as to keep the signal high and leave the details aside for separate inspection by those who are curious and have more time to spare.

“The authenticity of them was confirmed when the Comes vs Microsoft case produced exhibits for the broad public to access.”Many regulars are probably aware of the Halloween Documents. Eric Raymond (ESR) has a complete mirror of the text with commentary, so we will not replicate the documents, which have already been out there for years. The authenticity of them was confirmed when the Comes vs Microsoft case produced exhibits for the broad public to access.

Interestingly enough, Bill Gates said about these reports (Halloween documents): “The two documents in here from Vinod are the ones I want the board to see.” He was referring to Halloween Documents I and II. Here is Halloween Document I as text and as PDF. Here is Halloween Document II as text and as PDF.

Background



The documents which Gates referred to are already in ESR's Web site (as plain text), so there is no point repeating the process of posting them publicly. However, to highlight some particular bits from them, here are some portions from the above. Microsoft explains that:

OSS is a concern to Microsoft for several reasons:

1. OSS projects have achieved “commercial quality” 2. OSS projects have become large-scale & complex 3. OSS has a unique development process with unique strengths/weakness


Microsoft later adds that "to understand how to compete against OSS, we must target a process rather than a company."

Then come the issues of APIs, e.g.:

Linux and other OSS advocates are making a progressively more credible argument that OSS software is at least as robust – if not more – than commercial alternatives. [...] [E]vangelization of API’s in a closed source model basically defaults to trust, OSS API evangelization lets the developer make up his own mind.


The strategy in general:

Beating Linux In addition to the attacking the general weakness of OSS projects (e.g. Integrative / Architectual costs), some specific attacks on Linux are:

* Beat UNIX * All the standard product issues for NT vs. Sun apply to Linux * Fold extended functionality into commodity protocols / services and create new protocols * Linux’s homebase is currently commodity network and server infrastructure. By folding extended functionality (e.g. Storage+ in file systems, DAV/POD for networking) into today’s commodity services, we raise the bar & change the rules of the game.


That was about 10 years ago. As we noted before, Bill Gates once wrote: "What we are trying to do is use our server control to do new protocols and lock out Sun and Oracle specifically.”

How can Microsoft capture some of the rabid developer mindshare being focused on OSS products?

Some initial ideas include:

* Provide more extensibility – The Linux “enthusiast developer” loves writing to / understanding undocumented API’s and internals. Documenting / publishing some internal API’s as “unsupported” may be a means of generating external innovations that leverage our system investments.


It says "Documenting / publishing some internal API’s as “unsupported”..."

Does that sound familiar? As we shall show later, Microsoft also speaks frankly about "undocumentation".

Here is embrace & extend in action:

OSS projects have been able to gain a foothold in many server applications because of the wide utility of highly commoditized, simple protocols. By extending these protocols and developing new protocols, we can deny OSS projects entry into the market.


From Halloween Document II we pull the following (thanks to Jason):

The Linux community is very willing to copy features from other OS’s if it will serve their needs. Consequently, there is the very real long term threat that as MS expends the development dollars to create a bevy of new features in NT, Linux will simply cherry pick the best features and incorporate them into their codebase. The effect of patents and copyright in combatting Linux remains to be investigated.


Later came the SCO lawsuit, the Novell deal, and patent racketeering which carries on to this date.

New Material



Today's main exhibit ties the above documents together and we believe that there is no copy of it anywhere else (as text), so Wallclimber kindly contributed her time to process the text, which we then analysed. Wallclimber says that this "strategy" document outlines exactly what they've done to Novell. "I especially got a kick out of the "fatal flaws"," she added. Here is the original exhibit (PX08175, 1999) [PDF] and several points of interest that are extracted from the full text, which can be found at the bottom.

This short document is titled "Our Linux Strategy" and it was authored by Vinod Valloppillil.

Watch number 1 and number 2 in the list, then think about the loadable module [1, 2, 3, 4, 5, 6, 7], which added Microsoft hooks to Linux (hypercalls).

1. Embrace Linux: MS APIs / Linux kernel -- release an MS version of Linux and/or release key MSFT platform technologies on Linux (e.g. parts of Win32, app server, etc.)

Pros: Ride the wave & try to evangelize Win32 Cons: Dramatically evangelizes Linux & may risk MSFT IP due to GPL license issues Fatal Flaw: - Impossible to make this revenue neutral with Windows biz. - Doesn’t protect the "crown jewel" IP from being targeted at a later date

2. Embrace Linux: Linux APIs / MS Kernel -- try to get Linux API’s on Windows -- get more hardcore about POSIX subsystem on NT to capture Linux app base

Pros: Capture some of the Linux dev mindshare by making it easy to bring Linux apps to NT Cons: Hurts Win32 evangelization Fatal Flaw: - There are no Linux apps that we covet.


Also think about Mono, Moonlight, and OOXML.

Prior to that, Valloppillil states:

This document discusses both our strategy and our plans for competing with Linux. To understand the strategy it is important to remember the following: - Linux isn’t most importantly a product/feature; it’s a philosophy change - Linux has no new specific features to co-opt - Unlike the NC: the NC touted TCO benefits, and thus we introduced ZAK/ZAW - Unlike the Internet: the Internet was loaded with technology changes, and thus we invested in browser technologies and reexamined all our existing products

The core strategic thrust of Linux is NOT an attack against some product/feature weakness of Microsoft. It’s an attack at the base of the commercial software industry - Intellectual Property.

Previous threats to Microsoft (the NC, Java, etc.) have been about replacing Microsoft’s IP with another company’s IP that claimed some new benefit (e.g. TCO). What differentiates Linux is that OSS attempts to extricate Intellectual Property all together.


Learn from what Microsoft did to NetPC (NC) and to Java. Watch what else Microsoft put forth as an option:

Cons: ISVs getting hooked on undocumented API’s, support costs, etc.


So, "undocumented API’s" are an option, eh? Microsoft admits their existence.

Watch what Microsoft thought about Wine back when it was a lot less mature and capable:

- Microsoft is an IP company. Like the rest of the software industry, >90% of our IP valuation stems from Trade Secrecy of the source code. Open Source is mutually exclusive with Trade Secrecy. This plan would instantly make the various Win32 clones (e.g. http//www winehq.com) an order of magnitude more capable.


More compelling stuff from Microsoft:

2. Innovating, Creating New IP

(Re-)recognize that we are an IP company and that in our networked world, functionality delivered via protocols is steadily replacing functionality which was once delivered via APIs Thus, innovation must occur both internal to our products, but also between computers.

Windows clients must always be able to communicate with Linux servers (and vice-versa). However, there MUST be additional value created when a Windows machine is touching another Windows machine. NOT doing this is akin to giving away the Win32 APIs. Every group defining protocols needs to remember this.


Also:

We must innovate and keep our great advancements to ourselves. The fine balance between protecting/financing our innovations and interoperability will get more difficult overtime But, it is relatively easy today.


Notice the following:

4. Compete with Linux Head-On BED marketing is currently making the transition towards engaging Linux as a tier-1 competitor in the server & client markets. There are still some decisions to be made here (and headcounts to fill) to ensure that on a tactical basis, NT out markets Linux Some of the core deliverables include white papers, benchmarks, etc. More peripheral questions / issues include reclaiming retail shelf-space from Linux, etc We need engagement throughout the company (e g, retail) on this. Finally, getting the word out on NT’s architectural advantages over Linux is an imperative.


Then it says:

Open Source development is the greatest cloning machine of all time. Consequently, we must recognize that "Trade Secrecy" of source code will provide increasingly minimal protection over time and that aggressive patent procurement is our only investment defense. Additionally, strong patent procurement is a key enabler which allows us to publish more of our source code to leverage evangelization benefits (the patent application process is, in a manner of speaking, a form of source publication)

Initiatives (NOT discussed further in this paper) are underway to understand the options in this space.


“The following are all underway,” eh? What would that be? Those lawsuits Jim Allchin spoke about [1, 2]?

“The two [Halloween] documents in here from Vinod are the ones I want the board to see.”
      --Bill Gates
It is worth remembering that all these documents are spread with Bill Gates' oversight and endorsement, just like the AstroTurfing which he loves. At the time, when these documents leaked, Microsoft tried to portray the AstroTurf as an act it had nothing to do with; a lead participant, James Plamondon, insistingly denied this, saying that Bill Gates was a supporter of the tactics all along. His colleague Marshall Goldberg confirmed this in an internal presentation.

Likewise, when it comes to the Halloween Documents, Microsoft tried to dismiss this as “an engineer’s individual assessment of the market at one point in time.” The exhibits clearly show Bill Gates distributing this material quite enthusiastically to chief people at Microsoft. It means that Microsoft simply lied to save face.

At the end of the document we find out what's already "underway" at Microsoft:

The following are all underway:

1. Ramp-up / staff Linux competitive marketing efforts. 2. Ramp-up source licensing initiatives. DRG/MSDN is the owner for the umbrella but all component teams must begin evaluating what codebases would benefit the platform if they were evangelized via less restrictive licensing. 3. More proactively & aggressive secure patent rights to MSFT innovations that will be significant to the OSS fight. Development teams must shift mindsets from source code secrecy towards patents as the primary means of securing our key innovations. 4 [on-going] Create new IP in base scenarios - file sharing, management, etc.


"Ramp-up / staff Linux competitive marketing efforts" sounds like potential reference to more AstroTurfing, which is a reality. The remainder has a lot to do with patents, which we now know are used against GNU/Linux. The document as a whole is worth reading, assuming one has the patience. It's properly formatted below.




Appendix: Comes vs. Microsoft - exhibit PX08175, as text










Microsoft Confidential

Our Linux Strategy VinodV 5/19/99

Microsoft Confidential; ۩ 1999, All Rights Reserved Do Not Forward without Approval from Author.

Introduction This document discusses both our strategy and our plans for competing with Linux. To understand the strategy it is important to remember the following: - Linux isn’t most importantly a product/feature; it’s a philosophy change - Linux has no new specific features to co-opt - Unlike the NC: the NC touted TCO benefits, and thus we introduced ZAK/ZAW - Unlike the Internet: the Internet was loaded with technology changes, and thus we invested in browser technologies and reexamined all our existing products

The core strategic thrust of Linux is NOT an attack against some product/feature weakness of Microsoft. It’s an attack at the base of the commercial software industry - Intellectual Property.

Previous threats to Microsoft (the NC, Java, etc.) have been about replacing Microsoft’s IP with another company’s IP that claimed some new benefit (e.g. TCO). What differentiates Linux is that OSS attempts to extricate Intellectual Property all together.

Since many people have proposed how to deal with Linux, we thought it might be helpful as a thought exercise to quickly examine some of the alternative strategies we could consider. For each we include the "fatal flaws" that make them untenable.

1. Embrace Linux: MS APIs / Linux kernel -- release an MS version of Linux and/or release key MSFT platform technologies on Linux (e.g. parts of Win32, app server, etc.)

Pros: Ride the wave & try to evangelize Win32 Cons: Dramatically evangelizes Linux & may risk MSFT IP due to GPL license issues Fatal Flaw: - Impossible to make this revenue neutral with Windows biz. - Doesn’t protect the "crown jewel" IP from being targeted at a later date

2. Embrace Linux: Linux APIs / MS Kernel -- try to get Linux API’s on Windows -- get more hardcore about POSIX subsystem on NT to capture Linux app base

Pros: Capture some of the Linux dev mindshare by making it easy to bring Linux apps to NT Cons: Hurts Win32 evangelization Fatal Flaw: - There are no Linux apps that we covet.

3. Embrace Open Source: Publish NT Source -- release NT source code under a license similar to Sun’s community source license

Pros: Try to capture Linux’s evangelization benefits by publishing NT source Cons: ISVs getting hooked on undocumented API’s, support costs, etc. Fatal Flaw: - Microsoft is an IP company. Like the rest of the software industry, >90% of our IP valuation stems from Trade Secrecy of the source code. Open Source is mutually exclusive with Trade Secrecy. This plan would instantly make the various Win32 clones (e.g. http//www winehq.com) an order of magnitude more capable.

4. Lower the price of Windows -- release older / stripped versions of the OS for at lower price

Pros: Try to capture people who use Linux due to price sensitivity

Page 1

Plaintiff’s Exhibit 8175 Comes V. Microsoft

MS-CC-MDL 000000202974 HIGHLY CONFIDENTIAL




Microsoft Confidential

Cons: Building new versions of windows. Long-term support headaches Cannibalization of the "real" windows? Fatal Flaw: - Assumes that price is the primary motivator for Linux usage. This has not been borne out in reality.

What are the core strategies that we are going to pursue?

1. Fix our Sins

Linux’s most immediate contribution is highlighting our sins in some key market segments. There are already (large) investments in the company spun up to deal with our most pressing concerns such as reliability; remote admin; etc so we won’t spend further time describing them here. It is critical that we make progress in these areas

Currently, Linux gains horsepower due to VASTLY exaggerated negative claims about our abilities and corresponding VASTLY under reported positive claims about our innovative work. We must reverse the "conventional wisdom" that UNIX is technically superior to NT which is the foundation for Linux marketing. In most ways, NT is superior & the technical message needs to get out.

2. Innovating, Creating New IP

(Re-)recognize that we are an IP company and that in our networked world, functionality delivered via protocols is steadily replacing functionality which was once delivered via APIs Thus, innovation must occur both internal to our products, but also between computers.

Windows clients must always be able to communicate with Linux servers (and vice-versa). However, there MUST be additional value created when a Windows machine is touching another Windows machine. NOT doing this is akin to giving away the Win32 APIs. Every group defining protocols needs to remember this. Some core initiatives that are excellent demonstrations of this are:

Management - Deep, rich WMI instrumentation is an area where Windows and Win32 apps must excel. In addition to IP boundaries, Linux’s development methodology makes this difficult for Linux to provide leadership in breadth & uniformity of coverage/implementation.

Storage -- Rich, structured, remotable, queriable storage dramatically raises the bar versus today’s basic file system functionality. The benefits to client application vendors & server vendors are numerous and well detailed in other presentations.

These areas demonstrate functionality that IT managers -- once they’ve tasted it -- will (hopefully) find compelling enough to mandate across as many systems within their computing universes as possible. Letting our protocols become commoditized is a recipe for failure. We must innovate and keep our great advancements to ourselves. The fine balance between protecting/financing our innovations and interoperability will get more difficult overtime But, it is relatively easy today.

Outside of protocols we need advancements throughout the system. Advances in file formats (e.g., the disk structure), technology such as security, etc. are areas that are critical for us to innovate. We need to accelerate patenting every invention

3. Form Factor Proliferation This is a well-discussed area. Obviously PC’s will not be the exclusive center of computing in the near future and this addition to the OS requirements list provides the opening for low innovation competitors such as Linux in. We need to spread our technology everywhere And where we don’t have our OS present, we need to ensure the protocols are not IP latent and in fact open for us to use.

Page 2

MS-CC-MDL 000000202975 HIGHLY CONFIDENTIAL




Microsoft Confidential

4. Compete with Linux Head-On BED marketing is currently making the transition towards engaging Linux as a tier-1 competitor in the server & client markets. There are still some decisions to be made here (and headcounts to fill) to ensure that on a tactical basis, NT out markets Linux Some of the core deliverables include white papers, benchmarks, etc. More peripheral questions / issues include reclaiming retail shelf-space from Linux, etc We need engagement throughout the company (e g, retail) on this. Finally, getting the word out on NT’s architectural advantages over Linux is an imperative.

5. Getting Credit for the Openness and Availability of our Sources One of the key lessons learned from the Linux OS is the power of the Open Source model with respect to creating passionate, technically savvy development communities around a body of code. Reclaiming the hobbyist developer / "scratch an itch" developer communities is paramount for us (they were the original "long hairs" who introduced the PC to corporate America). While we may never be able to fully detract from Linux’s energy in this space, it is very important for us to focus our TREMENDOUS developer relations assets into this new "channel." JimAll presented a plan at the 3yr review that involved a 2-pronged attack on this channel:

a. Depth Licensing -- Ramping up full, formal source code licenses to ISVs/IHVs/Corps etc. by at least a factor of 10 vs. today’s efforts.

b. Breadth Licensing -- Reorganizing & creating new widely licensed, derivable, redistributable source code bases hosted on web sites targeting specific Win32 developer niche’s (e.g., ResKit level functionality).

6. Securing our Current & Future IP Once again, the core of the Linux phenomena -- and the #1 reason it tries to claim the "glow of inevitability" -- is it’s aversion to Intellectual Property (IP). Obviously, in terms of economic effects, IP is on par with motherhood & apple pie in its role in the world economy.

The belief that the "Open Source" pie will eventually gobble up ingredients from all the other pies is more dangerous to us & the software industry than the current Linux product

Open Source development is the greatest cloning machine of all time. Consequently, we must recognize that "Trade Secrecy" of source code will provide increasingly minimal protection over time and that aggressive patent procurement is our only investment defense. Additionally, strong patent procurement is a key enabler which allows us to publish more of our source code to leverage evangelization benefits (the patent application process is, in a manner of speaking, a form of source publication)

Initiatives (NOT discussed further in this paper) are underway to understand the options in this space.

Immediate Next Steps:

The following are all underway:

1. Ramp-up / staff Linux competitive marketing efforts. 2. Ramp-up source licensing initiatives. DRG/MSDN is the owner for the umbrella but all component teams must begin evaluating what codebases would benefit the platform if they were evangelized via less restrictive licensing. 3. More proactively & aggressive secure patent rights to MSFT innovations that will be significant to the OSS fight. Development teams must shift mindsets from source code secrecy towards patents as the primary means of securing our key innovations. 4 [on-going] Create new IP in base scenarios - file sharing, management, etc.

Please direct any questions / discussion to VinodV

Page 3

MS-CC-MDL 000000202976 HIGHLY CONFIDENTIAL



Credit: wallclimber

Comments

Recent Techrights' Posts

Who Asked Software in the Public Interest (SPI) for a Refund? ($100,000, Resulting in Losses of $267,201 in 12 Months, Highest-Ever Losses)
The IRS does not reveal who or what's tied to this refund (or the cause/reason)
"Cloud Computing" Was Always a Joke, But This Week Was the Punchline
Maybe stop following tech trends and fashions
 
Slopwatch: Google News is Promoting Fake 'Articles' About Fake Xubuntu, Fake Articles About Replacing Windows With GNU/Linux
The quality of the Web deteriorates and unless someone cleans up the mess, real sites will lose an incentive to produce anything
When "AI Layoffs" Mean Layoffs Due to the "AI" Bubble Popping
many people that are laid off by Microsoft claim to be specialists in "AI"
Mysterious grant forfeited, $100,000 from Software in the Public Interest accounts 2023
Reprinted with permission from Daniel Pocock
Evidence: bullying, student union behaviour: Armijn Hemel's FSFE resignation
Reprinted with permission from Daniel Pocock
Evidence: psychological abuse, stalking, Galia Mancheva, Susanne Eiswirt ignored by FSFE judgment for Matthias Kirschner
Reprinted with permission from Daniel Pocock
Helping FSFE scam victims and conference organisers
Reprinted with permission from Daniel Pocock
Nigerian fraud in FSFE constitution
Reprinted with permission from Daniel Pocock
Worrying and Amusing Stories of "Clown Computing" Gone Awry
Many of these disasters could be avoided
Some Large German Media Covers Richard Stallman's Talks in Germany Earlier This Week
LLM-based chatbots are just "bullshit generators" (as he has long called them)
Links 22/10/2025: Amazon Plans to Replace Workers With Robotics, AWS and Clown Computing in General Ridiculed
Links for the day
Gemini Links 22/10/2025: Niri Completely Changes Multitasking and Overview of Diff-ers
Links for the day
Links 22/10/2025: Study on Misinformation by Slop and Heavily Debt-Sabbled Microsoft OpenAI (ClosedSlop) Uses "Browser" as Gimmick/Distraction
Links for the day
They've Already Spent Close to a Million Dollars on Lawyers and Sent Us About 50 KG of Legal Papers (Sponsored by Mysterious Third Party) to Try to Censor Techrights, Without Success
They try to overcompensate with sheer volume for a lack of solid, clear arguments (we are the victims here)
Trouble in Red Hat/IBM and a Retreat to Ponzi Economics in Search of Wall Street Market Heist
Would you invest your life savings in this kind of crap?
12 Months Ago the 'Hulk Hogan of UEFI' Officially Went 'Tag-Team'
We're actually sort of flattered or proud that such despicable people are so desperate to censor us
"Cloud Computing" Does Not Mean Safety
Fault tolerance is related to the notion of software freedom
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Tuesday, October 21, 2025
IRC logs for Tuesday, October 21, 2025
The Fall of Windows: From Something to Nothing
Of course Microsoft will pretend everything is fine and "just trust the hey hi" (AI)
Sounds Like Fedora is Ready to Become Less of a Slave of Microsoft (GitHub)
This seems like a belated move in a positive direction
XBox is a Dead Microsoft Product in a Dying Industry
It's probable that another wave of XBox layoffs is just over the horizon (maybe even before month's end)
Progress on Techrights Site Search
Fun times
IBM's Bluewashing of Red Hat Means the Layoffs Are Silent, Barely Reported
Don't wait to hear about "Red Hat layoffs"
Gemini Links 21/10/2025: Happy Disconnection, AWS Falling Apart, Closing of Gemlog Blue
Links for the day
Full Audio of Today's Richard Stallman Talk in the Technical University of Munich
Free/Libre software and freedom in the digital society
Microsoft XBox is Just Vapourware (Promises of Hardware That Doesn't Exist), Real Products Perish
just as developers lose interest in developing for XBox Microsoft is increasing the costs imposed upon them
Slopwatch: Fake Articles (Slop) in "Linux" Clothing in Google News (Noise)
all about what Google does
Links 21/10/2025: Even "Inventor of Vibe Coding" Rejects Vibe Coding, USPTO Experiments With Slop in Examination
Links for the day
Richard Stallman Talk Now Available for Viewing (Archived Copy, Not Live-streamed)
This recording is over 2 hours old
Links 21/10/2025: AWS-Induced Chaos and Social Control Media Curbs
Links for the day
Gemini Links 21/10/2025: Programming, StarGrid, Brand-New Palm OS Strategy Game in 2025, and Chatbot as Addiction Mechanisms
Links for the day
The African Lion and the American Cowards
Safaris exist for people to watch and enjoy animals
Amazon Web Shenanigans Perfectly Timed for Today's Talk by Richard Stallman
Maybe listen to him instead of looking for excuses to ridicule the messenger
Mission:Libre Has Taken Off (Project by Carmen Maris)
there will be a lot more to report on next month (after the event)
Techrights to Publish More EPO Leaks Next Week
We're meanwhile also doing lots of work on search, whose interface now looks better
Links 21/10/2025: 'The Lost Art' of Neon Signs and Twitter (X) to Enable Identity Theft (or Handle Theft) as a Service
Links for the day
Plagiarism With LLM Slop: Hindustan Times (HT Digital Streams Limited) Has Become a Slop Factory/Hub
What a disgrace
A radical proposal to keep your personal data safe, by Richard Stallman
"The surveillance imposed on us today is worse than in the Soviet Union. We need laws to stop this data being collected in the first place"
Next Week We Launch Search at Techrights
We're planning to launch it some time next week. Maybe Tuesday, maybe Thursday.
Talk by Richard Stallman Will be Live-streamed in Less Than 10 Hours
Happy hacking
"No Kings" in the Software World (GAFAM Should Not Exist, Either)
"No Kings" is a good slogan. Let's start by ridding ourselves of masters, not only those who reside in DC or visit DC
Every Morning
Bugs/edge cases combined with automation can spell disaster
Insane, Deliberately Dishonest, or Just Another Bigot?
very intellectually-dishonest human being
A Lot of Techrights is Built on Perl
Perl also runs the sister site
The Register MS Selling Slop for Microsoft (Vapourware, Ponzi Scheme, False Claims)
What will be left of The Register MS if it keeps repeating falsehoods and looking to profit from Ponzi schemes?
analytics.usa.gov Says Less Than 14% of Web Requests (to Government Sites) Come From Vista 11
Vista 11 was released more than 4 years ago!
People Who Attempt to Take Down Correct Information Need a Doctor a Day
“Journalism is printing something that someone does not want printed. Everything else is public relations.” ― George Orwell
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Monday, October 20, 2025
IRC logs for Monday, October 20, 2025
Vista 11 is Sinking While Microsoft is PIPing (Mass Layoffs But Silent Layoffs)
We're witnessing a shift in platform dominance
Richard Stallman is Having a Good Week Already (Stallman Was Right About 'Clown Computing')
That alone is worth bringing up in his talk
An Update About Soylent News, With Jan Rinok "Back in the Saddle"
Burnout or "near burnout" a possibility when having to curate abuse
When Prominent GNU/Linux Distros Are Run by Spies
What has Microsoft Canonical become?
More Publishers and Companies Nowadays Say "GNU/Linux", Not "Linux"
It's not to see InstallAware saying GNU/Linux this week
Google News is Now Promoting a Parasitic Slopfarm Called "findarticles.com", Where Plagiarism of "Linux" Articles is Rampant
Does Google even care about the slop epidemic? Google itself is a vendor of slop now (and it calls it "Gemini")
Gemini Links 20/10/2025: Pumpkin Carving, "Hey Hi", and Other Buzzwords
Links for the day
Slopwatch: Google News Promoting Fear, Uncertainty, Doubt (FUD)
What is the value of Google News if so many results in it are fake 'articles?
Rejecting 'Snoop-Phones' and Turning "Old" Phones (or Tablets) Into Freedom-Respecting Appliances
Paul Fernhout (pdfernhout.net) wrote back to Akira Urushibatathis this past weekend
Our Uptime This Year Was Better Than AWS (Also a Lot Cheaper)
We never used "the cloud"
Amazon Web Shenanigans
An ongoing, experimental endeavour
Death of Elias Diem: FSFE mailing list archives hidden
Reprinted with permission from Daniel Pocock
Links 20/10/2025: Louvre Museum Reveals Weakness, About 7 Million Protest US Turning Into Oligarchy/Monarchy
Links for the day
They Should Have Listened to Techrights Over a Month Earlier (Xubuntu Site Compromised)
we reported this issue about 40 days earlier and nobody did anything about it
Richard Stallman to Give Another Talk Today in Bavaria (Bavarian Academy of Science)
Tomorrow at 6 PM he speaks in Munich
Apple is the Company of Dictators and Worse
Apple is just another greedy corporation in search of sweatshops and even pedophiles (especially the high-profile ones)
Counting Unhatched Eggs Is Not Counting Chickens
Everything here will persist as normal
Barry Kauler Explains That Puppy Linux and EasyOS Exclude Systemd to Keep Things Simple
Barry Kauler's Puppy Linux is in the community's hands. He now focuses on EasyOS and more.
The "Infinite Bread"
The biblical story of Jesus feeding the 5,000 has software parallels
Half a Year After Brian Fagioli Got Kicked Out of BetaNews for Slop He's Still Doing LLM Slop and Slop Images Targeting 'Linux' (Plagiarising Original Works)
If the Web gets polluted or flooded by slopfarms such as these, and Slashdot then sends traffic so these slopfarms (Slashdot probably doesn't do this intentionally), then real writers with real knowledge of GNU/Linux will lose the spark for publishing
In Many Cases and in Many Different Ways, Technology Became Less Durable and Less Reliable Over Time
The "modern" things are more complex. And complexity is a foe or reliability and repair-ability.
Microsoft's LinkedIn is Losing Money, Traffic, and Hope; Now It Wants to Sell Its Users' Lifeblood (and Data)
Let this be a reminder of what social control media really is about
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Sunday, October 19, 2025
IRC logs for Sunday, October 19, 2025
Campaign of FUD Against Framework Laptops and GNU/Linux (Using Microsoft's Attack on Linux, 'Secure Boot')
Ritual Defamation Cult has turned its attention over to Framework
Microsoft Lunduke: Freedom of Speech Means Spreading What I Have to Say and Banning People I Disagree With
4Chan is one he aims for and he is siccing 4Chan trolls at people he doesn't like
Liberation From 'The Feed'
They rank things based on the editor's choice/ideology (he or she knows the sponsors, hence the masters)
Microsoft's Killing of Vista 10 Seems to Have Resulted in More Articles About GNU/Linux (But Also FUD)
We not only saw a rise in traffic, we also saw a remarkable rise in the number of articles