Live data from Hacker News

AWS Bedrock to require sharing data with Anthropic for Mythos and future models

news.ycombinator.com

171–180 of 274 posts

Re: AWS Bedrock to require sharing data with Anthropic for Mythos and future models

#171
It’s worth noting that Anthropic has made some very odd moves in the last few months in which Claude Code reviews your usage of it and penalizes you for mentions of some short strings that don’t even indicate TOS violations. And if they’re going to insist on retaining all data for 30 days for nebulously defined “safety”, then I’m not particularly interested in doing business with them.

Imagine if they interpret “safety” such that they scan for the string “com.openai” and, if found, ask an LLM to summarize your entire session and send it for human review?

Re: AWS Bedrock to require sharing data with Anthropic for Mythos and future models

#173
post #140
post #122

Earlier quoted context omitted.

> you trust them enough not to log your data prior to this, but not enough to trust their stated limits on how logged data will be used now It doesn't really matter how much you happen trust another party. In the regulatory world it only matters what contracts they will sign that guarantee their compliance. We do have those with AWS, we don't with Anthropic. If Anthropic physically captures the data, they just moved…

It will absolutely cause some non-trivial number of customers to shift their configs away from Anthropic.

It's worthwhile to remember that this is only true of Mythos/Fable and other future models of "similar or higher capability levels" (ant is treating this as a new tier of model above Opus). Anyone who's already been happy using Haiku/Sonnet/Opus on Bedrock will not be affected by this at all.

Re: AWS Bedrock to require sharing data with Anthropic for Mythos and future models

#174
post #111

This policy applies across all providers. Here is the warning in Cursor: https://i.redd.it/7sfyker2ya6h1.png Note that Anthropic has committed not to train models on logged data, so I don’t understand some of the concerns here. What exactly is your threat model? That Anthropic would train models contrary to their terms of service? That you trust them enough not to log your data prior to this, but not enough to trust…

Someone has never dealt with HIPAA laws and it shows.

Who out there is going to be feeding patient medical data to Mythos/Fable?

Re: AWS Bedrock to require sharing data with Anthropic for Mythos and future models

#175
post #81

Earlier quoted context omitted.

A model that opens the slightest gap for a leak would be unacceptable to the org I work for. We are very paranoid about losing vulnerable customers' data.

Anthropic has all the answers for that. You’ll go through some compliance exercises and classify them as a subprocessor of highest tier of data sensitivity.

There are a significant number of extremely large companies that are wholly interested in such a sub-processor. The tier of data sensitivity is irrelevant.

Almost all companies are content to engage with data sub-processors with respect to customer data or some form of PII.

But there are many that will absolutely not let their IP visit or reside on systems they do not control.

This is absolutely a deal breaker for a ton of organizations and it's not going to trigger industry wide adoption like other comments here suggest. Instead another provider will offer a more appetizing deal and they will win market share.

Re: AWS Bedrock to require sharing data with Anthropic for Mythos and future models

#176
post #127

Earlier quoted context omitted.

No, we are unhappy because there is no guarantee that my corporate documents wont be shared or trained on. We are already paying plus for using bedrock instead of the API version from Anthropic, so now there is no reason to use bedrock anymore. This whole thing about this model being too powerful to share is just the usual BS. Is an advanced model that dont have guardrails, just like the models that have been shared…

... but you were silent when they did it to consumers...

The consumers were paying for tokens with their data. If you pay for the tokens yourself the expectation is that your data doesn’t get trained on or used.

Re: AWS Bedrock to require sharing data with Anthropic for Mythos and future models

#177
post #85

The root of the problem is that AI-as-a-service is corked, because companies providing it have a hell of an incentive to use all that data to out-compete their competitors, and they can do so in secret. To say nothing of salivating law-enforcement who really, really wants to tap into it. I'm hoping there will be at some point open-source and affordable hardware that can run competent models.

It's all extremely dystopian and I don't see how things improve. The handful of megacorps that have access to the compute and troves of stolen IP to train their secret models on have no incentive to contribute back. They say their models are too dangerous for the public, so they can nerf the GA versions while allowing only their preferred megacorp or nation state partners access to the real secret good versions. We c…

Realistically, local/open weight models will always be limited in idiosyncratic world knowledge compared to the proprietary frontier. There's just very limited upside to releasing tens or hundreds of terabytes of open weights for something that literally can only run in very large AI data centers, and Fable/Mythos is near enough to that class. Smaller models can be smart in very real ways, but the extent to which those "smarts" can apply to real-world problems will be limited.

Re: AWS Bedrock to require sharing data with Anthropic for Mythos and future models

#178

Earlier quoted context omitted.

The Fable announcement page on the Anthropic site says this data sharing will be applied regardless of the sharing setting of the company account. https://www.anthropic.com/news/claude-fable-5-mythos-5#a-new... --- ## A new data retention policy Finally, we’re making a change to the way we handle business customer data for Fable 5, Mythos 5, and future models with similar or higher capability levels. We will require…

No it says sharing is required. If you don't change the setting on your account then you simply can't access Fable, its not like the setting is ignored. I just tried this on my account and it blocks API requests to Fable.

Interesting. When I tried switching to it yesterday from Opus 4.8 ("/model" command) it didn't complain, but I didn't actually send anything to it when I saw the cost was like 2x Opus 4.8. ie switched back

I'll try to remember to actually try it tomorrow and see what happens.

Re: AWS Bedrock to require sharing data with Anthropic for Mythos and future models

#179
post #152

Earlier quoted context omitted.

no, it's very much compatible with GDPR and other laws, as it clearly (enough, kinda) communicated 1. what data they keep/collect 2. what they do with it (and that there is a reason to have it) 3. with whom they share it 4. how long they keep it --- GDPR might require data minimalism, but that doesn't mean you can't keep "all" conversations/data. It just means you have to have a reason of why exactly need all of it (…

> how long they keep it AFAIR it is not clear, because they write it is "30 days, but ...": > After 30 days, the data is deleted automatically, except in the rare cases where it's part of a safety investigation or we're legally required to keep it. So you have a vague clause saying "when" and vague clause saying for "how long". If it will fly I would be surprised.

This is all pretty standard with GDPR.

Re: AWS Bedrock to require sharing data with Anthropic for Mythos and future models

#180
post #174

Earlier quoted context omitted.

Someone has never dealt with HIPAA laws and it shows.

Who out there is going to be feeding patient medical data to Mythos/Fable?

Whoever Anthropic can convince, to help them form a competitor to OpenEvidence, who already feed patient medical data into their systems.
Post reply on HN