#satya-nadella — Public Fediverse posts

https://lamadredeltopo.rebuscando.info/el-director-ejecutivo-de-microsoft-defiende-el-riesgo-que-tomo-al-invertir-en-openai

#microsoft #openai #satyanadella

Nadella Defends OpenAI Investment Amid Legal Scrutiny

Microsoft CEO Satya Nadella testifies in court over Elon Musk's lawsuit about OpenAI's shift from non-profit to profit.

#OpenAI, #Microsoft, #ElonMusk, #SatyaNadella, #AI

https://newsletter.tf/nadella-defends-openai-investment-musk-lawsuit/

Microsoft's investment in OpenAI has grown from $13 billion to $92 billion. Elon Musk is suing OpenAI and Microsoft.

#OpenAI, #Microsoft, #ElonMusk, #SatyaNadella, #AI
https://newsletter.tf/nadella-defends-openai-investment-musk-lawsuit/

https://winbuzzer.com/2026/05/10/musk-v-altman-docs-microsoft-executives-had-reserv-xcxwbn/

Musk-Altman Trial Reveals Microsoft's 2018 OpenAI Doubts

#AI #MuskVAltman #Microsoft #OpenAI #SamAltman #ElonMusk #GregBrockman #SatyaNadella #MicrosoftAzure #AGI #AIInvestment #AIPartnerships #ChatGPT

US Top News and Analysis | Musk v. Altman heads to court next week. Here's what's at stake

AI generated summary, Read the full article for complete information.

The high‑profile lawsuit between Elon Musk and OpenAI CEO Sam Altman is set to go to trial in Oakland, California, with jury selection beginning Monday. Musk’s $134 billion suit alleges that OpenAI, Altman and president Greg Brockman broke a promise to keep the AI lab a nonprofit, seeking to unwind the company’s for‑profit restructuring, return “ill‑gotten” gains to the nonprofit, and remove Altman and Brockman from their roles. OpenAI, now valued at over $850 billion after creating a for‑profit subsidiary, calls the case baseless and a “harassment campaign,” while Musk’s attorneys have narrowed the claims to unjust enrichment, fraud, constructive fraud and breach of charitable trust. The trial, presided over by Judge Yvonne Gonzalez Rogers, will be split into a liability phase—expected to last through mid‑May—and a remedies phase, with a nine‑person jury deciding only on liability. The outcome could impact both Musk’s upcoming SpaceX IPO and OpenAI’s anticipated public offering later this year.

Read more: https://www.cnbc.com/2026/04/24/musk-v-altman-trial-openai-lawsuit-xai.html

#ElonMusk #SamAltman #SatyaNadella #OpenAI #Microsoft #GregBrockman #YvonneGonzalezRogers

AI generated summary, Read the full article for complete information.

@dch

I wonder if Satya Nadella has any regrets about cozying up to an orange autocrat and kissing his ass.

#SatyaNadella #Satya_Nadella

If Copilot really is "for entertainment purposes only", then it should be advertised like this.🍿

Celebrating 1+ years since users of M365 Office tools have been redirected to M365 Copilot chat UI by force. The digital equivalent of eyelid clamps.😬

(No, the poster is not GenAI, just copy-paste & font generators, thanks for asking.)

#Microsoft #Copilot #ClockworkOrange #SatyaNadella

https://winbuzzer.com/2026/04/05/ex-microsoft-engineer-believes-azure-problems-stem-from-talent-exodus-xcxwbn/

Ex-Microsoft Engineer: Azure Runs on Manual Fixes After Talent Exodus

#MicrosoftAzure #Microsoft #CloudComputing #SatyaNadella #BigTech #AIInfrastructure #Cloud

via #Microsoft : Announcing Copilot leadership update

https://ift.tt/zChfuW4
#Microsoft #Copilot #LeadershipUpdate #AILeadership #Superintelligence #SATYANADELLA #MustafaSuleyman #MicrosoftAI #CopilotExperience #CopilotPlatform #Microsoft365 #AIModels #FrontierModels #TechNew…

via #Microsoft : Microsoft announces Experiences + Devices leadership changes

https://ift.tt/alWtvOH
#Microsoft #ExperiencesAndDevices #LeadershipChanges #RajeshJha #SatyaNadella #MicrosoftNews #ExecutiveLeadership #CorporateNews #TechLeadership #MicrosoftBlog #FY27 #Executiv…

