Sabitlenmiş Tweet
Jesus Alvarez
232 posts

Jesus Alvarez
@Chuyqa
Quant. Previously Dev, Architect, Manager for Watson Integration @ IBM. "Back in my day ML had a lot more spark, yarn, xgb."
San Jose, CA Katılım Ağustos 2012
242 Takip Edilen118 Takipçiler

@deepfates Context window starts at 5am and lasts 2M tokens before sleep compaction (each coffee extends it by 100k).
My prompter left behind some 10 commandments in a .md file, but after a few thousand epochs the other agents aren't following it to spec.
English

@TheMadPsyntist @rwitoff @coinbase IOTX data finally flowing.. But still a handful of broken pairs Monday at 2pm.. *cough* ICP-USDT is still fucked.

English

Yesterday @coinbase experienced a multi-hour service disruption affecting trading, exchange access, and balance updates. Here's our initial read from Coinbase engineering on what happened, how we recovered, and what we're addressing.
At approximately 23:50 UTC on 2026-05-07, our monitoring detected cascading quote failures from internal services that triggered multiple Sev1 incidents that engineering immediately began investigating. Customer-facing impacts included spot trading, Prime, International and derivative exchanges.
Root cause: a thermal event (cooling system failure) inside a subset of racks within a single building in AWS us-east-1. We run a primary replica of our exchange infrastructure in a single zone, consistent with industry standards to reduce latency. To prepare for failures like this, we maintain a distributed standby, but during this incident, failures in the primary zone that were designed to be isolated were not, extending the duration of our outage.
The failure cascaded down two paths:
1. Multiple hardware components beneath our exchange’s matching engine failed, requiring recovery and failover
2. Distributed Kafka clusters that manage messaging across Coinbase systems failed to remain available, also requiring partition failovers to new hardware brokers with many TiBs of data
After isolating the incident: automated tooling drained ~10 Kubernetes clusters worth of related workloads out of the affected zone to stabilize internal services. Most services were back to normal within ~30 minutes of diagnosis. The two things we couldn't automatically drain: the exchange (dedicated hardware and storage) and Kafka (managed service that was designed to be resilient to this, with unique problems).
The exchange matching engine is the core system responsible for processing orders and maintaining order books. It is a distributed cluster and requires quorum to safely elect a leader and continue processing trading activity. During the incident, infrastructure-level constraints in the affected datacenter left only a subset of nodes healthy, preventing the cluster from reaching quorum. As a result, trading across Retail, Advanced, and Institutional exchanges were blocked.
Recovery required our oncall and engineering teams to execute our disaster recovery plan, restore quorum safely, and validate system health under constrained infrastructure conditions. The team built, tested, deployed, and validated the fix while continuing to manage the broader incident.
Kafka recovery was a much larger scale operation. Our primary managed Kafka partitions process many terabytes of data daily and are designed with resiliency guarantees for uninterrupted operation during a datacenter failure just like this. In this case, those guarantees failed and required manual recovery.
We again relied on disaster recovery procedures to recover stuck partitions onto new hardware (brokers) that enabled us to safely bring x-service messaging back online across Coinbase. During the lag, customers saw delayed balance streams which resolved automatically once replication caught up. No data lost.
Once the engine came back up as part of our standard runbooks, we re-opened markets carefully: all products to cancel-only mode first, audited product states, then moved all markets to auction mode, before restoring trading on Coinbase Exchange.
What went right: the team. Incident response across the company came together within minutes, followed well-rehearsed playbooks and used secure automation tooling to recover all services. We have a strong, senior team at Coinbase that worked through rare failure modes to recover all services.
To our customers: losing access to your account, even temporarily, is unacceptable. We know that. We're sorry, and we’ll publish a full root cause analysis in the coming weeks 🙏
English


300,000 AI builders have already added their hardware to HF to instantly see what model they can run locally.
To do so, go to huggingface.co/settings/local… and add your hardware specs.
You can even show off publicly by adding it to your HF profile!
Let's go local AI!

