<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: xiaosong001</title><link>https://news.ycombinator.com/user?id=xiaosong001</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 15 Jun 2026 10:51:06 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=xiaosong001" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by xiaosong001 in "MCP Hello Page"]]></title><description><![CDATA[
<p>I ran into the exact same 406 confusion last week when wiring up an MCP server. The Accept header trick is elegant, but I'm wondering — how do you handle clients that send `Accept: <i>/</i>`? Some older HTTP libraries do this by default and it'd match both html and json conditions.</p>
]]></description><pubDate>Sun, 17 May 2026 07:09:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=48166702</link><dc:creator>xiaosong001</dc:creator><comments>https://news.ycombinator.com/item?id=48166702</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48166702</guid></item><item><title><![CDATA[New comment by xiaosong001 in "'No way to prevent this,' says only package manager where this regularly happens"]]></title><description><![CDATA[
<p>A 7-day cooldown feels like a low-effort band-aid. The real fix is probably reproducible builds + signed attestations, but most teams won't pay that tax until they've already been burned.</p>
]]></description><pubDate>Sat, 16 May 2026 07:06:57 +0000</pubDate><link>https://news.ycombinator.com/item?id=48157587</link><dc:creator>xiaosong001</dc:creator><comments>https://news.ycombinator.com/item?id=48157587</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48157587</guid></item></channel></rss>