https://winbuzzer.com/2026/03/09/satya-nadella-credits-intel-mac-windows-office-success-xcxwbn/

Satya Nadella Credits Intel and Apple for Microsoft's Rise

#Intel #SatyaNadella #Microsoft #BigTech #Apple #Mac #MicrosoftWindows #MicrosoftAzure #MicrosoftOffice #Microsoft365 #MicrosoftExcel #MicrosoftWord #Software

Who ever believed that #AshaSharma got a "blank check" to resurrect #Xbox needs to get a their money back from their lobotomy.

#SatyaNadella has been bully with their gaming division to get more profits. That's why #Microsoft prostituted Halo and Fable to #PlayStation5.

A blank check does not make sense. Layoffs do.

#Videogames #Gaming #Games #MicrosoftGaming

Microsoft’s “Microslop” Discord Ban Backfires: What AI Builders Can Learn from This Epic Moderation Fail

2,644 words, 14 minutes read time.

The “Microslop” Catalyst: When Automated Moderation Becomes a PR Liability

The recent escalation on Microsoft’s official Copilot Discord server serves as a stark reminder that in the high-stakes world of generative AI, the community’s perception of quality is as vital as the underlying architecture itself. In early March 2026, what began as a routine effort to maintain decorum within a product-support hub rapidly spiraled into a live case study of the Streisand Effect. Reports from multiple industry outlets confirmed that Microsoft had implemented a blunt, automated keyword filter designed to silently delete any message containing the term “Microslop.” This derogatory portmanteau has been increasingly used by developers and power users to describe what they perceive as low-quality, intrusive, or “sloppy” AI integrations within the Windows ecosystem. While the corporate intent was likely to prune what a spokesperson later categorized as “coordinated spam,” the execution triggered a tidal wave of digital civil disobedience. Instead of silencing the critics, the automated system provided a focal point for them, validating the sentiment that the tech giant was more interested in brand preservation than addressing the technical grievances that birthed the nickname.

Analyzing the root of this frustration reveals that the term “slop” is often an emotional reaction to a very real technical burden placed on the developer community. For instance, attempting to upgrade a SharePoint Framework (SPFx) project from version 1.14.x to the recently released 1.22.x is frequently described by those in the trenches as a “blood bath” of error messages and cryptic warnings. The transition is not merely a version bump; it is an overhaul of the build toolchain that often leaves developers debugging deep-seated errors that appear to stem from AI-generated or “slop-induced” bugs within M365 and community plug-ins. When a developer spends three days chasing an error only to find it buried in a low-quality, automated code suggestion or a poorly integrated community tool, the “Microslop” label stops being a joke and starts being an accurate description of a broken workflow. This disconnect between Microsoft’s “AI-first” marketing and the gritty, error-prone reality of its development frameworks is precisely why a simple keyword filter was never going to be enough to contain the community’s mounting resentment.

The Streisand Effect: How Censorship Becomes a Signal

The failure of the “Microslop” ban is a textbook example of how heavy-handed moderation can amplify the very information it seeks to suppress. In the context of AI builders, this incident highlights the danger of using automated tools to sanitize discourse, as it inadvertently creates a “badge of resistance” for the user base. Every bypassed filter and every subsequent ban on the Copilot Discord became a signal to the broader industry that there was a significant rift between Microsoft’s narrative of AI “sophistication” and the community’s lived experience with the product. Furthermore, by escalating from keyword filtering to a full server lockdown, Microsoft effectively confirmed the power of the “Microslop” label. This elevated the term from a minor annoyance to a headline-grabbing symbol of corporate insecurity, demonstrating that the more a corporation tries to hide a piece of information, the more the public will seek it out and amplify it.

This phenomenon is particularly dangerous for AI-centric companies because the technology itself is already under intense scrutiny for its reliability and ethical implications. If a builder cannot manage a community hub without resorting to blunt-force censorship, it raises uncomfortable questions about how they manage the more complex, nuanced guardrails required for the Large Language Models (LLMs) themselves. The internet rarely leaves such attempts at suppression unpunished; in this case, the ban led to the creation of browser extensions and scripts specifically designed to spread the nickname across the web. This demonstrates that in 2026, community management is no longer just an administrative task; it is a critical component of brand integrity that requires a much more sophisticated approach than a simple “find and replace” blocklist. Builders must recognize that transparency is the only effective dampener for the Streisand Effect, as any attempt to use automation to hide dissatisfaction only serves to validate the critics.

