Shane 🇺🇸 ㈯

742 posts

Shane 🇺🇸 ㈯ banner
Shane 🇺🇸 ㈯

Shane 🇺🇸 ㈯

@Shane0xM

Building @GreenfieldLabs // OSS AI · Agentic Coding · Applied AI · Enterprise

Katılım Kasım 2023
817 Takip Edilen250 Takipçiler
Shane 🇺🇸 ㈯
Shane 🇺🇸 ㈯@Shane0xM·
Anyone else using OpenCode dealing with this when you have to restart Ghostty or run system restart? I'm working on something to bolt onto my oc-session CLI to solve this for MacOS to start (github.com/Shane0xM/oc-se…) Right now it's a simple Rust crate for managing OC sessions globally (got tired of having to cd in and out of paths and search /sessions in each subpath for recent sessions so this v1 solved that) Ideal state would be a simple command that preserves all tabs, desktop views, and sessions instantly to cut down on setup time and eliminate headaches in the case of crashes
Shane 🇺🇸 ㈯ tweet media
English
0
0
0
21
@levelsio
@levelsio@levelsio·
If Claude Code keeps being slow like this while I pay $200/mo (and they don't let me pay more) They will essentially force me to leave to Codex and I don't want to But it's soooooo slooooooooooooowwwww
@levelsio tweet media
English
635
46
2.6K
263.3K
Loktar 🇺🇸
Loktar 🇺🇸@loktar00·
Random site created with Grok Heavy, used Imagine for videos and images. Those are the stars of the show for sure. One concern though is this did use 5% of my usage which resets May 31st. Grok CLI is REALLY nice though honestly, would be amazing to hook up local models.
English
14
1
66
7.1K
Shane 🇺🇸 ㈯
Shane 🇺🇸 ㈯@Shane0xM·
Official Anthropic response to my data export issue that has been resolved for over 4 weeks I give them credit for working on getting around to responses b/c that whole AI support system was terrible, but a simple log lookup would show when the export succeeded Also “large file” is literally less than 1GB combined for CC and Desktop exports Sure let me download 3 months at a time for 3+ years worth of data and combine it myself The entire stack is vibed to the brim
Shane 🇺🇸 ㈯ tweet media
English
0
0
0
40
Shane 🇺🇸 ㈯
Shane 🇺🇸 ㈯@Shane0xM·
Really solid write up and overall handling of the situation that unfolded This should clear up any bs that it was the fault of a vibed release or anything of the sort Statement the other day is alarming but this clearly was not the catalyst of what transpired That said there are a few great lessons in below thread and worth the read Particularly around the disaster recovery set up and process of bringing things back online
rob@rwitoff

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
0
1
1
35
Shane 🇺🇸 ㈯
Shane 🇺🇸 ㈯@Shane0xM·
CLI > MCP I get the auth selling point but damn agents always work better with well documented Go/Rust CLIs Every time I veer off into using MCP I regret every second wasted
English
0
0
0
30
Cointelegraph
Cointelegraph@Cointelegraph·
🚨 LATEST: Trump-linked WLFI and WorldClaw launch WorldRouter to offer access to 300+ AI models via a single account, where agents can process payments in USD1. It adds locking $WLFI tokens will unlock additional features tied to the future of AI.
Cointelegraph tweet mediaCointelegraph tweet media
English
64
64
393
39K
Shane 🇺🇸 ㈯
Shane 🇺🇸 ㈯@Shane0xM·
Literally have no words Disgusted is an understatement
WLFI@worldlibertyfi

@WorldClawAI is expanding access to AI and $WLFI plays a key role in the ecosystem. Users can access 300+ models with WorldRouter, and agents can facilitate payments in USD1 on @BNBCHAIN and @solana to support task execution. Locking $WLFI tokens can provide access to additional features and functionality related to the future of AI. Subject to applicable terms and conditions.

English
0
0
0
39
Shane 🇺🇸 ㈯
Shane 🇺🇸 ㈯@Shane0xM·
“Non-technical teams shipping production code” That’s terrifying coming from Coinbase. Vibe coding is the security threat, not frontier models exploiting years of human-made vulnerabilities ripe for the picking. The next phase of agent-on-agent exploits is going to be 10x worse thanks to stupidity like this. When it hits, the engineers solving these problems will have been cut under expectations that non-technical folks can ship to prod reliably. If you thought today’s dormant vulnerabilities were bad, just wait until the ramifications of this shake out.
Brian Armstrong@brian_armstrong

This is an email I sent earlier today to all employees at Coinbase: Team, Today I’ve made the difficult decision to reduce the size of Coinbase by ~14%. I want to walk you through why we're doing this now, what it means for those affected, and how this positions us for the future. Why now Two forces are converging at the same time. We need to be front footed to respond to both. First, the market. Coinbase is well-capitalized, has diversified revenue streams, and is well-positioned to weather any storm. Crypto is also on the verge of the next wave of adoption, with stablecoins, prediction markets, tokenization, and more taking off. However, our business is still volatile from quarter to quarter. While we've managed through that cyclicality many times before and come out stronger on the other side, we’re currently in a down market and need to adjust our cost structure now so that we emerge from this period leaner, faster, and more efficient for our next phase of growth. Second, AI is changing how we work. Over the past year, I’ve watched engineers use AI to ship in days what used to take a team weeks. Non-technical teams are now shipping production code and many of our workflows are being automated. The pace of what's possible with a small, focused team has changed dramatically, and it's accelerating every day. All of this has led us to an inflection point, not just for Coinbase, but for every company. The biggest risk now is not taking action. We are adjusting early and deliberately to rebuild Coinbase to be lean, fast, and AI-native. We need to return to the speed and focus of our startup founding, with AI at our core. What this means To get there, we are not just reducing headcount and cutting costs, we’re fundamentally changing how we operate: rebuilding Coinbase as an intelligence, with humans around the edge aligning it. What does this mean in practice? - Fewer layers, faster decisions: We are flattening our org structure to 5 layers max below CEO/COO. Layers slow things down and create coordination tax. The future is small, high context teams that can move quickly. Leaders will own much more, with as many as 15+ direct reports. Fewer layers also means a leaner cost structure that is built to perform through all market cycles. - No pure managers: Every leader at Coinbase must also be a strong and active individual contributor. Managers should be like player-coaches, getting their hands dirty alongside their teams. - AI-native pods: We’ll be concentrating around AI-native talent who can manage fleets of agents to drive outsized impact. We’ll also be experimenting with reduced pod sizes, including “one person teams” with engineers, designers, and product managers all in one role. In short: AI is bringing a profound shift in how companies operate, and we’re reshaping Coinbase to lead in this new era. This is a new way of working, and we need to leverage AI across every facet of our jobs. To those who are affected I know there are real people behind these decisions — talented colleagues who have poured themselves into this company and our mission. To those of you who will be leaving: thank you. You’ve helped build Coinbase into what it is today, and I am sincerely grateful for everything you've done. All impacted team members will receive an email to their personal account in the next hour with more information, and an invitation to meet with an HRBP and a senior leader in your organization. Coinbase system access has been removed today. I know this feels sudden and harsh, but it is the only responsible choice given our duty to protect customer information. To those affected, we will be providing a comprehensive package to support you through this transition. US employees will receive a minimum of 16 weeks base pay (plus 2 weeks per year worked), their next equity vest, and 6 months of COBRA. Employees on a work visa will get extra transition support. Those outside of the US will receive similar support, based on local factors and subject to any consultation requirements. Coinbase prides itself on talent density. Our employees are among the most talented people in the world, and I have no doubt that your skills and experience will be highly sought after as you pursue your next chapters. How we move forward To the team that is staying, I know this is a difficult day. We’re saying goodbye to colleagues and friends you've been in the trenches with. But here’s what I want you to know as we move forward together: Over the past 13 years, we have weathered four crypto winters, gone public, and built the most trusted platform in our industry. We’ve made it this far by making hard decisions and by always staying focused on our mission. This time will be no different – nothing has changed about the long term outlook of our company or industry. And most importantly, our mission has never been more important for the world. Increasing economic freedom requires a new financial system, and we’re building it. The Coinbase that emerges from this will be more capable than ever to achieve our mission. Brian

English
2
0
0
51
Shane 🇺🇸 ㈯
Shane 🇺🇸 ㈯@Shane0xM·
Breakthroughs in attention are about to start dominating frontier research 52x faster than FlashAttention at 1M tokens is insane If they can get close to mid tier performance with this things are about to get super interesting
Alexander Whedon@alex_whedon

Introducing SubQ - a major breakthrough in LLM intelligence. It is the first model built on a fully sub-quadratic sparse-attention architecture (SSA), And the first frontier model with a 12 million token context window which is: - 52x faster than FlashAttention at 1MM tokens - Less than 5% the cost of Opus Transformer-based LLMs waste compute by processing every possible relationship between words (standard attention). Only a small fraction actually matter. @subquadratic finds and focuses only on the ones that do. That's nearly 1,000x less compute and a new way for LLMs to scale.

English
0
0
0
41
Shane 🇺🇸 ㈯
Shane 🇺🇸 ㈯@Shane0xM·
Such a joke… Looks like Dario finally got his way Open source AI will not slow down or be forced to abide with these pre-release standards and the gap will close faster than we thought Idc what intelligence I lose access to I will never use this PoS company again
Andrew Curran@AndrewCurran_

The Trump administration has informed Anthropic, Google and OpenAI that they are discussing the creation of new AI oversight procedures that would potentially require new AI models to pass a safety review before being cleared for release. Mythos has changed things.

English
0
0
1
54
Shane 🇺🇸 ㈯
Shane 🇺🇸 ㈯@Shane0xM·
@loktar00 Same but then I think about all the VRAM on that one card I’m not ready to pull it yet either but stacking 3-4 of those pretty much locks in frontier models for the next 10 years
English
0
0
3
57
Loktar 🇺🇸
Loktar 🇺🇸@loktar00·
@Shane0xM Bah yeah I imagine I'd feel the same way, the only thing tempting is the price, I just can't bring myself to drop 10k on a card yet
English
1
0
4
179
Loktar 🇺🇸
Loktar 🇺🇸@loktar00·
Tomorrow heading to Microcenter... have the urge to buy something, lol I know I shouldn't get a Spark but I'm tempted... there's also a few RTX 5000 72gb's in stock I'm hoping I just stay strong and come home with a bottle of Ballz or or a mousepad instead 😂
English
18
0
59
3.9K
Thomas Trimoreau
Thomas Trimoreau@TTrimoreau·
Is Claude Opus really the best model for coding right now ?
English
141
1
96
12K
Jim Cramer
Jim Cramer@jimcramer·
The bottom line: they are short compute and Codex is on fire...
English
153
67
1.9K
617K
Bhavy☄️
Bhavy☄️@Bhavani_00007·
Software Engineers what's your plan B if AI replaces you?
Bhavy☄️ tweet media
English
100
1
102
10.7K
Sam Altman
Sam Altman@sama·
wow y'all love 5.5 we should think of something nice to do to celebrate!
English
2.6K
285
11.1K
779.9K