06.06.19

Gemini version available ♊︎

Chapter 6: Damning With Faint Praise — Take the Right Examples of Free Software and Exploit Them for Everything

Posted in Free/Libre Software, FUD, GNU/Linux, Microsoft at 1:16 pm by Dr. Roy Schestowitz

Table of Contents

Introduction: Cover and quick Introduction [PDF]

Chapter 1: Know your enemies– Act like a friend [PDF]

Chapter 2: Work with the system– Use OEMs and your legal team [PDF]

Chapter 3: Playing the victim– Show the world that too much freedom hurts development [PDF]

Chapter 4: You get what you pay for– Getting skeptics to work for you [PDF]

Chapter 5: Open Source Judo– How to bribe the moderates to your side [PDF]

You are here ☞ Chapter 6: Damning with faint praise– Take the right examples of free software and exploit them for everything [PDF]

Chapter 7: Patent War– Use low-quality patents to prove that all software rips off your company

Chapter 8: A foot in the door– how to train sympathetic developers and infiltrate other projects

Chapter 9: Ownership through Branding– Change the names, and change the world

Chapter 10: Moving forward– Getting the best results from Open source with your monopoly


You might not believe me if I tell you that we decide what “cool” means, unless you look at the results in real life. We have the press working for us, we have open source doing what we need even as they believe they are fighting us. We can keep the press obedient in exchange for access, we can enjoy allegiance from open source from other deals that we make.

If our research shows that something is cool, we buy it or we produce it. One thing you can’t do is make the same thing look cool forever. No matter how happy some customers are, or how much they rely on our software, we are still going to lead them away from one thing and towards another– it isn’t just because it’s better; it’s because if we let them rely on what they already have, we won’t get to sell them anything new.

Now with cloudware, we control the access to the software. But it is still necessary for people to perceive that we are working to make improvements. The most convincing way to do this is to keep chasing what’s new– and dragging people from one thing to the next.

Once again we do this as friends, with a carrot of features and not just the stick of walled access and fees. We aren’t just forcing people to pay, but leading them to want their subscriptions and feel good about them. We make promises about the new features being useful, but we also need the press and our marketing to make our products cool. No matter how much of a monopoly we work to maintain, there are other companies out there looking to create something before we can. We need to be sure we own and control it– otherwise, it belongs to them.

Another great thing about what’s new is that people don’t know anything about it. We can write our own narrative about new products, and until enough people gain access and knowledge (and preferably first-hand experience) they can’t say very much about the product that we can say twice as much about. New products let us run circles around people who claim to know about them– they give us a unique advantage.

As for lack of familiarity, we can actually use that to increase interest rather than lose business. If the product is attractive enough, we can use the people who are familiar with it against the people who aren’t, and make the latter look like they are ignorant if they are unfamiliar with our product line. So the incentive to do business is to continue to appear knowledgeable. This tactic works notably well among enthusiasts and professionals.

If you ask people to define “cool,” they can’t always come up with something concrete. But you don’t have to be a cool person at all to know what definition of “cool” matters to us– “cool” is what’s new and what people want. That’s as cool as we will ever need to be. That’s what keeps us where we are, and everyone else where they are. And that’s what we have to keep control of, if we want to stay where we are.

On the other side of the coin we have what’s not cool: stuff that’s not new, or stuff that people don’t want. That’s what we have to avoid offering– if that’s all we have, we need to buy or develop new things to offer.

A superior product is like a politician’s speech– the best way to sell a lie is to put a truth in it, so people assume the rest of it is also the truth. And when you want to sell a new product you can do the same thing: start with a feature people are desperate to have, and you can build a lot of garbage around it as long as the important features are satisfying enough.

It should be more than obvious that some of these features– even some of the best features– are going to be proprietary. So it becomes imperative if we are going to compete with and also infiltrate open source that we need to loosen the hold that free software has on the narrative.

A schism can be hashed out and resolved– what we want is to widen it to a chasm and actually hand the reins of free software over to open source, so that all “open source” is forever a way to steer people towards our features.

Everything cool (that we care about) is new and wanted, and everything uncool is old and boring and standard. To keep churning out cooler, newer products (not always cool like Apple, sometimes just cool like an update with a few new features) we need to use our shills to show everyone how uncool the alternatives are. As long as we look cool and friendly, people will be reluctant to care that we need to go after our competition in this way. After all, cool is also about winning, and winning means someone loses somewhere.

By the time people are convinced that our competitors aren’t cool, they won’t want to side with them anymore and won’t defend them from us.

We need to turn rich against poor, as mentioned two chapters ago– and we need to turn inexperienced users against experienced ones, to prevent skeptics from handing down their stories to potential customers. It is essential to paint seasoned experts as gray and irrelevant, as has-beens who don’t understand the genius of our new offerings. And it is essential to paint every tool we used to offer or never offered as outdated and obsolete.