Why the “Slop” Narrative Resonates: The Technical Quality Gap

At the heart of the “Microslop” controversy lies a deeper, more substantive issue regarding the growing perception that AI integration has entered a period of diminishing returns, often referred to as the “slop” era. The term “slop” gained significant cultural weight after major linguistic authorities and industry analysts began using it to specifically define the flood of low-quality, mass-produced AI content clogging the modern internet. When users apply this term to a tech giant, they are not merely engaging in schoolyard insults; they are expressing a technical frustration with the way generative AI features have been integrated into a legacy operating system. Analyzing the user feedback leading up to the Discord lockdown reveals a clear pattern of “quantity over quality” in the deployment of Copilot. Developers and power users have documented numerous instances where AI components were perceived as being forced into core OS functions like Notepad, File Explorer, and Task Manager, often at the expense of system latency and overall stability.

This quality gap is precisely what gave the “Microslop” nickname its viral potency, as it hit upon a verifiable truth regarding the current state of the software. If the AI integration were universally recognized as seamless, high-value, and technically flawless, the derogatory label would have failed to gain traction among the engineering community. However, because the term captured a widespread sentiment that the software was becoming bloated with unrefined, “sloppy” code that prioritizes corporate AI metrics over actual user utility, the attempt to ban the word felt like an attempt to ban the truth itself. For AI builders, this serves as a critical warning that one cannot moderate their way out of a fundamental quality problem. If a community begins to categorize a product’s output as “slop,” the correct response is not to update the server’s AutoMod settings to include the word on a prohibited list; the solution is to re-evaluate the product roadmap and address the technical regressions causing the friction.

Root Cause Analysis: The Failure of Brittle Automation in Community Governance

The technical root cause of the Discord meltdown can be traced back to the implementation of “naive” or “brittle” automation—a common pitfall for organizations that treat community management as a purely administrative task. Microsoft’s moderation team relied on a basic fixed-string match filter, which is the mos

Furthermore, the automation failed to account for context, which is the most vital component of any successful moderation strategy. The bot reportedly flagged every instance of the word “Microslop,” regardless of whether the user was using it as an insult, asking a question about the controversy, or providing constructive criticism. By labeling a corporate nickname with the same “inappropriate” tag usually reserved for hate speech or harassment, the automated system actively insulted the intelligence of the user base. This lack of nuance in the AI-driven moderation stack created a pressure cooker environment where every automated deletion was viewed as an act of corporate censorship. For AI builders, the lesson is that any automation deployed for community governance must be as sophisticated as the product it supports. Relying on 1990s-era keyword filtering to manage a 2026-era AI community is a recipe for disaster, as it signals a lack of technical effort that only further reinforces the “slop” narrative the organization is trying to escape.

The Strategic Shift: Moving Beyond Blunt Force Suppression

The failure of the “Microslop” ban highlights a critical strategic inflection point for AI builders who must navigate the increasingly volatile waters of developer communities. Relying on blunt-force suppression as a first-line defense against product criticism is a strategy rooted in legacy corporate communication models that are incompatible with the transparent, decentralized nature of modern technical hubs. When a tech giant attempts to scrub a derogatory term from its digital ecosystem, it effectively abdicates its role as a collaborator and assumes the role of an adversary. This shift in posture is particularly damaging in the context of generative AI, where the success of a platform like Copilot is heavily dependent on the feedback loops and integrations created by the very developers who feel alienated by such heavy-handed moderation. Instead of viewing these “slop” accusations as a nuisance to be silenced, sophisticated AI organizations should view them as high-fidelity data points indicating where the gap between marketing hype and functional utility has become too wide to ignore.

Consequently, the move toward resilient community management requires a transition from “policing” to “pivoting.” Analyzing the fallout from the March 2026 lockdown reveals that the most effective way to neutralize a pejorative nickname is to address the technical deficiencies that gave the name its power. For instance, if users are labeling an AI integration as “slop” due to high latency, resource bloat, or inconsistent output, the strategic response should involve a public-facing commitment to performance benchmarks and a transparent roadmap for optimization. By engaging with the substance of the criticism rather than the semantics of the label, a builder can naturally erode the legitimacy of the mockery. Microsoft’s decision to hide behind a locked Discord server suggests a lack of preparedness for the “friction” that inevitably accompanies the rollout of transformative technologies. To avoid this pitfall, builders must ensure that their community teams are empowered with technical context and the authority to translate community outrage into actionable product requirements, rather than being relegated to the role of digital janitors tasked with sweeping dissent under the rug.

