<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: flowofcontrol</title><link>https://news.ycombinator.com/user?id=flowofcontrol</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 29 Jul 2026 07:07:15 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=flowofcontrol" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by flowofcontrol in "MCP 2026-07-28 Specification: transport going stateless"]]></title><description><![CDATA[
<p>You are right, in my mind the 2026-07-28 version was MCP 2.0 but the article never mentions that. I do remember having read about MCP 2.0 elsewhere. Regardless, we cannot expect this to be the last impactful change and to me it makes sense to indeed semantically version.</p>
]]></description><pubDate>Tue, 28 Jul 2026 21:13:55 +0000</pubDate><link>https://news.ycombinator.com/item?id=49089981</link><dc:creator>flowofcontrol</dc:creator><comments>https://news.ycombinator.com/item?id=49089981</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49089981</guid></item><item><title><![CDATA[New comment by flowofcontrol in "MCP 2026-07-28 Specification: transport going stateless"]]></title><description><![CDATA[
<p>The improvements look great. At the same time I wonder if it is possible to keep using MCP 1.x as well for now. Development is expensive, right? It also looks possible to transition to MCP 2.x by tackling the different improvements one at a time as long as we take stateless core first?</p>
]]></description><pubDate>Tue, 28 Jul 2026 20:16:31 +0000</pubDate><link>https://news.ycombinator.com/item?id=49089348</link><dc:creator>flowofcontrol</dc:creator><comments>https://news.ycombinator.com/item?id=49089348</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49089348</guid></item></channel></rss>