When dealing with open source, the most important person to paint as a has-been is Richard Stallman. He and Gates are decades-long rivals, diametrically opposed to each other in their philosophies. But more relevant is that he leads the movement that opposes us– we need to keep open source on our side, and lead them further away from free software.

Fortunately, Stallman and his followers are tightly-knit in their ideology. Attacking any of them is like attacking all of them– we can play up their hacker style as social ineptitude, their adherence (where it exists) to standards and interoperability as a refusal to evolve, their playful culture as a refusal to grow up and be professional, and their self-reliance and independence as being non-team-players and even toxic masculinity.

Their hacker philosophy is about putting certain values first– just as we use new features to get people to accept new flaws that we can promise to fix later (and then say that we have a greater commitment to security) and use open source to bring people to our exclusive software lines, we can use their values to steer the next generation of customers (and critics) towards a more corporate culture.

Any social values that we are saddled with keeping up appearances about in the workplace, we can instill through open source and then claim the rest are not putting enough emphasis on. Of course, some of these values are good values in and of themselves. But as much as we have “social value theater” in the workplace and have to play along, we can dump the same corporate culture onto anyone who will call it professionalism, and then say everyone else is just unprofessional and toxic.

In the short run we can use this against Stallman and his organization, but in the long run we can even use this to shackle Linus and gradually push him out the door. In our culture, it doesn’t pay to be eccentric except when it makes us billions– get with the program or get out. A leader that isn’t making us money is a leader who has let us down, and we need to get rid of them as quickly as possible.

The values of free software developers and the values of free software itself go hand in hand. We need to denigrate most of their software, along the same lines that we denigrate the people who create it. As said over and over, we need to rely on shills, fans, and “useful third parties” to denigrate these people and their work. We also need a “path forward” to our products. Whenever we outline our strategies to feed to our shills and the tech press, they need to paint free software and its authors as true gems– from a bygone era.

“Yes, that was really great. But now, it’s time to look to the future.”

The future is (always) us, and the products we want people to use. There’s no rise in quarterly revenue for tried-and-trusted, except when it’s merely the glue holding our new products together.

Relevant quotes from the Halloween documents:

“OSS poses a direct, short-term revenue and platform threat to Microsoft — particularly in server space. Additionally, the intrinsic parallelism and free idea exchange in OSS has benefits that are not replicable with our current licensing model and therefore present a long term developer mindshare threat.”

“However, other OSS process weaknesses provide an avenue for Microsoft to garner advantage in key feature areas such as architectural improvements (e.g. storage+), integration (e.g. schemas), ease-of-use, and organizational support.”

“OSS process vitality is directly tied to the Internet”

“The OSS process is unique in its participants’ motivations and the resources that can be brought to bare down on problems. OSS, therefore, has some
interesting, non-replicable assets which should be thoroughly understood.”

“Open source software has roots in the hobbyist and the scientific community and was typified by ad hoc exchange of source code by developers/users.”

“Credit for the first instance of modern, organized OSS is generally given to Richard Stallman of MIT. In late 1983, Stallman created the Free Software
Foundation (FSF) — http://www.gnu.ai.mit.edu/fsf/fsf.html — with the goal of creating a free version of the UNIX operating system.”

“Commercial software development processes are hallmarked by organization around economic goals. However, since money is often not the (primary) motivation behind Open Source Software, understanding the nature of the threat posed requires a deep understanding of the process and motivation of Open Source development teams.”

“In other words, to understand how to compete against OSS, we must target a process rather than a company.”

“These individuals are more like hobbyists spending their free time / energy on OSS project development while maintaining other full time jobs. This has begun to change somewhat as commercial versions of the Linux OS have appeared.”

“Coordination of an OSS team is extremely dependent on Internet-native forms of collaboration.”

“OSS projects the size of Linux and Apache are only viable if a large enough community of highly skilled developers can be amassed to attack a problem.”

“Common goals are the equivalent of vision statements which permeate the distributed decision making for the entire development team. A single, clear
directive (e.g. “recreate UNIX”) is far more efficiently communicated and acted upon by a group than multiple, intangible ones”

“Because the entire Linux community has years of shared experience dealing with many other forms of UNIX, they are easily able to discern — in a non-confrontational manner — what worked and what didn’t.”

“Having historical, 20:20 hindsight provides a strong, implicit structure. In more forward looking organizations, this structure is provided by strong, visionary leadership.”

“Raymond posits that developers are more likely to reuse code in a rigorous open source process than in a more traditional development environment because they are always guaranteed access to the entire source all the time.”