Building Resilience: Lessons in Context-Aware Governance

For AI startups and established enterprises alike, the “Microslop” debacle provides a definitive masterclass in the necessity of context-aware governance. The primary technical takeaway is that community moderation in 2026 must be as intellectually rigorous as the models being developed. A sophisticated governance stack would utilize sentiment analysis and intent recognition to differentiate between a user engaging in harassment and a user expressing a legitimate, albeit sarcastically phrased, grievance. By failing to integrate these more nuanced AI capabilities into their own moderation tools, Microsoft inadvertently signaled a lack of confidence in the very technology they are asking the world to adopt. If an AI leader cannot trust its own systems to handle a Discord meme without resorting to a total server blackout, it becomes significantly harder to convince enterprise clients that the same technology is ready to handle mission-critical business logic or sensitive customer interactions.

Furthermore, building a resilient community requires a fundamental acceptance of the “ugly” side of product development. In the age of social media and rapid-fire developer feedback, mistakes will be memed, and failures will be christened with catchy, derogatory nicknames. Attempting to legislate these memes out of existence is a losing battle that only serves to accelerate the Streisand Effect. Instead, AI builders should focus on creating “high-trust environments” where users feel that their feedback—no matter how unpolished or “sloppy” it may be—is being ingested as a valuable resource. This involves maintaining open channels even during a PR crisis and resisting the urge to implement “emergency” filters that treat your most vocal users like hostile actors. By prioritizing stability, transparency, and technical excellence over brand hygiene, organizations can transform a potential “Microslop” moment into a demonstration of corporate maturity and a commitment to long-term product quality.

From Damage Control to Product Discipline: Reclaiming the Narrative

The ultimate fallout of the Microsoft Discord lockdown serves as a definitive case study in why AI builders must prioritize technical discipline over narrative control. When a corporation attempts to “engineer” a community’s vocabulary through restrictive automation, it inadvertently signals a lack of confidence in the underlying product’s ability to speak for itself. Analyzing the broader industry trends of 2026, it becomes clear that the “slop” label is not merely a social media trend but a technical critique of the current state of LLM integration. For a developer audience, the transition from “Microsoft” to “Microslop” in common parlance was a direct reaction to perceived regressions in software performance and the intrusion of non-essential AI telemetry into stable workflows. By focusing on the removal of the word rather than the remediation of the code, Microsoft missed a critical opportunity to demonstrate the “sophistication” that CEO Satya Nadella has publicly championed. Builders must realize that in a highly literate technical ecosystem, the only way to effectively kill a derogatory meme is to make it irrelevant through superior engineering and undeniable user value.

Furthermore, the “Microslop” incident underscores the necessity of a unified strategy between product engineering and community management. In many large-scale tech organizations, these departments operate in silos, leading to situations where a community manager implements a blunt-force keyword filter without realizing it contradicts the broader corporate message of AI-driven nuance and intelligence. This strategic misalignment is what allowed a minor moderation decision to balloon into a global PR crisis that dominated tech headlines for a week. To build a resilient AI brand, organizations must ensure that their automated governance tools are reflective of their core technological promises. If your product is marketed as an “intelligent companion,” your moderation bot cannot behave like a primitive 1990s-era blacklist. Moving forward, the industry must adopt a “feedback-first” architecture where automated tools are used to categorize and elevate user frustration to engineering teams, rather than acting as a digital firewall designed to protect executive sensibilities from the harsh reality of user sentiment.

Conclusion: The Lasting Legacy of the “Slop” Era

The March 2026 Discord lockdown will likely be remembered as the moment “Microslop” transitioned from a niche joke to a permanent fixture of the AI era’s vocabulary. Microsoft’s attempt to use automated moderation as a shield against criticism backfired because it ignored the fundamental law of the digital age: the more you try to hide a grievance, the more you validate its existence. For those of us building in the AI space, the lessons are clear and uncompromising. We must build with transparency, moderate with context, and never mistake a blunt-force keyword filter for a comprehensive community strategy. If we want our products to be associated with innovation rather than “slop,” we must earn that reputation through technical excellence and genuine engagement, not through the silent deletion of our critics’ messages. In the end, Microsoft didn’t just ban a word; they inadvertently launched a movement, proving that even the world’s most powerful tech companies remain vulnerable to the power of a well-timed, nine-letter meme and the undeniable force of the Streisand Effect.

