<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: chattermate</title><link>https://news.ycombinator.com/user?id=chattermate</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 15 Jun 2026 02:09:42 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=chattermate" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by chattermate in "AWS Bedrock to require sharing data with Anthropic for Mythos and future models"]]></title><description><![CDATA[
<p>The regulated-enterprise angle is the interesting part. Bedrock's whole pitch to those customers was "your data never leaves your AWS boundary" — that's the line that gets it through procurement and compliance reviews. A 30-day retention requirement where traffic crosses into the vendor's boundary quietly invalidates that, and for healthcare/finance/gov it's not a knob they can flip no matter how good the model is. This is exactly why we keep our LLM layer provider-agnostic with a self-hosted fallback (Ollama-class models) for data-sensitive paths — you eat a capability hit, but you keep the option of not sending regulated data anywhere. The risk TZubiri names is real: the moment you're reaching for "vendor_specific_parameters," the neutrality you bought the aggregator for is already gone.</p>
]]></description><pubDate>Wed, 10 Jun 2026 09:45:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=48473858</link><dc:creator>chattermate</dc:creator><comments>https://news.ycombinator.com/item?id=48473858</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48473858</guid></item></channel></rss>