Google limits Meta's use of its Gemini AI models

This seems to be a bit of a misleading headline.

In the current climate limiting someone's use of AI might be expected to be about restricting access or restricting what someone can do with it, but the story here ostensibly seems to be about capacity constraints, not any limitation on what models or capabilities Google is giving Meta access to.

	▲	londons_explore 44 minutes ago \| parent [-]
		These kind of limits happen all the time for big clients. Cloud services like to present the illusion of an infinite amount of compute available at a fixed price per unit, but the reality is if you try to use too much of any service you'll find you have a quota and requests to increase it will fall on deaf ears if the provider doesn't have more of that resource. Too much of my working life has been spent shoehorning services into less space/compute/ram/spindles or migrations to other data centers to solve such issues.

▲

symisc_devel an hour ago | parent | prev | next [-]

I do believe this will be the norm from now on to get access to top frontier model. Computing capacity plus state restrictions plus KYC will be imposed to organisations to get access, individuals will be served last on the queue with degraded performance. Once the Chinese models catch up, nobody (at least individuals) will turn back again to frontier labs.

	▲	mden 28 minutes ago \| parent [-]
		This seems less about frontier models and restriction and more just lack of compute capacity to meet demand. This has always been an issue for large clients running on cloud, though not to this extent.

▲

HarHarVeryFunny an hour ago | parent | prev | next [-]

It's interesting that Meta is heavily using Google's models (as opposed to Anthropic or OpenAI) given that they are not SOTA for coding. I wonder if this for some strategic/competitive reason, or maybe for cost saving?

▲

dofm 10 minutes ago | parent | next [-]

I would imagine there are many situations within Meta's applications where relatively small models can do a good job — sentiment analysis, abusive language detection, characterising users based on their posts, summarising a user's complaint so it can be ignored more efficiently, assessing whether ads are likely to be fraudulent so they can be run more often, etc.

▲

sarjann 42 minutes ago | parent | prev [-]

Google tends to be very good at vision and smaller/ edge

	▲	HarHarVeryFunny 23 minutes ago \| parent [-]
		Hmm ... I was assuming they were using these models for development, but I wonder if any of it might be for production instead - perhaps using vision models to analyze posted content? That would certainly be massive scale, but I'd have thought that scale would require them to be running in their own datacenters.

▲

mark_l_watson 28 minutes ago | parent | prev | next [-]

Misleading title on HN but an interesting article, a reminder of why the hyper scalers are investing heavily in infrastructure.

That said, I expect much of the AI bubble to pop. Google Gemini with Antigravity is a good product, as is a Claude Code subscription but I have switched to using DeepSeek v4 Pro with the Claude Code harness and DeepSeek v4 Flash with the OpenCode harness (when I am not using local models with little-coder/pi) and at least for the foreseeable future I don’t think I am going back. Fast APIs at low cost trumps having to spend a little more time to get the same quality of results.

▲

Zambyte an hour ago | parent | prev [-]

Facebook does seem to be falling behind. Does anyone here use Llama over more recent options for any technical reasons?

	▲	khurs an hour ago \| parent \| next [-]
		if you use this as a rough gauge: https://openrouter.ai/models?order=top-weekly Llama Meta 70b is 50th or so down the list of popular models. It has 24.1b tokens used in 7 days vs the top models that have trillions or hundreds of billions of tokens. So practically dead!
	▲	dataminded 41 minutes ago \| parent \| prev [-]
		Meta's latest model is Spark Muse and not available outside of its products. https://ai.meta.com/blog/introducing-muse-spark-msl/