English

@tmuxvim It's been incredibly annoying. It feels like it was trained on youtube videos with a surprised open mouth.

English

@zvlasov > MCP Is dead
Indeed, Clean API Docs > MCP.
Funny to kraken, okx, and unusualwhales all release an MCP this week just as the ai labs phasing away from it
blog.kraken.com/news/industry-…
okx.com/learn/agent-tr…
English

1Q 2026 vibe check. Everyone is:
- battling with openClaws and what tasks to give it
- building in public: “$0 → $1m ARR vibecoding”
- voice → text or → code
- web3 died. But agentic-native web rising. CLIs & APIs for agents. MCPs not cool anymore
- agentic ecommerce, x402
- crypto wallet apps slowly turning into neo-banks. Now offering yield on deposits + crypto cards
- prediction markets reaching retail like memecoins wanted to but failed
- gambling every possible asset on hyperliquid. Running out of things to tokenize
- clipping
- injecting peptides
- "receptor resetting and modulating drugs aren't drugs!"
- not drinking alcohol or smoking sigs, but using weed, nic pouches, vapes.
- tired of winning
English

@abacaj "Ran it for 1 day and prevented it from creating a tax nightmare for me of transactions because some molt told it to create a wallet"
or
"Ran it for 1 day and it didnt nuke anything important in my google drive"
English

@Polymarket 1.6 Million Printed books in the Vatican.
80,000 manuscripts.
521 million pages × 300 words/page ≈1.56 × 10¹¹ words x 1.3 tok/word ≈200B tokens.
x (1/30 tok/param) ~ 7B parameters.
The Vatican should drop their own 7B Model this year.
English

@_fluxfeeds @grok How does this compare with the largest drone shows put on by the US companies such as Sky Elements
English

@imnotanoob1 @Gemini @erickuhn19 @cameron @tyler When does this go live?
Both of these still only show ethereum as a network..
api.gemini.com/v1/network/USDC
api.gemini.com/v1/network/ETH

English

@Gemini now supports multichain deposits & withdrawals 🚀
Deposit on one network, withdraw on another — more flexibility, better onchain experience.
Here’s how we did it: gemini.com/blog/how-gemin…
Thanks @erickuhn19, @cameron, @tyler for trusting me with this! Onwards 🚀
English

@__tinygrad__ @grok For OpenBLAS, cuBLAS, and rocBLAS, is there no way to avoid the intermediate deepcopy/materialization?
English

Makeover on the new @Gemini app upgrade!!! 🔥
Andrew Fuller@andrewfullerxyz
We just dropped a major Gemini app upgrade: 🟠 Mars theme (pairs perfectly with your Bitcoin-orange Gemini Credit Card) 📊 Portfolio front & center + quick Privacy Mode toggle 📈 Live-updating charts with a fresh new design ⚡️ New Quick Action Button to easily trade or transfer from any tab And even more improvements are coming soon! Update now and tell us what you think!
English

@jeremyphoward @__tinygrad__ This seems like it would prevent Hotz from opening issues against their github as he works on getting MLPerf running... But his issues have saved hundreds if not 1000s of debugging hours.
English

@__tinygrad__ If you get AMD on MLPerf, wouldn't they want as many people as possible to know about it? And wouldn't they love getting lots of help to get there from open source contributors? What is confidentiality getting them?!?
English

@WarMonitors A symbol that their women are free enough to show their hair... Looks a bit ghostly with the white, but damn thats great to see.
English

Going to start asking for GPT history summaries instead of resumes soon..
> you're optimizing async Python pipelines, tuning covered call strategies, and benchmarking Flask vs FastAPI like it's Formula 1 qualifying. You’ve got Grafana dashboards lighting up like NORAD on Christmas Eve, and you debug latency with the precision of a neurosurgeon

English























