
Centralism Vs Decentralisation 🤝 $BTC, obviously 🦾 Slave-State Resistant 🕊️🕊️🕊️@WhiteWhaleDefi No Financial Advice
Joined November 2021
- Tweets8.7K
- Following1.1K
- Followers5.1K
- Likes33.4K
Replying to @LunaVShape @0xdimix
A 5-10T param model at 4-bit quantization needs ~2.5-5 TB VRAM for weights alone (roughly 0.5 GB per billion params). Long-context KV cache adds hundreds of GB more.
Current best home rigs (multi-GPU or high unified memory) top out in the low hundreds of GB effective. Not practical yet for smooth inference.
Moore's Law (~2x density every ~2 years) points to 10-15+ years for consumer hardware to handle this scale comfortably, though better quantization, MoE sparsity, offloading, and new memory tech could make usable local runs viable sooner.
AveChristusRex retweeted
He sold his Bugatti to build a Church (and a university, and a small town.)
Tom Monaghan founded Domino’s Pizza and became a billionaire. He bought yachts, private jets, and the Detroit Tigers.
Then he read C.S. Lewis and had a massive reversion to his Catholic faith. He took a "millionaire's vow of poverty," sold the Tigers, sold his fleet of classic cars (including a $8M Bugatti), and gave away his fortune.
He used the money to build a Catholic university (Ave Maria) and a massive Church in Florida.
He proved that you can serve God or Money, but not both. But he also proved money is not evil, and as any tool can be used for good in the right hands.
do you understand what just happened to your computer..
Google Chrome secretly downloaded a 4GB AI model onto your device. Without asking.. Without telling you..
It's called weights.bin. It lives deep in your system folders. It powers Gemini Nano - Google's on-device AI.
And if you delete it? Chrome re-downloads it automatically. Like nothing happened.
Just Google deciding your hard drive is their storage unit.
At 1 billion Chrome users - that's 4 BILLION gigabytes of data pushed silently across the internet.
The carbon footprint alone equals tens of thousands of cars running for a year.
Check your disk right now:
📁 %LOCALAPPDATA%\Google\Chrome\User Data\OptGuideOnDeviceModel
To stop it: chrome://flags → disable Optimization Guide On Device Model → restart Chrome → delete the folder.
Reshare so people know what's sitting on their computers.
Google Chrome is quietly downloading a roughly 4 GB AI model to many users’ computers without clear upfront consent.
The file, called weights.bin, is part of Google’s Gemini Nano on-device language model and lands in the browser’s user data folder under OptGuideOnDeviceModel.
It powers built-in AI tools such as “Help me write,” smarter tab suggestions, on-device scam detection, and page summarization. The download triggers automatically for devices meeting minimum hardware requirements, and Chrome often replaces the files if deleted.
While the model processes data locally, installation happens in the background with minimal notification.
The scale is noteworthy. Hundreds of millions or billions of installations add up to thousands of tonnes of carbon emissions globally from data transfer, even though each is a one-time event.
To prevent or remove it, go to chrome://flags, disable the entries for the optimization guide on-device model and Prompt API, restart the browser, and manually delete the folder.
ANTHROPIC ACABA DE ARREGLAR UNO DE LOS MAYORES PROBLEMAS DE CLAUDE
Los límites de uso.
Después de meses de usuarios quejándose de quedarse sin mensajes en Claude, Anthropic acaba de cerrar un acuerdo con SpaceX para conseguir más capacidad de compute.
Y los cambios llegan hoy:
→ Límites de Claude Code duplicados para Pro, Max y Team
→ Eliminado el throttling en horas punta
→ Mucho más límite para la API de Opus
→ +300 MW extra de capacidad desde Colossus 1
Había gente pagando $200/mes y agotando el límite en menos de una hora.
Ese era probablemente el mayor punto débil de Claude frente a OpenAI.
Ahora Anthropic está recurriendo a infraestructura de SpaceX para intentar seguir el ritmo de la demanda.
We’ve agreed to a partnership with @SpaceX that will substantially increase our compute capacity.
This, along with our other recent compute deals, means that we’ve been able to increase our usage limits for Claude Code and the Claude API.