“Treating your users as co-developers is your least-hassle route to rapid code improvement and effective debugging.”

“Release early. Release often. And listen to your customers.”

“Because the developers are typically hobbyists, the ability to `fund’ multiple, competing efforts is not an issue and the OSS process benefits from the ability to pick the best potential implementation out of the many produced.”

“Universities are some of the original proponents of OSS as a teaching tool.”

“Linus Torvalds is a celebrity in the Linux world and his decisions are considered final. By contrast, a similar celebrity leader did NOT exist for the BSD-derived efforts.”

“What are the core strengths of OSS products that Microsoft needs to be concerned with?”

“The single biggest constraint faced by any OSS project is finding enough developers interested in contributing their time towards the project. As an
enabler, the Internet was absolutely necessary to bring together enough people for an Operating System scale project.”

“Like commercial software, the most viable single OSS project in many categories will, in the long run, kill competitive OSS projects and `acquire’ their IQ assets. For example, Linux is killing BSD Unix and has absorbed most of its core ideas (as well as ideas in the commercial UNIXes).”

“One of the most interesting implications of viable OSS ecosystems is long-term credibility.”

“Long term credibility exists if there is no way you can be driven out of business in the near term. This forces change in how competitors deal with you.”

“a product/process is long-term credible if FUD tactics can not be used to combat it.”

“OSS systems are considered credible because the source code is available from potentially millions of places and individuals.”

“The likelihood that Apache will cease to exist is orders of magnitudes lower than the likelihood that WordPerfect, for example, will disappear. The
disappearance of Apache is not tied to the disappearance of binaries (which are affected by purchasing shifts, etc.) but rather to the disappearance of source code and the knowledge base.“

“Inversely stated, customers know that Apache will be around 5 years from now — provided there exists some minimal sustained interested from its
user/development community.”