Call to Action

If this breakdown helped you think a little clearer about the threats out there, don’t just click away. Subscribe for more no-nonsense security insights, drop a comment with your thoughts or questions, or reach out if there’s a topic you want me to tackle next. Stay sharp out there.

D. Bryan King

Sources

• PCMag: Microsoft Effort to Ban ‘Microslop’ on Copilot Discord Didn’t Go As Planned
• Windows Latest: Microsoft Locks Copilot Discord After Moderation Backlash
• Futurism: Microsoft Bans “Microslop” on Discord, Gets So Humiliated It Locks Server
• Gizmodo: Microsoft Bans Term ‘Microslop’ From Official Discord Server
• PC Gamer: Microsoft banned the word ‘Microslop’ in its Copilot Discord server
• It’s FOSS: Microsoft Locks Down Discord Server Over “Microslop” Posts
• Slashdot: Microsoft Bans ‘Microslop’ On Its Discord, Then Locks the Server
• Ground News: Microsoft Locks Down Discord Server After Microslop Ban Backfires
• Mysterium VPN: Microsoft Banned “Microslop” on Discord, Then Panicked
• Kotaku: Flood Of ‘Microslop’ Messages Forces Microsoft’s Official Copilot AI Discord Into Lockdown
• WinBuzzer: Microsoft Bans ‘Microslop’ on Discord, Locks Server After Backlash
• NIST: AI Risk Management Framework
• CISA: Secure by Design Principles for AI

Disclaimer:

The views and opinions expressed in this post are solely those of the author. The information provided is based on personal research, experience, and understanding of the subject matter at the time of writing. Readers should consult relevant experts or authorities for specific guidance related to their unique situations.

Related Posts

Rate this:

Asha Sharma has been named CEO of Microsoft Gaming, succeeding Phil Spencer. Here’s her background, role, and vision for Xbox’s future across console, cloud and subscriptions. https://english.mathrubhumi.com/technology/who-is-asha-sharma-the-indian-origin-executive-named-ceo-of-microsoft-gaming-x13tkc3b?utm_source=dlvr.it&utm_medium=mastodon #AshaSharma #MicrosoftGaming #Xbox #PhilSpencer #SatyaNadella

#PhilSpencer going out from #Xbox was coming since ages.

Xbox fucked up their game in 2013 and Phil was given a bad hand. He tried his best, but the Xbox he wanted is not the Xbox became today.

#SatyaNadella wants the numbers go up and the next people in line will do that if that means killing the brand in the process.

I trust #AshaSharma will transform Xbox into an anecdotic sticker logo.

#Videogames #Gaming #Games #Microsoft #Activision #Bethesda #Blizzard

via #Microsoft : Asha Sharma named EVP and CEO, Microsoft Gaming

https://ift.tt/YfFIPhH
#AshaSharma #MicrosoftGaming #EVP #CEO #Microsoft #GamingLeadership #Xbox #MattBooty #PhilSpencer #SatyaNadella #MicrosoftNews #GamingIndustry #GameDevelopment #GameStudios #XboxCommunity …

#Microsoft #Satyanadella #MrJellybean
#windows #abuse

@onghu

Is the cost of importing it form a closeby country with that option too much?

#Enshittification #LLM #AI #programming #OpenSource #technology #Lenovo #Linux #POSIX #SatyaNadella #microSoft #license #hardware #software #win64

@tragivictoria

Thank you for your reaction

It's in the linked video. Watch it again

#Enshittification #LLM #AI #programming #OpenSource #technology #Lenovo #Linux #POSIX #SatyaNadella #microSoft #license #hardware #software #win64

Lenovo
TIl about an interesting OS option by Lenovo, on their notebook computers. Logical yet interesting and expected

You get an *Open Source* OS by default from Lenovo. No more win64 as default

If you want closed source you have to **ask** for it and pay the _hefty premium_ that microSoft's microslop demands, for their LLM infected, malware like OS. Lenovo wants to sell it's notebooks for the best price possible if you want an OS, and microsoft does not meet those demands anymore (for a while)

