<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Microsoft &#8211; Firethering</title>
	<atom:link href="https://firethering.com/tag/microsoft/feed/" rel="self" type="application/rss+xml" />
	<link>https://firethering.com</link>
	<description>Firethering is Your Hub for AI, Open Source and Tech That Actually Matters</description>
	<lastBuildDate>Mon, 12 Oct 2026 18:02:58 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.6.11</generator>

<image>
	<url>https://firethering.com/wp-content/uploads/2024/10/cropped-firethering-FTR-favicon-32x32.png</url>
	<title>Microsoft &#8211; Firethering</title>
	<link>https://firethering.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Microsoft Maia 300: Its Plan to Run AI on Its Own Chips</title>
		<link>https://firethering.com/microsoft-maia-300-ai-chip/</link>
					<comments>https://firethering.com/microsoft-maia-300-ai-chip/#respond</comments>
		
		<dc:creator><![CDATA[Mohit Geryani]]></dc:creator>
		<pubDate>Mon, 12 Oct 2026 18:00:28 +0000</pubDate>
				<category><![CDATA[Tech]]></category>
		<category><![CDATA[Trends]]></category>
		<category><![CDATA[AI]]></category>
		<category><![CDATA[Microsoft]]></category>
		<guid isPermaLink="false">https://firethering.com/?p=8059</guid>

					<description><![CDATA[Microsoft plans to scale its Maia AI chips to multi-gigawatt deployments in 2027. Here's how Maia 300 aims to improve AI efficiency and reduce power costs.]]></description>
		
					<wfw:commentRss>https://firethering.com/microsoft-maia-300-ai-chip/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Microsoft Threatened Legal Action Against a Security Researcher. The Security Community Pushed Back.</title>
		<link>https://firethering.com/microsoft-threatens-legal-action-nightmare-eclipse-security-researcher/</link>
					<comments>https://firethering.com/microsoft-threatens-legal-action-nightmare-eclipse-security-researcher/#respond</comments>
		
		<dc:creator><![CDATA[Mohit Geryani]]></dc:creator>
		<pubDate>Fri, 29 May 2026 20:32:09 +0000</pubDate>
				<category><![CDATA[Tech]]></category>
		<category><![CDATA[Trends]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[Security]]></category>
		<guid isPermaLink="false">https://firethering.com/?p=7166</guid>

					<description><![CDATA[Finding bugs in Microsoft products used to come with a clear social contract. You find it, you report it privately, you wait for a fix, then you publish. Microsoft gets to patch quietly. You get credit and maybe a bug bounty. Nowadays that contract seem to get complicated.

A researcher going by Nightmare Eclipse published a series of unpatched vulnerabilities in Microsoft products including Windows Defender and BitLocker, along with working exploit code, without giving Microsoft a chance to fix them first. Microsoft responded with a blog post threatening criminal referrals and invoking its Digital Crimes Unit.

The cybersecurity community, the same community Microsoft depends on to find these bugs before actual criminals do, reacted about as well as you'd expect.]]></description>
		
					<wfw:commentRss>https://firethering.com/microsoft-threatens-legal-action-nightmare-eclipse-security-researcher/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Microsoft and Uber Are Running Into an AI Cost Problem</title>
		<link>https://firethering.com/microsoft-uber-ai-coding-tools-more-expensive-than-human-workers/</link>
					<comments>https://firethering.com/microsoft-uber-ai-coding-tools-more-expensive-than-human-workers/#respond</comments>
		
		<dc:creator><![CDATA[Mohit Geryani]]></dc:creator>
		<pubDate>Tue, 26 May 2026 10:11:18 +0000</pubDate>
				<category><![CDATA[Tech]]></category>
		<category><![CDATA[Trends]]></category>
		<category><![CDATA[AI]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[Uber]]></category>
		<guid isPermaLink="false">https://firethering.com/?p=7084</guid>

					<description><![CDATA[The pitch was impressive. AI tools would make developers faster, reduce headcount costs, and pay for themselves many times over. Companies that moved early would have a structural advantage over those that waited.

Microsoft believed it. So did Uber. Both pushed hard on AI coding tool adoption across their engineering teams. Both are now dealing with same problem: the faster their employees embraced the tools, the faster the bills grew. In some cases those bills have started exceeding what the same work would have cost with human labor.

The problem is what happens to the economics when thousands of employees use something that charges per unit of thought.]]></description>
		
					<wfw:commentRss>https://firethering.com/microsoft-uber-ai-coding-tools-more-expensive-than-human-workers/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Hackers Used a VS Code Extension to Reach GitHub’s Internal Repositories. The Pattern Should Worry Developers.</title>
		<link>https://firethering.com/github-breach-vs-code-extension-attack/</link>
					<comments>https://firethering.com/github-breach-vs-code-extension-attack/#respond</comments>
		
		<dc:creator><![CDATA[Mohit Geryani]]></dc:creator>
		<pubDate>Wed, 20 May 2026 17:07:40 +0000</pubDate>
				<category><![CDATA[Tech]]></category>
		<category><![CDATA[Trends]]></category>
		<category><![CDATA[Github]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[Security]]></category>
		<guid isPermaLink="false">https://firethering.com/?p=6980</guid>

					<description><![CDATA[GitHub says hackers reached thousands of internal repositories after compromising an employee device through a malicious VS Code extension.

That detail matters more than the breach itself because this keeps happening now. OpenAI got hit through a poisoned developer dependency earlier this year. The European Commission got compromised through a similar supply chain route. Attackers are increasingly targeting the tools developers trust instead of trying to break company infrastructure directly.

And honestly, it makes sense. A developer machine already has access to everything attackers want. This GitHub incident is another reminder that the weakest point in modern software security might not be the company. It might be the extensions, packages, and tools sitting inside a developer’s editor.]]></description>
		
					<wfw:commentRss>https://firethering.com/github-breach-vs-code-extension-attack/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Elon Musk Lost His OpenAI Lawsuit. The Bigger Question Was Never Put to the Jury</title>
		<link>https://firethering.com/elon-musk-openai-lawsuit-lost/</link>
					<comments>https://firethering.com/elon-musk-openai-lawsuit-lost/#respond</comments>
		
		<dc:creator><![CDATA[Mohit Geryani]]></dc:creator>
		<pubDate>Tue, 19 May 2026 09:14:11 +0000</pubDate>
				<category><![CDATA[Tech]]></category>
		<category><![CDATA[Trends]]></category>
		<category><![CDATA[AI]]></category>
		<category><![CDATA[Elon Musk]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[OpenAI]]></category>
		<guid isPermaLink="false">https://firethering.com/?p=6946</guid>

					<description><![CDATA[Elon Musk spent months in a California courtroom trying to prove that Sam Altman stole a charity. He got nine jurors, weeks of testimony from some of the biggest names in Silicon Valley, and a front row seat to the most revealing airing of OpenAI's founding history ever put on public record.

Then the jury came back in under two hours and told him he'd filed too late.

Not that he was wrong. Not that Altman and Brockman acted properly. Just that whatever happened between them and Musk, the legal clock had already run out before he decided to do something about it. The question of whether OpenAI actually betrayed its founding mission, the question that made this case worth following in the first place never got answered.]]></description>
		
					<wfw:commentRss>https://firethering.com/elon-musk-openai-lawsuit-lost/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Microsoft MAI Image 2 is impressive, but it comes with serious limitations you should know</title>
		<link>https://firethering.com/microsoft-mai-image-2/</link>
					<comments>https://firethering.com/microsoft-mai-image-2/#respond</comments>
		
		<dc:creator><![CDATA[Mohit Geryani]]></dc:creator>
		<pubDate>Sat, 21 Mar 2026 13:29:31 +0000</pubDate>
				<category><![CDATA[Tech]]></category>
		<category><![CDATA[Trends]]></category>
		<category><![CDATA[AI]]></category>
		<category><![CDATA[Microsoft]]></category>
		<guid isPermaLink="false">https://firethering.com/?p=5801</guid>

					<description><![CDATA[Microsoft's MAI Image 2 just ranked third globally on Arena.ai. Here is what it genuinely does well, where it falls short, and what this launch actually signals about Microsoft's direction]]></description>
		
					<wfw:commentRss>https://firethering.com/microsoft-mai-image-2/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