“The GPL and its aversion to code forking reassures customers that they aren’t riding an evolutionary `dead-end’ by subscribing to a particular commercial version of Linux.”

“The “evolutionary dead-end” is the core of the software FUD argument.”

From https://antitrust.slated.org/halloween/halloween1.html

Share in other sites/networks: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Reddit
  • email

Decor ᶃ Gemini Space

Below is a Web proxy. We recommend getting a Gemini client/browser.

Black/white/grey bullet button This post is also available in Gemini over at this address (requires a Gemini client/browser to open).

Decor ✐ Cross-references

Black/white/grey bullet button Pages that cross-reference this one, if any exist, are listed below or will be listed below over time.

Decor ▢ Respond and Discuss

Black/white/grey bullet button If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

DecorWhat Else is New


  1. [Meme] [Teaser] GitHub an Expensive and Dangerous Trap (Also: Misogyny Hub)

    The ongoing Microsoft GitHub exposé will give people compelling reasons to avoid GitHub, which is basically just a subsidised (at a loss) trap



  2. Norway Should Have Voted Against Benoît Battistelli's Illegal (Anti-)'Strike Regulations' at the European Patent Office

    Benoît Battistelli‘s EPO faced no real and potent opposition from Norwegian delegates, who chose to abstain from the vote on the notorious and illegal so-called ‘Strike Regulations’ (they’re just an attack on strikes, an assault on basic rights of labourers)



  3. Links 19/10/2021: Sequoia PGP LGPL 2.0+, Open RAN Adoption

    Links for the day



  4. [Meme] [Teaser] Benoît Battistelli, King of Iceland

    Later today we shall see how the current deputy of the head of the EPO‘s overseeing body was in fact likely rewarded for her complicity in Benoît Battistelli‘s abuses against EPO staff, including staff from Iceland



  5. IRC Proceedings: Monday, October 18, 2021

    IRC logs for Monday, October 18, 2021



  6. Links 19/10/2021: MyGNUHealth 1.0.5 and Ubuntu 22.04 Now Developed

    Links for the day



  7. [Meme] [Teaser] Thrown Under the Bus

    Tomorrow we shall look at Danish enablers of unlawful EPO regulations, Jesper Kongstad and Anne Rejnhold Jørgensen



  8. The World Needs to Know What Many Austrians Already Know About Rude Liar, the Notorious 'Double-Dipper'

    Today we publish many translations (from German) about the Austrian double-dipper, who already became the subject of unfavourable press coverage in his home country; he’s partly responsible for crushing fundamental rights at the EPO under Benoît Battistelli‘s regime



  9. The EPO’s Overseer/Overseen Collusion — Part XVI: The Demise of the Austrian Double-Dipper

    Friedrich ‘Rude Liar’ Rödler is notorious in the eyes of EPO staff, whom he was slandering and scandalising for ages while he himself was the real scandal



  10. Links 18/10/2021: Porteus Kiosk 5.3 and Ventoy 1.0.55

    Links for the day



  11. [Meme] [Teaser] More to Life Than Patents

    Greedy sociopaths oughtn’t be put in charge of patent offices; this is what’s dooming the EPO in recent years (all they think about is money



  12. Microsoft GitHub Exposé — Part II — The Campaign Against GPL Compliance and War on Copyleft Enforcement

    Microsoft contemplated buying GitHub 7.5 years ago; the goal wasn’t to actually support “Open Source” but to crush it from the inside and that’s what Microsoft has been doing over the past 2.5 years (we have some details from the inside)



  13. Links 18/10/2021: Linux 5.15 RC6 and 7 New Stable Kernels

    Links for the day



  14. [Meme] The Austrian School of Friedrich Rude Liar

    With reference to the Austrian School, let’s consider the fact that Friedrich Rude Liar might in fact be standing to personally gain by plundering the EPO‘s staff by demonising them while helping Benoît Battistelli crush them



  15. IRC Proceedings: Sunday, October 17, 2021

    IRC logs for Sunday, October 17, 2021



  16. How (Simple Technical Steps) to Convince Yourself That DuckDuckGo is Just Spyware Connected to Microsoft, Falsely Advertised as 'Privacy'

    In recent days we published or republished some bits and pieces about what DuckDuckGo really is; the above reader dropped by to enlighten us and demonstrate just how easy it is to see what DuckDuckGo does even at the client side (with JavaScript); more people need to confront DuckDuckGo over this and warn colleagues/friends/family (there’s more here)



  17. Austria's Right-Wing Politicians Displaying Their Arrogance to EPO Examiners

    The EPO‘s current regime seems to be serving a money-hungry lobby of corrupt officials and pathological liars; tonight we focus on Austria



  18. [Meme] Friedrich Rödler's Increasingly Incomprehensible Debt Quagmire, Years Before EPO Money Was Trafficked Into the Stock Market

    As it turns out, numerous members of the Administrative Council of the EPO are abundantly corrupt and greedy; They falsely claim or selfishly pretend there’s a financial crisis and then moan about a "gap" that does not exist (unless one counts the illegal gambling, notably EPOTIF, which they approved), in turn recruiting or resorting to scabs that help improve ‘profit margins’



  19. The EPO’s Overseer/Overseen Collusion — Part XV: Et Tu Felix Austria…

    Prior to the Benoît Battistelli and António Campinos regime the EPO‘s hard-working staff was slandered by a corrupt Austrian official, Mr. Rödler



  20. Links 17/10/2021: Blender 2.93.5, Microsoft Bailouts

    Links for the day



  21. Links 17/10/2021: GhostBSD 21.10.16 and Mattermost 6.0

    Links for the day



  22. IRC Proceedings: Saturday, October 16, 2021

    IRC logs for Saturday, October 16, 2021



  23. [Meme] First Illegally Banning Strikes, Then Illegally Taking Over Courts

    The vision of Team Battistelli/Campinos is a hostile takeover of the entire patent system, not just patent offices like the EPO; they’d stop at nothing to get there



  24. Portuguese Network of Enablers

    Instead of serving Portuguese people or serving thousands of EPO workers (including many who are Portuguese) the delegation from Portugal served the network of Campinos



  25. In Picture: After Billions Spent on Marketing, With Vista 11 Hype and Vapourware, No Real Gains for Windows

    The very latest figures from Web usage show that it’s hardly even a blip on the radar; Windows continues bleeding to death, not only in servers



  26. [Meme] [Teaser] Double-Dipping Friedrich Rödler

    As we shall see tomorrow night, the EPO regime was supported by a fair share of corrupt officials inside the Administrative Council



  27. The EPO’s Overseer/Overseen Collusion — Part XIV: Battistelli's Iberian Facilitators - Portugal

    How illegal “Strike Regulations” and regressive ‘reforms’ at the EPO, empowering Benoît Battistelli to the detriment of the Rule of Law, were ushered in by António Campinos and by Portugal 5 years before Campinos took Battistelli’s seat (and power he had given himself)



  28. Links 16/10/2021: SparkyLinux Turns 10 and Sculpt OS 21.10

    Links for the day



  29. “Facebook Whistleblowers” Aside, It Has Been a Dying Platform for Years, and It's Mentally Perverting the Older Generation

    Guest post by Ryan, reprinted with permission



  30. [Meme] Microsoft Has Always Been About Control Over Others

    Hosting by Microsoft means subjugation or a slavery-like relationship; contrary to the current media narrative, Microsoft has long been censoring LinkedIn for China’s autocratic regime; and over at GitHub, as we shall show for months to come, there’s a war on information, a war on women, and gross violations of the law


RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

Recent Posts