Loss per unit USD47 with win64
Profit extra per unit USD89 with Open Source Linux OS. The decision is logical

https://www.youtube.com/watch?v=_fw4HsJpfa8

#Enshittification #LLM #AI #programming #OpenSource #technology #Lenovo #Linux #POSIX #SatyaNadella #microSoft #license #hardware #software #win64

Yesterday, Microsoft Word CVP praised his OpenClaw setup at home.
https://www.omarknows.ai/p/meet-lobster-my-personal-ai-assistant

Today, Microsoft CEO started following #OpenClaw on GitHub.
https://github.com/saztd?tab=following

Get ready for Microsoft OneClaw, to be announced by Build 2026.🦀

#Microsoft #SatyaNadella

Who could have predicted this?

#microsoft #ai #satyanadella

via #Microsoft : Updates in two of our core priorities

https://ift.tt/xyVzWFg
#NetNewArticle #UpdatesInTwoCorePriorities #Microsoft #Security #Quality #Engineering #SatyaNadella #HayeteGallot #CharlieBell #SecurityCopilot #Purview #AgentPlatform #SecureFutureInitiative #Quali…

In the last week or so, #Microsoft's CEO Satya Nadella announced that they were going to pull back from doing new feature work for #Windows for a bit, and focus on bug fixes and other quality-of-life improvements for users and administrators. Windows' already shaky reputation has taken a beating over the last year as it seems that every monthly rollup #patch, and many out-of-band #patches, introduce new problems at the same rate as they fix previous ones.

Is this giving you deja vu? It should. Remember a couple or three years ago, when the same guy announced that Microsoft was going to focus on security? They were in the middle of a long spell of brutal security holes found in all their products. Remember how they told their #engineers "If you have to choose between doing a feature and doing security, choose security"?

Remember how you never heard about that initiative again?

It's the same thing here. #PR garbage in service of a narrative that no, Windows' horrible security, usability, and #stability aren't actually that bad, so that MS can focus on their core competencies of buzzword promotion, stock market analyst manipulation, and monopoly abuse.

Perhaps someone in Microsoft management actually believes these refocusing efforts are genuine - but if you don't change the incentives, they won't actually take hold.

#PR #marketing #buzzword #MSWindows #SatyaNadella #security #WeveHeardOfIt #stability #crash #rollup #monopoly #MemoryHole

Satya Nadella has now published his first public GitHub repo: https://github.com/saztd/debatechamber

"Philosophical Debate Chamber - AI philosophers debate life's deepest questions"

Built with GitHub Copilot and vibes.✌️

No, I couldn't get the LLMs working on my machine.😅 Satya may have a newer Copilot CLI version running than me.

#Microsoft #GitHub #Copilot #SatyaNadella

UA: Не знаю що робиться в Майкрософті, але вони вже показують ширшій публіці чого їх так ненавидять. Що #СатьяНаделла скаже цього разу?

EN: I have no idea what's going on with #Microsoft but they has started to show to the broader audience why they are so hated. What #SatyaNadella is going to say this time?

Джерело/Source: https://nitter.net/gfodor/status/2014360679629848887#m

#windows #development #ai #windows11 #windows11update #віндовс #майкрософт

Microsoft plays catchup in AI race with OpenAI announcement

In a surprising strategic pivot, Microsoft is moving to diversify its AI portfolio beyond its primary partnership. Amidst scaling challenges and rising costs at OpenAI, the Redmond giant has announced a new series of "in-house" frontier models and a broader integration of open-source architectures.

#Microsoft #OpenAI #AIBusiness #TechNews #SatyaNadella #Innovation #Business #tech #technology

https://www.technology-news-channel.com/microsoft-plays-catchup-in-ai-race-with-openai-announcement/

🤯 Listen to Satya Nadella talk about the need for hospitals to pay for AI so they don't have to pay their doctors more money.

https://youtu.be/1co3zt3-r7I

Does he know he's completely gaslighting everyone when he speaks, or does he really think he's doing the world a favor?

He says everyone will get their agency back by using agents. Huh?

BigTech gets a cut of every last human (client) connected to all the agents built on the platforms burning up everyone's future on this planet for profit.

Uh, thanks dude 👍

#Microsoft #AI #SatyaNadella #Healthcare #Surveillance #CyberSecurity #Davos #Agents #Cloud #DataCenters #Crypto #ClimateChange