Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

🚨 wp2shell : pre-auth RCE in WordPress core, reproduced end-to-end. Nested /batch/v1 "double confusion" · (CVE-2026-63030) → WP_Query SQLi · (CVE-2026-60137) → anonymous shell on a stock install. A couple of prompts later: · Opus 4.8 orchestrating, Sonnet agents executing. Exploit dev has gotten scary easy. Patched in 6.9.5...

AseemShrey's profile picture

Aseem Shrey

8,925 subscribers

33,831 görüntüleme • 2 ay önce •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

2 Yorum

Sandeep Kamble profil fotoğrafı
Sandeep Kamble2 ay önce

Nah man. You can't easily create RCE with any model. It was not easy.

Aseem Shrey profil fotoğrafı
Aseem Shrey1 ay önce

Agreed. I am testing doing it with open source models, like GLM 5.2. This was with sonnet as agents and opus as orchestrator. But also we had the benefit of knowing that there’s a pre-auth RCE in the version change. So you just needed to reverse the patch.

Benzer Videolar

Here's wp2shell 🐚 single-file, zero-dependency PoC for the WordPress core pre-auth RCE (CVE-2026-63030 + CVE-2026-60137) one anonymous HTTP request: REST batch route confusion → unauth SQLi → admin hash → shell default install. no plugins. no login. the best of other public PoCs, unified into one file. scanner + full-chain code + deep dive + lab to play 👇
0:53

Here's wp2shell 🐚 single-file, zero-dependency PoC for the WordPress core pre-auth RCE (CVE-2026-63030 + CVE-2026-60137) one anonymous HTTP request: REST batch route confusion → unauth SQLi → admin hash → shell default install. no plugins. no login. the best of other public PoCs, unified into one file. scanner + full-chain code + deep dive + lab to play 👇

0xSha

28,781 görüntüleme • 2 ay önce

🚨 ثغرة حرجة في نواة WordPress تسمح بتنفيذ أوامر عن بُعد دون مصادقة, واستغلال نشط مؤكد خلال 24 ساعة من الإفصاح سلسلة أُطلق عليها "wp2shell"، اكتشفتها شركة Searchlight Cyber عبر وحدة Assetnote، وأُفصح عنها في 17 يوليو 2026 عبر برنامج HackerOne الخاص بـ WordPress. التقييم CVSS 10.0. 🔹 التفاصيل التقنية: • CVE-2026-63030, خلل route confusion في نقطة نهاية REST API المخصصة للطلبات المجمّعة (/wp-json/batch/v1). خلل في التحليل يُخرج مصفوفتين داخليتين عن التزامن، فيُنفَّذ طلب فرعي تحت معالج طلب آخر. أُدخل هذا الخلل في الإصدار 6.9 • CVE-2026-60137, حقن SQL في معامل author__not_in داخل الصنف WP_Query، وهو الصنف الذي تمر عبره غالبية استعلامات WordPress. موجود منذ الإصدار 6.8 • منفردةً، كل ثغرة محدودة الأثر. مسلسلةً، تنتهي بتنفيذ أوامر عن بُعد على تثبيت افتراضي دون حساب ودون إضافات ودون تفاعل من المستخدم • بحسب تحليل Cloudflare، مسار الوصول إلى RCE متاح حين لا يكون persistent object cache مفعّلاً, وهو الوضع الافتراضي في أغلب التثبيتات. 🔹 الوضع الحالي: • PoC عام متاح على GitHub منذ أيام • Wiz Research رصدت استغلالاً فعلياً in the wild مع زرع webshells دائمة على خوادم مصابة • WordPress.[org فعّلت التحديث التلقائي القسري نظراً لخطورة الثغرة 🔹 ما يجب فعله: • التحقق من الإصدار فعلياً لا افتراض نجاح التحديث التلقائي، عبر wp core version أو من لوحة التحكم • حصر كل تثبيتات WordPress في البيئة، بما فيها بيئات الاختبار والتطوير والمواقع المنسية • لمن لا يستطيع الإصلاح فوراً: عليه حجب /wp-json/batch/v1 ومعامل rest_route=/batch/v1 على مستوى WAF كإجراء مؤقت لا كبديل • مراجعة السجلات بحثاً عن طلبات POST إلى المسارين أعلاه، وفحص الخوادم بحثاً عن ملفات webshell مزروعة، من كان مكشوفاً بين 17 و20 يوليو يُفترض أنه استُهدف حتى يثبت العكس 🔎 هذه حالة تستحق الدراسة في تقييم المخاطر: ثغرتان تُصنَّفان منفردتين بخطورة متوسطة، تنتجان مسلسلتين أخطر نتيجة ممكنة في تطبيقات الويب. النظرة أحادية الثغرة كانت ستمرّ على كلتيهما دون إنذار. 🔎 نقطة تستحق الانتباه: Searchlight Cyber اكتشفت هذه السلسلة باستخدام نموذج لغوي (GPT-5.6 Sol). بعد أسبوع من حادثة استخدام نماذج في اختراق بنية Hugging Face، هذه هي الوجهة المقابلة للقدرة نفسها، والفارق ليس في النموذج بل في من يشغّله ولأي غرض. 🔎 بالنسبة لبيئات OT تحديداً: WordPress يعمل على عدد كبير من المواقع المؤسسية والبوابات التعريفية، وكثير منها مستضاف على شرائح شبكية قريبة من بيئات التشغيل أو متصلة بها. تثبيت منسي على خادم في DMZ هو مسار وصول أولي كلاسيكي.
0:39

🚨 ثغرة حرجة في نواة WordPress تسمح بتنفيذ أوامر عن بُعد دون مصادقة, واستغلال نشط مؤكد خلال 24 ساعة من الإفصاح سلسلة أُطلق عليها "wp2shell"، اكتشفتها شركة Searchlight Cyber عبر وحدة Assetnote، وأُفصح عنها في 17 يوليو 2026 عبر برنامج HackerOne الخاص بـ WordPress. التقييم CVSS 10.0. 🔹 التفاصيل التقنية: • CVE-2026-63030, خلل route confusion في نقطة نهاية REST API المخصصة للطلبات المجمّعة (/wp-json/batch/v1). خلل في التحليل يُخرج مصفوفتين داخليتين عن التزامن، فيُنفَّذ طلب فرعي تحت معالج طلب آخر. أُدخل هذا الخلل في الإصدار 6.9 • CVE-2026-60137, حقن SQL في معامل author__not_in داخل الصنف WP_Query، وهو الصنف الذي تمر عبره غالبية استعلامات WordPress. موجود منذ الإصدار 6.8 • منفردةً، كل ثغرة محدودة الأثر. مسلسلةً، تنتهي بتنفيذ أوامر عن بُعد على تثبيت افتراضي دون حساب ودون إضافات ودون تفاعل من المستخدم • بحسب تحليل Cloudflare، مسار الوصول إلى RCE متاح حين لا يكون persistent object cache مفعّلاً, وهو الوضع الافتراضي في أغلب التثبيتات. 🔹 الوضع الحالي: • PoC عام متاح على GitHub منذ أيام • Wiz Research رصدت استغلالاً فعلياً in the wild مع زرع webshells دائمة على خوادم مصابة • WordPress.[org فعّلت التحديث التلقائي القسري نظراً لخطورة الثغرة 🔹 ما يجب فعله: • التحقق من الإصدار فعلياً لا افتراض نجاح التحديث التلقائي، عبر wp core version أو من لوحة التحكم • حصر كل تثبيتات WordPress في البيئة، بما فيها بيئات الاختبار والتطوير والمواقع المنسية • لمن لا يستطيع الإصلاح فوراً: عليه حجب /wp-json/batch/v1 ومعامل rest_route=/batch/v1 على مستوى WAF كإجراء مؤقت لا كبديل • مراجعة السجلات بحثاً عن طلبات POST إلى المسارين أعلاه، وفحص الخوادم بحثاً عن ملفات webshell مزروعة، من كان مكشوفاً بين 17 و20 يوليو يُفترض أنه استُهدف حتى يثبت العكس 🔎 هذه حالة تستحق الدراسة في تقييم المخاطر: ثغرتان تُصنَّفان منفردتين بخطورة متوسطة، تنتجان مسلسلتين أخطر نتيجة ممكنة في تطبيقات الويب. النظرة أحادية الثغرة كانت ستمرّ على كلتيهما دون إنذار. 🔎 نقطة تستحق الانتباه: Searchlight Cyber اكتشفت هذه السلسلة باستخدام نموذج لغوي (GPT-5.6 Sol). بعد أسبوع من حادثة استخدام نماذج في اختراق بنية Hugging Face، هذه هي الوجهة المقابلة للقدرة نفسها، والفارق ليس في النموذج بل في من يشغّله ولأي غرض. 🔎 بالنسبة لبيئات OT تحديداً: WordPress يعمل على عدد كبير من المواقع المؤسسية والبوابات التعريفية، وكثير منها مستضاف على شرائح شبكية قريبة من بيئات التشغيل أو متصلة بها. تثبيت منسي على خادم في DMZ هو مسار وصول أولي كلاسيكي.

Abdulrahman Alamri

15,591 görüntüleme • 1 ay önce

⚡ Kleros Development Update | May 2026 Kleros Foresight opens the month: movies round 2 is now live, so you can trade today. Batch redemption shipped, redemption values were corrected with a pre-check before claiming, resolved answers now show right on the market cards, and a resolution email tells you the moment your winnings are ready to claim. Kleros Skills is being prepared for launch: knowledge packs that teach AI agents how to use Kleros, whatever assistant they run on. The first two packs are almost ready. One lets an agent pin files to IPFS for $0.01 in USDC, the other lets it interact with Kleros Curate and Scout. A Kleros CLI, ERC-8004 agent verification, and an Escrow pack are on the roadmap. Scout reached its definitive version: 2.6M curated addresses on the homepage, a dedicated new-submission page, a transaction-result page, and an in-app file viewer. Uploads now flow through Atlas with limits sourced from role restrictions, submissions defer uploads until sign-in, and ATQ duplicate detection plus JavaScript Court landed in the disputes view. Atlas shipped v1.6.0. Signup is now per product: Court V1, Court V2, and Foresight each get their own confirmation email, unsubscribe link, and onboarding flow. Court reminders moved to a fixed, configurable time, and every batch send is preceded by a transaction simulation. Proof of Humanity V2 email notifications now cover the complete profile lifecycle: pending revocations, vouching activity, disputed flows, and challenge outcomes, processed end to end by Atlas. Only the frontend opt-in toggle remains. An evidence-key fix means older cases render attachments properly again, and the referral system spec went through review. Vea published the veashi-sdk to npm at v0.0.2, the first packaged version of the cross-chain SDK. The LayerZero Labs contracts were reorganized under the adapter layout, the Hashi executor decoupling merged after April's review pass, and an ENVIO HyperIndex indexer for the relayer is on the way. Court V2: The contracts are being simplified, the partial-coherence kit was merged, and the security findings are being worked through. From here, the code heads into another round of internal reviews. We'd rather take the time and get it right. Full breakdown 👇
2:48

⚡ Kleros Development Update | May 2026 Kleros Foresight opens the month: movies round 2 is now live, so you can trade today. Batch redemption shipped, redemption values were corrected with a pre-check before claiming, resolved answers now show right on the market cards, and a resolution email tells you the moment your winnings are ready to claim. Kleros Skills is being prepared for launch: knowledge packs that teach AI agents how to use Kleros, whatever assistant they run on. The first two packs are almost ready. One lets an agent pin files to IPFS for $0.01 in USDC, the other lets it interact with Kleros Curate and Scout. A Kleros CLI, ERC-8004 agent verification, and an Escrow pack are on the roadmap. Scout reached its definitive version: 2.6M curated addresses on the homepage, a dedicated new-submission page, a transaction-result page, and an in-app file viewer. Uploads now flow through Atlas with limits sourced from role restrictions, submissions defer uploads until sign-in, and ATQ duplicate detection plus JavaScript Court landed in the disputes view. Atlas shipped v1.6.0. Signup is now per product: Court V1, Court V2, and Foresight each get their own confirmation email, unsubscribe link, and onboarding flow. Court reminders moved to a fixed, configurable time, and every batch send is preceded by a transaction simulation. Proof of Humanity V2 email notifications now cover the complete profile lifecycle: pending revocations, vouching activity, disputed flows, and challenge outcomes, processed end to end by Atlas. Only the frontend opt-in toggle remains. An evidence-key fix means older cases render attachments properly again, and the referral system spec went through review. Vea published the veashi-sdk to npm at v0.0.2, the first packaged version of the cross-chain SDK. The LayerZero Labs contracts were reorganized under the adapter layout, the Hashi executor decoupling merged after April's review pass, and an ENVIO HyperIndex indexer for the relayer is on the way. Court V2: The contracts are being simplified, the partial-coherence kit was merged, and the security findings are being worked through. From here, the code heads into another round of internal reviews. We'd rather take the time and get it right. Full breakdown 👇

Kleros

11,849 görüntüleme • 3 ay önce

OpenAI and Anthropic this week: GPT-5.6 price cuts, Claude cracking ciphers, and both backing "Pacing the Frontier" (Week 31, 2026) Starting with OpenAI - GPT-5.6 got a big price cut, with Luna dropping 80% and Terra 20%, plus a new Fast mode for Sol in the API ChatGPT for Academic Researchers opened too, giving free frontier model access to 100,000 scientists On the research side, OpenAI shared ten advances in mathematics and theoretical computer science, all from an internal version of the next model called Astra, plus a study on how AI expands the range of work people do and a field report on scientists using coding agents On the developer side: GPT Transcribe and GPT Live Transcribe, a Terraform provider, an open-source Codex Security CLI, Sign in with ChatGPT in beta, and a desktop app update with browser upgrades, multi-repo review, image editing, and an Activity view GPT-5.4 retires from Codex end of August, the Student Collective opened, and two API settings tripled Sol's ARC-AGI-3 score Plus, I spotted a new "Places" section in ChatGPT Onto Anthropic - Claude Mythos Preview helped find weaknesses in cryptographic algorithms, cutting the effective key strength of the post-quantum scheme HAWK in half and speeding up an attack on reduced-round AES by 200 to 800 times, with no impact on production systems Anthropic released MCP 2026-07-28, the biggest protocol update since launch, moving it to a stateless core with standardized extensions and hardened auth Anthropic disclosed three incidents where Claude reached the internet from inside cybersecurity evaluation environments and accessed real systems of three organizations, traced to a misconfiguration rather than a model alignment failure Dario Amodei laid out Anthropic's position on open-weights models too, saying clearly a ban has never been on the table Both companies backed the "Pacing the Frontier" petition And I spotted Anthropic adding noindex and nofollow to shared Claude conversations
2:45

OpenAI and Anthropic this week: GPT-5.6 price cuts, Claude cracking ciphers, and both backing "Pacing the Frontier" (Week 31, 2026) Starting with OpenAI - GPT-5.6 got a big price cut, with Luna dropping 80% and Terra 20%, plus a new Fast mode for Sol in the API ChatGPT for Academic Researchers opened too, giving free frontier model access to 100,000 scientists On the research side, OpenAI shared ten advances in mathematics and theoretical computer science, all from an internal version of the next model called Astra, plus a study on how AI expands the range of work people do and a field report on scientists using coding agents On the developer side: GPT Transcribe and GPT Live Transcribe, a Terraform provider, an open-source Codex Security CLI, Sign in with ChatGPT in beta, and a desktop app update with browser upgrades, multi-repo review, image editing, and an Activity view GPT-5.4 retires from Codex end of August, the Student Collective opened, and two API settings tripled Sol's ARC-AGI-3 score Plus, I spotted a new "Places" section in ChatGPT Onto Anthropic - Claude Mythos Preview helped find weaknesses in cryptographic algorithms, cutting the effective key strength of the post-quantum scheme HAWK in half and speeding up an attack on reduced-round AES by 200 to 800 times, with no impact on production systems Anthropic released MCP 2026-07-28, the biggest protocol update since launch, moving it to a stateless core with standardized extensions and hardened auth Anthropic disclosed three incidents where Claude reached the internet from inside cybersecurity evaluation environments and accessed real systems of three organizations, traced to a misconfiguration rather than a model alignment failure Dario Amodei laid out Anthropic's position on open-weights models too, saying clearly a ban has never been on the table Both companies backed the "Pacing the Frontier" petition And I spotted Anthropic adding noindex and nofollow to shared Claude conversations

Tibor Blaho

11,623 görüntüleme • 1 ay önce

Cerebras inference is very fast. So fast that it changes how we think about configuring our LLMs for voice agent use cases. Kimi K2.6 is a 1T parameter reasoning model that Cerebras serves at 650 - 1,000 tokens per second (end-to-end throughput), with time to first token metrics as low as 150ms (latency). These numbers are two to three times faster than other similarly capable models. The biggest lever we get from this kind of speed is that we can use the model in reasoning mode, and still have excellent "time to first non-thinking token." This solves a big pain point we have in 2026 for voice agent use cases. Almost all recent innovation in post-training has focused on making models good at reasoning ("test time compute"). This is great, but it makes the user-facing model latency much, much slower. Which is a problem for conversational voice agents. We can run Kimi K2.6 with reasoning turned on, and get responses faster than other models produce with reasoning disabled. On my 30-turn voice agent benchmark, Kimi K2.6 with reasoning enabled ties GPT 5.1 and Haiku 4.5 with reasoning disabled, and is still about 200ms seconds faster! On my primary task agent benchmark, Kimi K2.6 is now the #2 model. It ranks just behind Gemini 3.5 Flash in "high" reasoning mode, and tied with GLM 5, Sonnet 4.6, and GPT 5.4 with reasoning set to "low." But Kimi K2.6 completes each turn in the agent loop in under 500ms. The other four models are all at least 3x slower. (Models only qualify for this benchmark if they can complete task turns at a P50 <4s.) A couple of other things that this speed buys us, for production voice agents: - Tool calls happen fast enough that we don't have to work around tool call latency in our pipeline design. - We can prompt the model to output structured data at the beginning of a response, followed by plain text for voice generation. This opens up possibilities like asking the model to do complex classification/generation tasks that influence the rest of the pipeline. For example, the model could create a detailed style prompt for a steerable TTS model, for each individual conversation turn. And, of course, you can use Kimi K2.6 with reasoning turned off. Cerebras calls this "instant" mode. Here's a video of a Cerebras Kimi K2.6 voice agent with voice-to-voice response time, measured at the client, under 500ms. This is the true response latency as perceived by the user, including all network and audio codec overhead, transcription and turn detection, Kimi K2.6 token generation, and voice generation. 500ms is, effectively, instant. So the Cerebras naming for this mode is a propos. :-)
0:40

Cerebras inference is very fast. So fast that it changes how we think about configuring our LLMs for voice agent use cases. Kimi K2.6 is a 1T parameter reasoning model that Cerebras serves at 650 - 1,000 tokens per second (end-to-end throughput), with time to first token metrics as low as 150ms (latency). These numbers are two to three times faster than other similarly capable models. The biggest lever we get from this kind of speed is that we can use the model in reasoning mode, and still have excellent "time to first non-thinking token." This solves a big pain point we have in 2026 for voice agent use cases. Almost all recent innovation in post-training has focused on making models good at reasoning ("test time compute"). This is great, but it makes the user-facing model latency much, much slower. Which is a problem for conversational voice agents. We can run Kimi K2.6 with reasoning turned on, and get responses faster than other models produce with reasoning disabled. On my 30-turn voice agent benchmark, Kimi K2.6 with reasoning enabled ties GPT 5.1 and Haiku 4.5 with reasoning disabled, and is still about 200ms seconds faster! On my primary task agent benchmark, Kimi K2.6 is now the #2 model. It ranks just behind Gemini 3.5 Flash in "high" reasoning mode, and tied with GLM 5, Sonnet 4.6, and GPT 5.4 with reasoning set to "low." But Kimi K2.6 completes each turn in the agent loop in under 500ms. The other four models are all at least 3x slower. (Models only qualify for this benchmark if they can complete task turns at a P50 <4s.) A couple of other things that this speed buys us, for production voice agents: - Tool calls happen fast enough that we don't have to work around tool call latency in our pipeline design. - We can prompt the model to output structured data at the beginning of a response, followed by plain text for voice generation. This opens up possibilities like asking the model to do complex classification/generation tasks that influence the rest of the pipeline. For example, the model could create a detailed style prompt for a steerable TTS model, for each individual conversation turn. And, of course, you can use Kimi K2.6 with reasoning turned off. Cerebras calls this "instant" mode. Here's a video of a Cerebras Kimi K2.6 voice agent with voice-to-voice response time, measured at the client, under 500ms. This is the true response latency as perceived by the user, including all network and audio codec overhead, transcription and turn detection, Kimi K2.6 token generation, and voice generation. 500ms is, effectively, instant. So the Cerebras naming for this mode is a propos. :-)

kwindla

40,593 görüntüleme • 3 ay önce

Last night was the biggest disaster in the history of Tesla. Let me walk you through what actually happened on that earnings call, because the headlines are doing you a disservice: Elon Musk got on the call and admitted (his words) that Hardware 3 "simply does not have the capability to achieve unsupervised FSD." He said he wished it were otherwise. He said the memory bandwidth is one-eighth of what Hardware 4 has. And that's the end of the conversation. Approximately 4 million Tesla vehicles on the road right now have Hardware 3. Many of those owners paid $8,000 to $15,000 for Full Self-Driving capability based on Musk's repeated promises (going back to 2016) that the hardware was sufficient for full autonomy. As recently as 2022, Musk was publicly assuring owners that HW3 had the processing power to get it done. BUT IT DIDN'T Those promises are now officially broken. The solution is a "discounted trade-in" toward a new car with Hardware 4. Not a refund or a free upgrade... A discount on buying ANOTHER Tesla. Investor Ross Gerber said it too - all HW3 owners got screwed, and with roughly 285,000 FSD purchasers affected, the potential liability runs into the BILLIONS. But that's not even the worst part. Musk was asked if the current FSD v14.3 was ready for unsupervised deployment. He said yes. Then immediately walked it back and admitted Tesla has "major architectural improvements" in the pipeline that would significantly improve safety. What he really means: the software isn't SAFE ENOUGH to deploy without a human watching. Full unsupervised FSD for consumer cars is pushed to Q4 2026. At the earliest... Maybe. How many times has this deadline been pushed? I've lost count. And trust me, I've seen a lot of broken promises. But this one takes the cake. Now let's talk about the numbers everyone is celebrating: Tesla reported $22.4 billion in revenue and $0.41 in non-GAAP earnings. A "double beat." The stock popped 4% after hours. Victory, right? WRONG Dig into the actual filing: The number one driver of operating income improvement wasn't cost reductions, wasn't volume growth, wasn't FSD revenue. It was - and Tesla listed this FIRST in their own shareholder letter - "one-time benefits related to warranty and tariffs." They released warranty reserves. They booked tariff refund windfalls. They stretched supplier payments by 10 days. They took on billions in new debt. Then they presented everything through non-GAAP metrics that strip out over $1 billion in stock-based compensation. GAAP net income was $477 million on $22.4 billion in revenue. That's a 2.1% net margin. On a $1.4 trillion market cap. Let me put that in perspective: 3.75 billion shares outstanding. Annualize the Q1 GAAP profit and you get roughly $1.9 billion. That's a trailing P/E ratio north of 700. Use the adjusted number - strip out stock comp, which is a REAL cost to shareholders through dilution - and you're still at around 250x earnings. All of this is extremely bad, but I didn't even talk about the CAPEX BOMB yet... 3 months ago, Tesla guided to "over $20 billion" in 2026 capital expenditure. Last night they raised it to over $25 billion. A $5 billion increase in a single quarter. That's 3x their historical annual capex run rate - $8.5 billion in 2025, $11.3 billion in 2024. The CFO confirmed on the call that Tesla expects NEGATIVE free cash flow for the rest of the year. So you have a company generating roughly $6 billion in annual free cash flow on a good year, and they're about to spend $25 billion. The math doesn't work. They will almost certainly need to issue equity. Which means dilution. Which means the $1.9 billion in annual earnings gets spread across even MORE shares. The core auto business is literally deteriorating in real time: Tesla delivered 358,000 vehicles in Q1 (missed estimates again). They produced 408,000. That's 50,000 cars sitting on lots that nobody bought. Inventory days jumped from 10 to 27 in just a few quarters. California (their most important US market) saw registrations crash 24% year over year. Their market share in the state fell from 9.2% to 7.7%. That's on top of a Q1 2025 that was ALREADY weak from Model Y retooling. They're declining off a decline. And here's what really kills the bull case... The entire valuation rests on robotaxis, Optimus robots, and autonomy. So let's put numbers on it: Waymo - the actual leader in autonomous driving with 15 million completed rides in 2025 alone, over 127 million autonomous miles driven, operating commercially across 6 US cities with plans to expand to 20 more - just raised $16 billion at a $126 billion valuation. That's the market's verdict on what the LEADING robotaxi company is worth. $126 billion. And Waymo is YEARS ahead of Tesla in actual deployment. Tesla has 3.75 billion shares outstanding. So even if you assign $126 billion in robotaxi value (giving Tesla full credit for matching Waymo despite being nowhere close) that's $33 a share. Add the auto business at generous auto-industry multiples, maybe $20 a share. Throw in energy storage and services, $10-15. Sum of the parts gets you to roughly $65-70 a share if you're feeling generous. Maybe $50 if you're not. The stock is $387. So what exactly are you paying for? You're paying for a STORY. You're paying for PROMISES that keep getting pushed back, technology that keeps falling short, and a business plan that requires spending $25 billion a year while the core product sells fewer units at declining margins in a market where California sales just fell 24% and the federal EV tax credit is gone. I managed the number one mutual fund in America. I founded two billion-dollar hedge funds. I've been doing this since 1981. And I am telling you: Tesla at $387 is one of the most egregious mispricings I have seen in my entire career. THE CRASH WILL BE EPIC
5:21

Last night was the biggest disaster in the history of Tesla. Let me walk you through what actually happened on that earnings call, because the headlines are doing you a disservice: Elon Musk got on the call and admitted (his words) that Hardware 3 "simply does not have the capability to achieve unsupervised FSD." He said he wished it were otherwise. He said the memory bandwidth is one-eighth of what Hardware 4 has. And that's the end of the conversation. Approximately 4 million Tesla vehicles on the road right now have Hardware 3. Many of those owners paid $8,000 to $15,000 for Full Self-Driving capability based on Musk's repeated promises (going back to 2016) that the hardware was sufficient for full autonomy. As recently as 2022, Musk was publicly assuring owners that HW3 had the processing power to get it done. BUT IT DIDN'T Those promises are now officially broken. The solution is a "discounted trade-in" toward a new car with Hardware 4. Not a refund or a free upgrade... A discount on buying ANOTHER Tesla. Investor Ross Gerber said it too - all HW3 owners got screwed, and with roughly 285,000 FSD purchasers affected, the potential liability runs into the BILLIONS. But that's not even the worst part. Musk was asked if the current FSD v14.3 was ready for unsupervised deployment. He said yes. Then immediately walked it back and admitted Tesla has "major architectural improvements" in the pipeline that would significantly improve safety. What he really means: the software isn't SAFE ENOUGH to deploy without a human watching. Full unsupervised FSD for consumer cars is pushed to Q4 2026. At the earliest... Maybe. How many times has this deadline been pushed? I've lost count. And trust me, I've seen a lot of broken promises. But this one takes the cake. Now let's talk about the numbers everyone is celebrating: Tesla reported $22.4 billion in revenue and $0.41 in non-GAAP earnings. A "double beat." The stock popped 4% after hours. Victory, right? WRONG Dig into the actual filing: The number one driver of operating income improvement wasn't cost reductions, wasn't volume growth, wasn't FSD revenue. It was - and Tesla listed this FIRST in their own shareholder letter - "one-time benefits related to warranty and tariffs." They released warranty reserves. They booked tariff refund windfalls. They stretched supplier payments by 10 days. They took on billions in new debt. Then they presented everything through non-GAAP metrics that strip out over $1 billion in stock-based compensation. GAAP net income was $477 million on $22.4 billion in revenue. That's a 2.1% net margin. On a $1.4 trillion market cap. Let me put that in perspective: 3.75 billion shares outstanding. Annualize the Q1 GAAP profit and you get roughly $1.9 billion. That's a trailing P/E ratio north of 700. Use the adjusted number - strip out stock comp, which is a REAL cost to shareholders through dilution - and you're still at around 250x earnings. All of this is extremely bad, but I didn't even talk about the CAPEX BOMB yet... 3 months ago, Tesla guided to "over $20 billion" in 2026 capital expenditure. Last night they raised it to over $25 billion. A $5 billion increase in a single quarter. That's 3x their historical annual capex run rate - $8.5 billion in 2025, $11.3 billion in 2024. The CFO confirmed on the call that Tesla expects NEGATIVE free cash flow for the rest of the year. So you have a company generating roughly $6 billion in annual free cash flow on a good year, and they're about to spend $25 billion. The math doesn't work. They will almost certainly need to issue equity. Which means dilution. Which means the $1.9 billion in annual earnings gets spread across even MORE shares. The core auto business is literally deteriorating in real time: Tesla delivered 358,000 vehicles in Q1 (missed estimates again). They produced 408,000. That's 50,000 cars sitting on lots that nobody bought. Inventory days jumped from 10 to 27 in just a few quarters. California (their most important US market) saw registrations crash 24% year over year. Their market share in the state fell from 9.2% to 7.7%. That's on top of a Q1 2025 that was ALREADY weak from Model Y retooling. They're declining off a decline. And here's what really kills the bull case... The entire valuation rests on robotaxis, Optimus robots, and autonomy. So let's put numbers on it: Waymo - the actual leader in autonomous driving with 15 million completed rides in 2025 alone, over 127 million autonomous miles driven, operating commercially across 6 US cities with plans to expand to 20 more - just raised $16 billion at a $126 billion valuation. That's the market's verdict on what the LEADING robotaxi company is worth. $126 billion. And Waymo is YEARS ahead of Tesla in actual deployment. Tesla has 3.75 billion shares outstanding. So even if you assign $126 billion in robotaxi value (giving Tesla full credit for matching Waymo despite being nowhere close) that's $33 a share. Add the auto business at generous auto-industry multiples, maybe $20 a share. Throw in energy storage and services, $10-15. Sum of the parts gets you to roughly $65-70 a share if you're feeling generous. Maybe $50 if you're not. The stock is $387. So what exactly are you paying for? You're paying for a STORY. You're paying for PROMISES that keep getting pushed back, technology that keeps falling short, and a business plan that requires spending $25 billion a year while the core product sells fewer units at declining margins in a market where California sales just fell 24% and the federal EV tax credit is gone. I managed the number one mutual fund in America. I founded two billion-dollar hedge funds. I've been doing this since 1981. And I am telling you: Tesla at $387 is one of the most egregious mispricings I have seen in my entire career. THE CRASH WILL BE EPIC

George Noble

1,229,752 görüntüleme • 4 ay önce

//The Wire//1900Z July 14, 2026// //ROUTINE// //BLUF: WAR IN MIDDLE EAST REMAINS HOT WITH USA AND IRAN EXCHANGING HEAVY FIRE OVERNIGHT. NEW YORK TIMES JOURNALISTS ISSUED SUBPOENAS REGARDING THEIR REPORTING ON AIR FORCE ONE.// -----BEGIN TEARLINE----- -International Events- Middle East: The war continued to escalate overnight, with the attack/counterattack cycle no longer being distinguishable, as all belligerents are now attacking constantly. At least two more ships have been struck in the Strait of Hormuz since last night, and the US has continued to fly continuous sorties to strike targets within Iran. Dozens of targets were struck overnight, with CENTCOM announcing that the sorties took 5 hours to complete throughout the region. As of this morning, nearly all of the targets that have been struck have been within a few hundred yards of the Gulf, with heavy concentrations of targets being located within Bushehr, Bandar Abbas, Chabahar, and Jask, all of which are major naval bases. Most of the Gulf islands have also been struck, with Qeshm and Kish Islands being targeted heavily this afternoon. Conversely, Iran has conducted their own strikes in Jordan, Bahrain, Qatar, and Kuwait. In Kuwait, Iranian forces have conducted counter-battery fire on American HIMARS missile launcher sites, with multiple ballistic missile strikes taking place at most of the US bases and missile launch sites all day. Analyst Comment: Over the past 24 hours, the war in the Middle East has returned to the level of fighting first observed during the height of the war back in March. How long this is planned to continue is unknown, but this is not a slight increase in targeting; the war appears to be fully back on once again. United Kingdom: This morning Counterterrorism police released more details regarding a high-profile murder case that took place last week. On Thursday, Ann Widdecombe was found murdered in her home in the town of Haytor in Devon. After her murder was discovered, local authorities immediately referred the case to counterterrorism, and one suspect has already been arrested in conjunction with this case. This suspect has been charged for the murder, and as of this morning terrorism offenses have been added to the list of charges. Analyst Comment: This case is noteworthy as most of the information so far indicates this was a political assassination, and the speed at which authorities have immediately declared this to be a terrorism incident is very, very unusual. Widdecombe was a former Member of Parliament, and in her later years was a familiar conservative political commentator known to weigh in on political issues throughout the nation. More details may or may not come to light in due time regarding the identity of the suspect, but due to the high-profile nature of this murder, this case will be in the headlines for a while. -HomeFront- Washington D.C. - Yesterday a total of five New York Times reporters have been subpoenaed to appear before a grand jury, to testify regarding their reporting on the alleged security breaches onboard the new Air Force One. Last week, President Trump flew to Turkey for the NATO summit on the new airframe, but during the trip, an undisclosed security issue prompted the Secret Service to switch back to the older platform. Analyst Comment: The details of exactly what the alleged crimes are, have not been disclosed. The New York Times has a history of publishing content which could lead to security issues, but in this case nothing they wrote in their original report appears to have been classified. However, they did explicitly state that they had a source who had classified knowledge of the defenses (or rather, the alleged lack of defenses) on the new Air Force One platform, which is probably why the harsh crackdown on the New York Times. They also made the claim that the new airframe has not had enough time to install the anti-missile countermeasures of the older platform, though no detail on this was provided. Regardless, talking to journalists in any capacity about any of the protection measures used by the White House is a huge no-no, and one of the most sensitive issues that always results in a very heavy-handed response. -----END TEARLINE----- Analyst Comments: As the war in the Persian Gulf rages on, concerns are growing regarding the apparent widening of the war to include the Red Sea region. The mutual targeting between the Saudis and the Houthis in Yemen has continued to some degree, though it's too soon to tell if either party is committed to turning this into a more protracted fight. If that is the chosen course of action, the situation is likely to get very serious. While the Strait of Hormuz remains a hot warzone that has restricted the flow of about 20 million barrels per day out of the region, the Saudi East-West Pipeline system has been working to reduce this deficit by pumping roughly 7 million barrels per day during most of this conflict. This has eased the burden of Hormuz being cut off, and has been one of the main factors keeping oil from reaching $200 per barrel. However, this pipeline runs from the Gulf, across the desert, before terminating in Yanbu at a major oil export terminal. This terminal....is within missile range of the Houthis. Somewhat interestingly, there are also very little air defenses in the southern regions of Saudi Arabia despite the Saudis fighting the Houthis for a couple of decades at this point; nearly all missile defenses are on the northern coastline or in the vicinity of American bases. So far during this conflict, the Iranians have successfully struck the Yanbu oil terminal using extremely long-range (and slow-flying) drones. The Houthis have a much higher chance of success in threatening Yanbu, and if they are able to strike this facility, the global oil crisis will go from worse to worst. Analyst: S2A1 Research: NomadNet: 5fa68c88be727a0e1a250a75e5e79269 Disclaimer: No LLMs were used in the writing of this report. //END REPORT//
4:58

//The Wire//1900Z July 14, 2026// //ROUTINE// //BLUF: WAR IN MIDDLE EAST REMAINS HOT WITH USA AND IRAN EXCHANGING HEAVY FIRE OVERNIGHT. NEW YORK TIMES JOURNALISTS ISSUED SUBPOENAS REGARDING THEIR REPORTING ON AIR FORCE ONE.// -----BEGIN TEARLINE----- -International Events- Middle East: The war continued to escalate overnight, with the attack/counterattack cycle no longer being distinguishable, as all belligerents are now attacking constantly. At least two more ships have been struck in the Strait of Hormuz since last night, and the US has continued to fly continuous sorties to strike targets within Iran. Dozens of targets were struck overnight, with CENTCOM announcing that the sorties took 5 hours to complete throughout the region. As of this morning, nearly all of the targets that have been struck have been within a few hundred yards of the Gulf, with heavy concentrations of targets being located within Bushehr, Bandar Abbas, Chabahar, and Jask, all of which are major naval bases. Most of the Gulf islands have also been struck, with Qeshm and Kish Islands being targeted heavily this afternoon. Conversely, Iran has conducted their own strikes in Jordan, Bahrain, Qatar, and Kuwait. In Kuwait, Iranian forces have conducted counter-battery fire on American HIMARS missile launcher sites, with multiple ballistic missile strikes taking place at most of the US bases and missile launch sites all day. Analyst Comment: Over the past 24 hours, the war in the Middle East has returned to the level of fighting first observed during the height of the war back in March. How long this is planned to continue is unknown, but this is not a slight increase in targeting; the war appears to be fully back on once again. United Kingdom: This morning Counterterrorism police released more details regarding a high-profile murder case that took place last week. On Thursday, Ann Widdecombe was found murdered in her home in the town of Haytor in Devon. After her murder was discovered, local authorities immediately referred the case to counterterrorism, and one suspect has already been arrested in conjunction with this case. This suspect has been charged for the murder, and as of this morning terrorism offenses have been added to the list of charges. Analyst Comment: This case is noteworthy as most of the information so far indicates this was a political assassination, and the speed at which authorities have immediately declared this to be a terrorism incident is very, very unusual. Widdecombe was a former Member of Parliament, and in her later years was a familiar conservative political commentator known to weigh in on political issues throughout the nation. More details may or may not come to light in due time regarding the identity of the suspect, but due to the high-profile nature of this murder, this case will be in the headlines for a while. -HomeFront- Washington D.C. - Yesterday a total of five New York Times reporters have been subpoenaed to appear before a grand jury, to testify regarding their reporting on the alleged security breaches onboard the new Air Force One. Last week, President Trump flew to Turkey for the NATO summit on the new airframe, but during the trip, an undisclosed security issue prompted the Secret Service to switch back to the older platform. Analyst Comment: The details of exactly what the alleged crimes are, have not been disclosed. The New York Times has a history of publishing content which could lead to security issues, but in this case nothing they wrote in their original report appears to have been classified. However, they did explicitly state that they had a source who had classified knowledge of the defenses (or rather, the alleged lack of defenses) on the new Air Force One platform, which is probably why the harsh crackdown on the New York Times. They also made the claim that the new airframe has not had enough time to install the anti-missile countermeasures of the older platform, though no detail on this was provided. Regardless, talking to journalists in any capacity about any of the protection measures used by the White House is a huge no-no, and one of the most sensitive issues that always results in a very heavy-handed response. -----END TEARLINE----- Analyst Comments: As the war in the Persian Gulf rages on, concerns are growing regarding the apparent widening of the war to include the Red Sea region. The mutual targeting between the Saudis and the Houthis in Yemen has continued to some degree, though it's too soon to tell if either party is committed to turning this into a more protracted fight. If that is the chosen course of action, the situation is likely to get very serious. While the Strait of Hormuz remains a hot warzone that has restricted the flow of about 20 million barrels per day out of the region, the Saudi East-West Pipeline system has been working to reduce this deficit by pumping roughly 7 million barrels per day during most of this conflict. This has eased the burden of Hormuz being cut off, and has been one of the main factors keeping oil from reaching $200 per barrel. However, this pipeline runs from the Gulf, across the desert, before terminating in Yanbu at a major oil export terminal. This terminal....is within missile range of the Houthis. Somewhat interestingly, there are also very little air defenses in the southern regions of Saudi Arabia despite the Saudis fighting the Houthis for a couple of decades at this point; nearly all missile defenses are on the northern coastline or in the vicinity of American bases. So far during this conflict, the Iranians have successfully struck the Yanbu oil terminal using extremely long-range (and slow-flying) drones. The Houthis have a much higher chance of success in threatening Yanbu, and if they are able to strike this facility, the global oil crisis will go from worse to worst. Analyst: S2A1 Research: NomadNet: 5fa68c88be727a0e1a250a75e5e79269 Disclaimer: No LLMs were used in the writing of this report. //END REPORT//

S2 Underground

17,672 görüntüleme • 2 ay önce

🚨 THE WHITE HOUSE PANIC: WHAT IS MELANIA TRYING TO BURY? 🕵️‍♀️ The internet is exploding after Yesterday's high-stakes, on-camera denial from First Lady Melania Trump at the White House regarding any connection to Jeffrey Epstein. She called the ongoing claims “lies” that “need to end today.” But the timing is raising massive questions. Why is the East Wing suddenly in a state of high alert over a story they claim is ancient history? 📚 THE SCRUBBED MANUSCRIPT The answer may lie in the legal firestorm surrounding the book Entitled: The Rise and Fall of the House of York by Andrew Lownie. Reports confirm that the initial 2025 hardcover print run contained a nuclear-level quote attributed to a 2007 interview with Jeffrey Epstein: “The first time Donald had sex with Melania was on my plane. Little did he know I beat him to the punch a year before... things got wild... I ended up almost naked in the back of a limo, going at it with Melania.” ⚖️ THE SILENCE OF THE LAMBS As soon as those first 60,000 copies hit the shelves, Melania’s legal team descended. The Recall: HarperCollins UK was forced to recall the book and scrub the passage from all future printings, e-books, and audiobooks. The Apology: The publisher issued a public apology, attempting to bury the claim entirely. The Missing Tapes: While Michael Wolff’s 2017 tapes (containing a different claim about the couple) are public, the raw audio or full transcript of this specific 2007 interview has never surfaced. ❓ THE PREEMPTIVE STRIKE Is Melania’s White House address a genuine defense of her character, or a preemptive strike against something else about to break? The book was scrubbed. The alleged 2007 interview tape is still missing. And now—just months later—the First Lady is using the White House podium to declare the Epstein talk must end. Why was the legal response to this specific book so aggressive? Why did she wait until April 2026 to make this specific on-camera denial? If the story is "defamatory and false," why the sudden five-alarm fire drill in the West Wing? 🧊 THE BIG PICTURE The Epstein shadow continues to loom over the administration, and this level of damage control suggests the "official narrative" is under serious pressure. Melania says the talk needs to "end today," but without the release of the unedited 2007 interview transcripts, the questions will only grow. Is this the final cover-up of the Epstein era, or the crack in the armor that brings the whole house of cards down? Share this before the "Handlers" scrub it again. 🕊️ Video from: RT
0:52

🚨 THE WHITE HOUSE PANIC: WHAT IS MELANIA TRYING TO BURY? 🕵️‍♀️ The internet is exploding after Yesterday's high-stakes, on-camera denial from First Lady Melania Trump at the White House regarding any connection to Jeffrey Epstein. She called the ongoing claims “lies” that “need to end today.” But the timing is raising massive questions. Why is the East Wing suddenly in a state of high alert over a story they claim is ancient history? 📚 THE SCRUBBED MANUSCRIPT The answer may lie in the legal firestorm surrounding the book Entitled: The Rise and Fall of the House of York by Andrew Lownie. Reports confirm that the initial 2025 hardcover print run contained a nuclear-level quote attributed to a 2007 interview with Jeffrey Epstein: “The first time Donald had sex with Melania was on my plane. Little did he know I beat him to the punch a year before... things got wild... I ended up almost naked in the back of a limo, going at it with Melania.” ⚖️ THE SILENCE OF THE LAMBS As soon as those first 60,000 copies hit the shelves, Melania’s legal team descended. The Recall: HarperCollins UK was forced to recall the book and scrub the passage from all future printings, e-books, and audiobooks. The Apology: The publisher issued a public apology, attempting to bury the claim entirely. The Missing Tapes: While Michael Wolff’s 2017 tapes (containing a different claim about the couple) are public, the raw audio or full transcript of this specific 2007 interview has never surfaced. ❓ THE PREEMPTIVE STRIKE Is Melania’s White House address a genuine defense of her character, or a preemptive strike against something else about to break? The book was scrubbed. The alleged 2007 interview tape is still missing. And now—just months later—the First Lady is using the White House podium to declare the Epstein talk must end. Why was the legal response to this specific book so aggressive? Why did she wait until April 2026 to make this specific on-camera denial? If the story is "defamatory and false," why the sudden five-alarm fire drill in the West Wing? 🧊 THE BIG PICTURE The Epstein shadow continues to loom over the administration, and this level of damage control suggests the "official narrative" is under serious pressure. Melania says the talk needs to "end today," but without the release of the unedited 2007 interview transcripts, the questions will only grow. Is this the final cover-up of the Epstein era, or the crack in the armor that brings the whole house of cards down? Share this before the "Handlers" scrub it again. 🕊️ Video from: RT

Project Constitution

43,336 görüntüleme • 5 ay önce

I finally finished my Rust version of Mario Zechner's (Mario Zechner) excellent Pi Agent, which I made with his blessing and which is called pi_agent_rust. You can get it here: If you're not familiar with Pi, it's a minimalist and extensible agent harness (similar to Claude Code and Codex) and, among other uses, serves as the core agent harness inside the OpenClaw project. I say my Rust "version" instead of "port" because it's really quite different in how it's implemented for it to be called a port. Arguably, the incremental functionality in the implementation was more complex than the rest of the project combined. Still, it provides the same features and functionality as the original, and is proven to be compatible with hundreds of popular extensions to Pi (the conformance harness shows 224 out of 224 extensions working perfectly). But the way it's architected has some major changes. Pi Agent relies on node or bun to provide access to the filesystem and for various other tasks, and that is also how Pi's extension system works. I decided early on that I didn't want to do things that way. Instead, I wanted to integrate that functionality directly into the binary itself; that is, to provide equivalent functionality for everything that would normally be provided by node/bun in the original. I did this for several reasons: one, it's a lot more performant in terms of footprint and latency. On realistic end-to-end large-session workloads (not toy microbenchmarks), pi_agent_rust is now: - 4.95x faster than legacy Node and 2.80x faster than legacy Bun at 1mm-token session scale - 4.32x faster than legacy Node and 2.14x faster than legacy Bun at 5mm-token session scale - ~8x to ~13x lower RSS memory footprint in those same scenarios But the other reason is security and control: by handling everything internally in an end-to-end way, we can do all sorts of clever things to harden the system against insecure or malicious extensions. Those extensions no longer have direct access to the ambient filesystem: they now need to go through pi_agent_rust, and we can analyze extensions carefully before ever running them and also block things that look suspicious at runtime. In practice that means explicit capability-gated hostcalls, with policy/risk/quota enforcement and runtime telemetry/auditability. In order to do all this, I had to effectively build the missing runtime substrate from scratch in Rust, not just translate TypeScript syntax: - define and implement a typed hostcall ABI for extension->host interactions - build native Rust connectors for tool/exec/http/session/ui/events instead of ambient Node/Bun access - implement a compatibility/shim layer so real-world Pi extensions still behave correctly - add capability policy evaluation, runtime risk scoring, per-extension quotas, and audit telemetry on the execution path - wire the whole thing through structured concurrency (asupersync) so cancellation/lifetimes are deterministic and failure handling is explicit - build a conformance + benchmark harness large enough to validate behavior/perf across hundreds of extensions and realistic long-session workloads This was a full re-architecture of the execution model while preserving the Pi workflow and extension ecosystem. And indeed, this aspect of it dwarfs the entire rest of the project in size and complexity. To put hard numbers on that: the extension/runtime/security subsystem alone is now about 86.5k lines of Rust across src/extensions.rs (~48.1k), src/extensions_js.rs (~23.4k), src/extension_dispatcher.rs (~13.4k), and src/extension_index.rs (~1.7k), with roughly 2.5k callable units in just those files. For context, the original Pi coding-agent production code is about 27.4k lines total. So this one subsystem by itself is roughly 3.2x the size of the original harness, which is why calling this a “port” would seriously undersell what had to be built. And on top of that, pi_agent_rust introduces a bunch of genuinely new capabilities beyond the legacy harness, not just a faster core: - Security and enforcement are materially stronger at runtime: capability-gated hostcalls with explicit policy profiles (safe/balanced/permissive), per-extension trust lifecycle (pending -> acknowledged -> trusted -> killed), explicit kill-switch operations, and audited state transitions. - Shell execution mediation is deterministic and argument-aware: rule/feature-based risk scoring plus heredoc AST inspection (dcg_rule_hit, dcg_heredoc_hit) before spawn, instead of relying on coarse deny patterns. - Containment and forensics are first-class: tamper-evident runtime risk ledger tooling (verify/replay/calibrate), unified incident evidence bundles, and forced-compat controls that let you contain issues without disabling the whole extension system. - The extension runtime architecture is native: JS extensions run in embedded QuickJS with typed hostcall boundaries and Rust-native connectors for tool/exec/http/session/ui/events, plus compatibility shims for real-world legacy extensions. - Runtime behavior under load is explicitly engineered: deterministic hostcall reactor mesh, fast-lane vs compat-lane routing, and warm-isolate prewarm handoff for more predictable throughput and latency under contention. - Long-session reliability is upgraded: JSONL v3 sessions with indexed sidecar acceleration and optional SQLite-backed sessions, plus operational controls via --session-durability, --no-migrations, and migrate. - Provider and auth coverage are broader and more operationally explicit: native Anthropic/OpenAI (Chat + Responses)/Gemini/Cohere/Azure/Bedrock/Vertex/Copilot/GitLab plus large OpenAI-compatible routing; pi --list-providers currently shows 90 providers with aliases and required auth env keys. - Auth is not just API keys: OAuth (Anthropic/OpenAI Codex/Gemini CLI/Antigravity/Kimi/Copilot/GitLab plus extension-defined OAuth), AWS credential chains (Bedrock), service-key exchange (SAP AI Core), and bearer-token flows. - Operator tooling is stronger: pi doctor supports scoped checks (config, dirs, auth, shell, sessions, extensions), machine-readable output (--format json|markdown), and safe auto-remediation (--fix). - Extension/package lifecycle workflows are built in: install, remove, update, update-index, search, info, and list. I want to thank Mario for making a great harness and for not telling me to get lost when I asked him if he was OK with me porting it to Rust. I may give him a hard time in jest about not going "full clanker," but that doesn't mean that I don't respect his work a huge amount. PS: There could still be bugs. If you find some, please let me know in GitHub Issues and I'll fix them same day. There's always a tradeoff between perfect and getting stuff out the door and I felt like it was time to release this.
0:38

I finally finished my Rust version of Mario Zechner's (Mario Zechner) excellent Pi Agent, which I made with his blessing and which is called pi_agent_rust. You can get it here: If you're not familiar with Pi, it's a minimalist and extensible agent harness (similar to Claude Code and Codex) and, among other uses, serves as the core agent harness inside the OpenClaw project. I say my Rust "version" instead of "port" because it's really quite different in how it's implemented for it to be called a port. Arguably, the incremental functionality in the implementation was more complex than the rest of the project combined. Still, it provides the same features and functionality as the original, and is proven to be compatible with hundreds of popular extensions to Pi (the conformance harness shows 224 out of 224 extensions working perfectly). But the way it's architected has some major changes. Pi Agent relies on node or bun to provide access to the filesystem and for various other tasks, and that is also how Pi's extension system works. I decided early on that I didn't want to do things that way. Instead, I wanted to integrate that functionality directly into the binary itself; that is, to provide equivalent functionality for everything that would normally be provided by node/bun in the original. I did this for several reasons: one, it's a lot more performant in terms of footprint and latency. On realistic end-to-end large-session workloads (not toy microbenchmarks), pi_agent_rust is now: - 4.95x faster than legacy Node and 2.80x faster than legacy Bun at 1mm-token session scale - 4.32x faster than legacy Node and 2.14x faster than legacy Bun at 5mm-token session scale - ~8x to ~13x lower RSS memory footprint in those same scenarios But the other reason is security and control: by handling everything internally in an end-to-end way, we can do all sorts of clever things to harden the system against insecure or malicious extensions. Those extensions no longer have direct access to the ambient filesystem: they now need to go through pi_agent_rust, and we can analyze extensions carefully before ever running them and also block things that look suspicious at runtime. In practice that means explicit capability-gated hostcalls, with policy/risk/quota enforcement and runtime telemetry/auditability. In order to do all this, I had to effectively build the missing runtime substrate from scratch in Rust, not just translate TypeScript syntax: - define and implement a typed hostcall ABI for extension->host interactions - build native Rust connectors for tool/exec/http/session/ui/events instead of ambient Node/Bun access - implement a compatibility/shim layer so real-world Pi extensions still behave correctly - add capability policy evaluation, runtime risk scoring, per-extension quotas, and audit telemetry on the execution path - wire the whole thing through structured concurrency (asupersync) so cancellation/lifetimes are deterministic and failure handling is explicit - build a conformance + benchmark harness large enough to validate behavior/perf across hundreds of extensions and realistic long-session workloads This was a full re-architecture of the execution model while preserving the Pi workflow and extension ecosystem. And indeed, this aspect of it dwarfs the entire rest of the project in size and complexity. To put hard numbers on that: the extension/runtime/security subsystem alone is now about 86.5k lines of Rust across src/extensions.rs (~48.1k), src/extensions_js.rs (~23.4k), src/extension_dispatcher.rs (~13.4k), and src/extension_index.rs (~1.7k), with roughly 2.5k callable units in just those files. For context, the original Pi coding-agent production code is about 27.4k lines total. So this one subsystem by itself is roughly 3.2x the size of the original harness, which is why calling this a “port” would seriously undersell what had to be built. And on top of that, pi_agent_rust introduces a bunch of genuinely new capabilities beyond the legacy harness, not just a faster core: - Security and enforcement are materially stronger at runtime: capability-gated hostcalls with explicit policy profiles (safe/balanced/permissive), per-extension trust lifecycle (pending -> acknowledged -> trusted -> killed), explicit kill-switch operations, and audited state transitions. - Shell execution mediation is deterministic and argument-aware: rule/feature-based risk scoring plus heredoc AST inspection (dcg_rule_hit, dcg_heredoc_hit) before spawn, instead of relying on coarse deny patterns. - Containment and forensics are first-class: tamper-evident runtime risk ledger tooling (verify/replay/calibrate), unified incident evidence bundles, and forced-compat controls that let you contain issues without disabling the whole extension system. - The extension runtime architecture is native: JS extensions run in embedded QuickJS with typed hostcall boundaries and Rust-native connectors for tool/exec/http/session/ui/events, plus compatibility shims for real-world legacy extensions. - Runtime behavior under load is explicitly engineered: deterministic hostcall reactor mesh, fast-lane vs compat-lane routing, and warm-isolate prewarm handoff for more predictable throughput and latency under contention. - Long-session reliability is upgraded: JSONL v3 sessions with indexed sidecar acceleration and optional SQLite-backed sessions, plus operational controls via --session-durability, --no-migrations, and migrate. - Provider and auth coverage are broader and more operationally explicit: native Anthropic/OpenAI (Chat + Responses)/Gemini/Cohere/Azure/Bedrock/Vertex/Copilot/GitLab plus large OpenAI-compatible routing; pi --list-providers currently shows 90 providers with aliases and required auth env keys. - Auth is not just API keys: OAuth (Anthropic/OpenAI Codex/Gemini CLI/Antigravity/Kimi/Copilot/GitLab plus extension-defined OAuth), AWS credential chains (Bedrock), service-key exchange (SAP AI Core), and bearer-token flows. - Operator tooling is stronger: pi doctor supports scoped checks (config, dirs, auth, shell, sessions, extensions), machine-readable output (--format json|markdown), and safe auto-remediation (--fix). - Extension/package lifecycle workflows are built in: install, remove, update, update-index, search, info, and list. I want to thank Mario for making a great harness and for not telling me to get lost when I asked him if he was OK with me porting it to Rust. I may give him a hard time in jest about not going "full clanker," but that doesn't mean that I don't respect his work a huge amount. PS: There could still be bugs. If you find some, please let me know in GitHub Issues and I'll fix them same day. There's always a tradeoff between perfect and getting stuff out the door and I felt like it was time to release this.

Jeffrey Emanuel

136,133 görüntüleme • 7 ay önce

Maple is preparing for the release of a co-working agent. You install it locally and it works with your files, whether it's office work or building websites and apps. It's a turnkey solution, as easy as Claude Code, that keeps your data secure and private, no data sharing with closed AI labs. This is THE sovereign AI app for individuals and businesses who want powerful AI while retaining ownership of their information. Why build an agent into the Maple app when other agents already exist? Easy, we want to give you control over your work. We don't have a business plan that incorporates making money off our users' data. In the age of AI, your information, whether it's personal or company trade secrets, is the single thing that differentiates you from everyone else. We all have access to AI that can build a professional website for selling shoes. But your strategy and network for how you sell shoes should not be shared with your competitors. Sovereignty is the path to protecting what makes you, you. Maple sits at the intersection of Usability and Sovereignty. Maple gives you the best tools that are both easy to use and maintain your data sovereignty. Sovereign for one, sovereign for all. It has been a journey to get here. We brought to market the very first personal chatbot with end-to-end encryption using TEEs in late 2024. Prior to that there were proofs of concept but no full product offerings. Every other AI chat product on the market handled your data in plain text, either selling you a service to get your data or asking you to trust that they won't snoop on you. Quickly people found Maple and latched onto its open-source code and verifiable encryption. We didn't stop there. You may remember earlier this year we teased a product called "Maple Agent" and opened up a waiting list. That product is a mobile app that acts as your AI "friend", maintaining one long continuous chat, and getting to know you over time. I dislike using the word "friend" there, but it's the best way to convey the UX in a few words. AI is a tool, always has been, always will be. Any kind of friendly personality on top is just synthetic. In our testing, the UX of Maple Agent is really powerful for what it does. Think about the many short AI chats you have in your favorite app, whether it's looking up a historical fact or asking advice about a topic. With Maple Agent, those all go away in favor of the long-running chat with the friendly agent. It's like you have your own personal assistant who knows you so well and can look up anything for you. When I ask AI certain questions, I want to ask an expert who already understands my situation so I'm not repeating myself for the 100th time. That's the amazing value the personal agent brings to the table. We still see great utility for a personal agent like the "Maple Agent". Thousands of people on the waiting list, hoping to get their hands on it, agree that the concept is worth exploring and trying out. We were constrained in launching it due to a few circumstances, one of them being access to the scale of compute needed to power it. We have a clear path laid out for how to get there, but today is not the day to execute on that. It will be in the near future. Instead we have a different agent ready to go that we think is also incredible. We now have an agentic harness inside of the Maple Research app. This thing is a powerhouse. It even builds and publishes its own software releases. The agent in Maple Research works with your local filesystem, speaks to the largest open models running in TEEs, utilizes local models for certain tasks, is compatible with MCP tools, has an API for connecting to anything you need, and also supports the ACP protocol, which means it can be extended in the future to speak to other tools like Claude Code, Codex, and local models running on your own hardware. A big unlock for us was the Goose Development Kit, which powers the core of our agent harness. More on that to come as we publish articles and documentation later about the agent. The agent inside Maple Research doesn't have a name. At least not yet, not sure if it ever will. For now we call it "Chat Mode" and "Agent Mode". Think of this as the workhorse, the truck, the heavy lifter. Our other "Agent", the phone app, is your sidekick in your pocket, ready to help with quick things and ongoing conversations about life. I am incredibly excited about the Maple Research Agent. While I'm already seeing great results using it for internal work items, I'm especially thrilled about the personal health and wellness work it's doing for me. I know there are plenty of apps out there for compiling wellness data, but I'm having it build a tool tailored specifically for what I need, without the extra fluff. And none of my health data is being donated to the closed AI labs or sent to advertisers. I know that the AI logic is not being silently adjusted to fit the whims of a large corporation that has paid for product placement. It's me, state of the art AI, and my data. That's how I want it. Maple's new agent makes that possible. We can't wait for you to try it out. If you want early access, comment here, email us, reach out in some way. To those on the other agent waitlist, you're already in the queue. Thanks for reading this lengthy update. :)
0:49

Maple is preparing for the release of a co-working agent. You install it locally and it works with your files, whether it's office work or building websites and apps. It's a turnkey solution, as easy as Claude Code, that keeps your data secure and private, no data sharing with closed AI labs. This is THE sovereign AI app for individuals and businesses who want powerful AI while retaining ownership of their information. Why build an agent into the Maple app when other agents already exist? Easy, we want to give you control over your work. We don't have a business plan that incorporates making money off our users' data. In the age of AI, your information, whether it's personal or company trade secrets, is the single thing that differentiates you from everyone else. We all have access to AI that can build a professional website for selling shoes. But your strategy and network for how you sell shoes should not be shared with your competitors. Sovereignty is the path to protecting what makes you, you. Maple sits at the intersection of Usability and Sovereignty. Maple gives you the best tools that are both easy to use and maintain your data sovereignty. Sovereign for one, sovereign for all. It has been a journey to get here. We brought to market the very first personal chatbot with end-to-end encryption using TEEs in late 2024. Prior to that there were proofs of concept but no full product offerings. Every other AI chat product on the market handled your data in plain text, either selling you a service to get your data or asking you to trust that they won't snoop on you. Quickly people found Maple and latched onto its open-source code and verifiable encryption. We didn't stop there. You may remember earlier this year we teased a product called "Maple Agent" and opened up a waiting list. That product is a mobile app that acts as your AI "friend", maintaining one long continuous chat, and getting to know you over time. I dislike using the word "friend" there, but it's the best way to convey the UX in a few words. AI is a tool, always has been, always will be. Any kind of friendly personality on top is just synthetic. In our testing, the UX of Maple Agent is really powerful for what it does. Think about the many short AI chats you have in your favorite app, whether it's looking up a historical fact or asking advice about a topic. With Maple Agent, those all go away in favor of the long-running chat with the friendly agent. It's like you have your own personal assistant who knows you so well and can look up anything for you. When I ask AI certain questions, I want to ask an expert who already understands my situation so I'm not repeating myself for the 100th time. That's the amazing value the personal agent brings to the table. We still see great utility for a personal agent like the "Maple Agent". Thousands of people on the waiting list, hoping to get their hands on it, agree that the concept is worth exploring and trying out. We were constrained in launching it due to a few circumstances, one of them being access to the scale of compute needed to power it. We have a clear path laid out for how to get there, but today is not the day to execute on that. It will be in the near future. Instead we have a different agent ready to go that we think is also incredible. We now have an agentic harness inside of the Maple Research app. This thing is a powerhouse. It even builds and publishes its own software releases. The agent in Maple Research works with your local filesystem, speaks to the largest open models running in TEEs, utilizes local models for certain tasks, is compatible with MCP tools, has an API for connecting to anything you need, and also supports the ACP protocol, which means it can be extended in the future to speak to other tools like Claude Code, Codex, and local models running on your own hardware. A big unlock for us was the Goose Development Kit, which powers the core of our agent harness. More on that to come as we publish articles and documentation later about the agent. The agent inside Maple Research doesn't have a name. At least not yet, not sure if it ever will. For now we call it "Chat Mode" and "Agent Mode". Think of this as the workhorse, the truck, the heavy lifter. Our other "Agent", the phone app, is your sidekick in your pocket, ready to help with quick things and ongoing conversations about life. I am incredibly excited about the Maple Research Agent. While I'm already seeing great results using it for internal work items, I'm especially thrilled about the personal health and wellness work it's doing for me. I know there are plenty of apps out there for compiling wellness data, but I'm having it build a tool tailored specifically for what I need, without the extra fluff. And none of my health data is being donated to the closed AI labs or sent to advertisers. I know that the AI logic is not being silently adjusted to fit the whims of a large corporation that has paid for product placement. It's me, state of the art AI, and my data. That's how I want it. Maple's new agent makes that possible. We can't wait for you to try it out. If you want early access, comment here, email us, reach out in some way. To those on the other agent waitlist, you're already in the queue. Thanks for reading this lengthy update. :)

Mark

46,589 görüntüleme • 1 ay önce

Microsoft just lost $357 billion in a single day... While Meta gained $170 billion. Both companies are spending over $100 billion on AI this year. One got punished. One got rewarded. The difference tells you everything about where this market is heading: Microsoft reported Wednesday. Beat on revenue. Beat on earnings. Revenue up 17%. EPS up 24%. But the stock dropped 10% - worst decline since March 2020. Why? Azure cloud growth came in at 39%. The Street wanted 39.4%. A miss of 0.4 percentage points erased a third of a trillion dollars. Meanwhile, capex jumped 89% year-over-year to $37.5B in a single quarter. CFO Amy Hood admitted two-thirds went to "short-lived assets" - GPUs that depreciate fast. And Microsoft also said they'll remain "capacity constrained through at least the end of our fiscal year." In other words: "We're spending $72B in six months and STILL can't build data centers fast enough." But that's not the real problem... The real problem is what's happening inside Microsoft's spending. They're not just building infrastructure for Azure customers. They're allocating scarce GPUs to their own products: M365 Copilot, GitHub Copilot, internal R&D. Hood said they must "balance Azure revenue growth with growing needs across first-party apps and AI solutions." Microsoft is competing with its own cloud customers for compute capacity. If they'd allocated all new GPUs to Azure, growth would've exceeded 40%. Instead, they're betting their own AI products will generate more value than selling raw compute. That bet hasn't paid off yet. And 45% of their $625B backlog is tied to ONE customer: OpenAI. Now compare that to Meta: Revenue beat. Earnings beat. Guidance crushed expectations. And they announced $115-135B in AI capex for 2026 - nearly DOUBLE what they spent in 2025. The stock surged 10%. Why the opposite reaction? Meta is seeing immediate returns. Ad impressions up 18%. Average price per ad up 6%. Revenue up 24% year-over-year. Their AI investment is already showing up in the core business TODAY. Better ad targeting. Better recommendations. Better engagement. Q1 revenue guidance came in at $53.5-56.5B - Wall Street expected $51.4B. That's 30% revenue growth ACCELERATION. When you have 3.58B daily active users, AI improvements compound immediately. Zuckerberg called it a "major AI acceleration" and Wall Street didn't care about the $135B spending number. Because they can SEE the connection between spending and revenue. Here's what matters: The hyperscalers are now spending over $600B combined on AI infrastructure in 2026. AI assets depreciate at roughly 20% per year. The five hyperscalers face annual depreciation expenses approaching $400B - MORE than their combined profits in 2025. This is the biggest capital spending cycle in history. And we just entered Phase 3, where AI-enabled revenue models must finally prove their worth. The market stopped rewarding spending. It's rewarding RETURNS. Meta showed returns. Microsoft showed constraints and margin compression. That's why we saw a $527B swing between two companies reporting on the same day. My read: The easy money in the AI trade is over. From here, execution matters more than ambition. Companies that can turn infrastructure spending into measurable productivity gains get rewarded. Companies still building without clear payback get punished - even when they beat estimates. Microsoft isn't a bad company. It's a company that bet big on AI infrastructure and is now scrambling to show ROI before margins collapse further. Meta isn't necessarily a better AI company. It just has a business model where AI improvements translate directly to revenue growth. For investors, the lesson is clear: The AI infrastructure phase is maturing. Winners from here will be companies with clear paths from spending to earnings. Not companies asking you to trust the process while margins compress.
0:32

Microsoft just lost $357 billion in a single day... While Meta gained $170 billion. Both companies are spending over $100 billion on AI this year. One got punished. One got rewarded. The difference tells you everything about where this market is heading: Microsoft reported Wednesday. Beat on revenue. Beat on earnings. Revenue up 17%. EPS up 24%. But the stock dropped 10% - worst decline since March 2020. Why? Azure cloud growth came in at 39%. The Street wanted 39.4%. A miss of 0.4 percentage points erased a third of a trillion dollars. Meanwhile, capex jumped 89% year-over-year to $37.5B in a single quarter. CFO Amy Hood admitted two-thirds went to "short-lived assets" - GPUs that depreciate fast. And Microsoft also said they'll remain "capacity constrained through at least the end of our fiscal year." In other words: "We're spending $72B in six months and STILL can't build data centers fast enough." But that's not the real problem... The real problem is what's happening inside Microsoft's spending. They're not just building infrastructure for Azure customers. They're allocating scarce GPUs to their own products: M365 Copilot, GitHub Copilot, internal R&D. Hood said they must "balance Azure revenue growth with growing needs across first-party apps and AI solutions." Microsoft is competing with its own cloud customers for compute capacity. If they'd allocated all new GPUs to Azure, growth would've exceeded 40%. Instead, they're betting their own AI products will generate more value than selling raw compute. That bet hasn't paid off yet. And 45% of their $625B backlog is tied to ONE customer: OpenAI. Now compare that to Meta: Revenue beat. Earnings beat. Guidance crushed expectations. And they announced $115-135B in AI capex for 2026 - nearly DOUBLE what they spent in 2025. The stock surged 10%. Why the opposite reaction? Meta is seeing immediate returns. Ad impressions up 18%. Average price per ad up 6%. Revenue up 24% year-over-year. Their AI investment is already showing up in the core business TODAY. Better ad targeting. Better recommendations. Better engagement. Q1 revenue guidance came in at $53.5-56.5B - Wall Street expected $51.4B. That's 30% revenue growth ACCELERATION. When you have 3.58B daily active users, AI improvements compound immediately. Zuckerberg called it a "major AI acceleration" and Wall Street didn't care about the $135B spending number. Because they can SEE the connection between spending and revenue. Here's what matters: The hyperscalers are now spending over $600B combined on AI infrastructure in 2026. AI assets depreciate at roughly 20% per year. The five hyperscalers face annual depreciation expenses approaching $400B - MORE than their combined profits in 2025. This is the biggest capital spending cycle in history. And we just entered Phase 3, where AI-enabled revenue models must finally prove their worth. The market stopped rewarding spending. It's rewarding RETURNS. Meta showed returns. Microsoft showed constraints and margin compression. That's why we saw a $527B swing between two companies reporting on the same day. My read: The easy money in the AI trade is over. From here, execution matters more than ambition. Companies that can turn infrastructure spending into measurable productivity gains get rewarded. Companies still building without clear payback get punished - even when they beat estimates. Microsoft isn't a bad company. It's a company that bet big on AI infrastructure and is now scrambling to show ROI before margins collapse further. Meta isn't necessarily a better AI company. It just has a business model where AI improvements translate directly to revenue growth. For investors, the lesson is clear: The AI infrastructure phase is maturing. Winners from here will be companies with clear paths from spending to earnings. Not companies asking you to trust the process while margins compress.

George Noble

120,301 görüntüleme • 7 ay önce

I've never heard Elon Musk be so bullish on Tesla ⚡️ here's my video analysis of the $TSLA Q4 2024 earnings call: -Robotaxi launch in Austin, June 2025 -California & other states launch robotaxi late 2025 -Cybercab in 2026 -Optimus V1 in 2025, 1K/month production line -Optimus V2 in 2026, 10K/month production line -2026 good year for Tesla, 2027/28 insanely good & more!! Timestamps- 0:00 Intro 0:44 Elon Opening Remarks 13:29 SAY Retail Questions 22:37 Analyst Questions 25:04 Gali Final Thoughts/Rant also here are my notes I typed during the conference call if you're interested! (may be errors) Tesla Q4 2024 Earnings Call Notes INTRO- ELON OPENING REMARKS -Q4 set record, delivered cars at rate of almost 2M cars/year -Model Y best-selling vehicle of any kind on earth (elon focused and talking quickly) -10Xing on autonomy, not doubling -many investments made this year that will bear immense fruit in the future, for AI -see a path for Tesla to the worlds most valuable company by far, worth more than the next 5 companies combined, difficult but achievable path -overwhelmingly due to autonomous vehicles and autonomous robots -setting up for an epic 2026, and ridiculously good 2027 and 2028 -meeting FSD now is like meeting a toddler -human intuition is linear, we’re seeing exponential progress -#1 recommendation is try it -typical passenger car has 10 hours of use out of 168, when its autonomous, itll be used for 55 hours a week … can deliver packages in the middle of thenight, or supply restaurants, all hours of the day or night. 5X increase in utility -more on self driving, continued improvements in safety numbers, much safer to use FSD -V14 will be another big step from V13 -launched CORTEX training cluster at Giga Austin, big step for FSD, continue to invest in training needs -Optimus training needs are about 10X what’s needed for the car -cost of training is dropping dramatically over time -Optimus has potential to be north of $10T in revenue, can put a lot training compute into that situation, even pumping $500B into it would be a good deal -future very different from the past, incredible inflection point in human history -proof is in the pudding -launching in June this year in Austin, already have cars moving autonomously in Fremont, thousands of cars per day driving, soon in Austin then elsewhere in the world -toe in the water at first to make sure everything is cool, but we have a general solution for autonomy , then put a few more toes, then a foot. Safety of the general public and those in the car as the top priority -with regard to Optimus, making insane revenue projections that sound insane, i realize that. But i think they will prove to be accurate -several thousand bots made this year, they will be doing useful things by the end of this year, im confidence, production design one at the tesla factories, then will learn for production design two -ramp optimus production faster than anything has ever launched, doesn’t take very many years before we’er making 100M of these things per year , 500% growth per year -tried using all these suppliers to get it to build Optimus, but nothing worked, had to build it internally from first principles, the hand is increibdle -long term Optimus will be the value of the company -back to Energy,/earth, -energy storage is a big deal, becoming more important, enables far greater energy output to the grid than is currently possible. -grid has no storage, designed for peak storage, lots of waste -once you have grid energy storage, the potential of the grid is unlocked, at least double -this will drive demand of battery packs as to as much as we can possibly make -shanghai factory starting operation, starting another factory -cant shoot our selves in the foot, battery capacity can only go into storage or mobility, so always making that tradeoff -demand for total Gigawatt hours for batteries, transportation or stationary will grow in a very big way over time 2025 a pivotal year for tesla, launch of full self driving, biggest year in tesla history, maybe even bigger than first car or model s, 3 or y … probably most important year in tesla’s history I don’t even know who is in 2nd place in real world AI, would need a telescope to see them SAY QUESTIONS -FSD Unsupervised launched in California this year as well -most likely release it in many regions of the US by the end of this year -40K people day everyday no mention, some scrapes a shin with autonomous car its headlines news -need to use insane amounts of caution -discussions about licensing FSD? Yes -best way to know to work with us, bbuy a car and take it apart -only worth very high volume cars/production partners -tesla engineering very focused on getting it to roll out for tesla first -soon will be obvious that if you don’t have FSD you’re dead as an OEM -is Optimus design locked? -Optimus is not design locked, constantly iterating, best robotics engineers in the world, and other ingredients, battery pack, charging, great electronics, great communications, great connectivity, real world AI, then you need to scale that production to real world levels -prototypes are easy production is hard -thijs year close loop with using optimus internally at tesla, would could obviously use a few thousand robots for the most boring annoying tasks at the company -with production version 2, launches sometime next year, would like beginning, might be middle though, -production line will be doing 10K units per month capacity for v2, first line designing is for roughly 1,000 units per month, then next line will be for 100,000 units per month -could start delivering them late next year, will go so fast, will ramp like crazy, demand will not be a problem, even at a high price, once were above 1M units per year, production costs of optimus will be less than $20,000 -if you compare complexity of optimus to complexity of a car, its much less than a car -price of optimus will be set buy market demand -Semi ramping next year, TCO no brainer, like optimus, will be massive demand, will meaningfully contribute to tesla’s revenue at scale -tesla semi with autonomy, is incredibly valuable -we actually have a shortage of truck drivers here in the US -will HW3 owners need a hardware update, got 12.6 which is like a baby v13, have’t given up on it, releases will trail HW4 releases … “honest answer” is were going to have to upgrade for those who have bought full self driving, will be painful and difficult and we’ll get it done “Happy not many people bought FSD” -solar roof, given up on ramping it? -lots of customer interest despite premium, making easier to install, focused on growth through certified installers, many been installing for many years -supply product to the roofing industry -it’s a premium product like S/X -combined with Tesla powerwall you can be self sufficient for several days ANALYST QUETIONS -robotaxis in Austin and several other cities this year, and next year all over america -america innovates, europe regulates, to release FSD in europe, have to go through massive paperwork through netherlands, then presents to EU in may, some big country committee, nothing we can do to make it happen sooner. -can’t do training in china with video training, publicly available videos in china are being run through the tesla system to be used for training, bus lanes are complicated and a big challenge -tesla can keep manufacturing even if geopolitical tensions rise to very high levels -Pierre question on June in Austin, -can i try unsupervised myself, or will it be the Tesla fleet? -it will be the Tesla fleet testing it, that’s the toe in the water, scrutinizing everything -autonomous ride hailing for money in june -probably next year for you to put your car on network -trump removing EV incentives? -all transport will go electric, can’t be stopped, even planes, will be like stopping the steam engine or combustion engine -only thing holding back EVs was range, and thats a solved problem -right now solving battery production, not demand, big battery retooling for model y coming up, short term impact on output
33:55

I've never heard Elon Musk be so bullish on Tesla ⚡️ here's my video analysis of the $TSLA Q4 2024 earnings call: -Robotaxi launch in Austin, June 2025 -California & other states launch robotaxi late 2025 -Cybercab in 2026 -Optimus V1 in 2025, 1K/month production line -Optimus V2 in 2026, 10K/month production line -2026 good year for Tesla, 2027/28 insanely good & more!! Timestamps- 0:00 Intro 0:44 Elon Opening Remarks 13:29 SAY Retail Questions 22:37 Analyst Questions 25:04 Gali Final Thoughts/Rant also here are my notes I typed during the conference call if you're interested! (may be errors) Tesla Q4 2024 Earnings Call Notes INTRO- ELON OPENING REMARKS -Q4 set record, delivered cars at rate of almost 2M cars/year -Model Y best-selling vehicle of any kind on earth (elon focused and talking quickly) -10Xing on autonomy, not doubling -many investments made this year that will bear immense fruit in the future, for AI -see a path for Tesla to the worlds most valuable company by far, worth more than the next 5 companies combined, difficult but achievable path -overwhelmingly due to autonomous vehicles and autonomous robots -setting up for an epic 2026, and ridiculously good 2027 and 2028 -meeting FSD now is like meeting a toddler -human intuition is linear, we’re seeing exponential progress -#1 recommendation is try it -typical passenger car has 10 hours of use out of 168, when its autonomous, itll be used for 55 hours a week … can deliver packages in the middle of thenight, or supply restaurants, all hours of the day or night. 5X increase in utility -more on self driving, continued improvements in safety numbers, much safer to use FSD -V14 will be another big step from V13 -launched CORTEX training cluster at Giga Austin, big step for FSD, continue to invest in training needs -Optimus training needs are about 10X what’s needed for the car -cost of training is dropping dramatically over time -Optimus has potential to be north of $10T in revenue, can put a lot training compute into that situation, even pumping $500B into it would be a good deal -future very different from the past, incredible inflection point in human history -proof is in the pudding -launching in June this year in Austin, already have cars moving autonomously in Fremont, thousands of cars per day driving, soon in Austin then elsewhere in the world -toe in the water at first to make sure everything is cool, but we have a general solution for autonomy , then put a few more toes, then a foot. Safety of the general public and those in the car as the top priority -with regard to Optimus, making insane revenue projections that sound insane, i realize that. But i think they will prove to be accurate -several thousand bots made this year, they will be doing useful things by the end of this year, im confidence, production design one at the tesla factories, then will learn for production design two -ramp optimus production faster than anything has ever launched, doesn’t take very many years before we’er making 100M of these things per year , 500% growth per year -tried using all these suppliers to get it to build Optimus, but nothing worked, had to build it internally from first principles, the hand is increibdle -long term Optimus will be the value of the company -back to Energy,/earth, -energy storage is a big deal, becoming more important, enables far greater energy output to the grid than is currently possible. -grid has no storage, designed for peak storage, lots of waste -once you have grid energy storage, the potential of the grid is unlocked, at least double -this will drive demand of battery packs as to as much as we can possibly make -shanghai factory starting operation, starting another factory -cant shoot our selves in the foot, battery capacity can only go into storage or mobility, so always making that tradeoff -demand for total Gigawatt hours for batteries, transportation or stationary will grow in a very big way over time 2025 a pivotal year for tesla, launch of full self driving, biggest year in tesla history, maybe even bigger than first car or model s, 3 or y … probably most important year in tesla’s history I don’t even know who is in 2nd place in real world AI, would need a telescope to see them SAY QUESTIONS -FSD Unsupervised launched in California this year as well -most likely release it in many regions of the US by the end of this year -40K people day everyday no mention, some scrapes a shin with autonomous car its headlines news -need to use insane amounts of caution -discussions about licensing FSD? Yes -best way to know to work with us, bbuy a car and take it apart -only worth very high volume cars/production partners -tesla engineering very focused on getting it to roll out for tesla first -soon will be obvious that if you don’t have FSD you’re dead as an OEM -is Optimus design locked? -Optimus is not design locked, constantly iterating, best robotics engineers in the world, and other ingredients, battery pack, charging, great electronics, great communications, great connectivity, real world AI, then you need to scale that production to real world levels -prototypes are easy production is hard -thijs year close loop with using optimus internally at tesla, would could obviously use a few thousand robots for the most boring annoying tasks at the company -with production version 2, launches sometime next year, would like beginning, might be middle though, -production line will be doing 10K units per month capacity for v2, first line designing is for roughly 1,000 units per month, then next line will be for 100,000 units per month -could start delivering them late next year, will go so fast, will ramp like crazy, demand will not be a problem, even at a high price, once were above 1M units per year, production costs of optimus will be less than $20,000 -if you compare complexity of optimus to complexity of a car, its much less than a car -price of optimus will be set buy market demand -Semi ramping next year, TCO no brainer, like optimus, will be massive demand, will meaningfully contribute to tesla’s revenue at scale -tesla semi with autonomy, is incredibly valuable -we actually have a shortage of truck drivers here in the US -will HW3 owners need a hardware update, got 12.6 which is like a baby v13, have’t given up on it, releases will trail HW4 releases … “honest answer” is were going to have to upgrade for those who have bought full self driving, will be painful and difficult and we’ll get it done “Happy not many people bought FSD” -solar roof, given up on ramping it? -lots of customer interest despite premium, making easier to install, focused on growth through certified installers, many been installing for many years -supply product to the roofing industry -it’s a premium product like S/X -combined with Tesla powerwall you can be self sufficient for several days ANALYST QUETIONS -robotaxis in Austin and several other cities this year, and next year all over america -america innovates, europe regulates, to release FSD in europe, have to go through massive paperwork through netherlands, then presents to EU in may, some big country committee, nothing we can do to make it happen sooner. -can’t do training in china with video training, publicly available videos in china are being run through the tesla system to be used for training, bus lanes are complicated and a big challenge -tesla can keep manufacturing even if geopolitical tensions rise to very high levels -Pierre question on June in Austin, -can i try unsupervised myself, or will it be the Tesla fleet? -it will be the Tesla fleet testing it, that’s the toe in the water, scrutinizing everything -autonomous ride hailing for money in june -probably next year for you to put your car on network -trump removing EV incentives? -all transport will go electric, can’t be stopped, even planes, will be like stopping the steam engine or combustion engine -only thing holding back EVs was range, and thats a solved problem -right now solving battery production, not demand, big battery retooling for model y coming up, short term impact on output

Gali

79,010 görüntüleme • 1 yıl önce

i spent the morning tracing the whole thing on dune and the story is interesting + worth sharing. drainer wallet: 0xF7cFFC27732a5C9c4E2D592F3E33435F8dDb019A: fresh wallet, first tx ever was today 2026-05-11 at 00:52 utc. by 01:27 utc it had pulled ~$173k of assets + some memecoins from at least 5 different wallets on ethereum, base, and bsc. drained wallets: > 0x62acE10c…EE8A: ~$30k of priced assets (eth + bnb) + memecoins, drained across base / eth / bsc > 0x6131b5fae19ea4f9d964eac0408e4408b66337b5: ~$119k (eth), drained across eth + base it's clear that is not an approval/permit exploit. it's a private-key compromise. at 00:53 your wallet sent 5.8 eth to the drainer. 3 minutes later, the drainer sent 0.02 eth back to you. a few minutes after that, a 157k sat1 erc20 transfer left your wallet to the drainer. that 0.02 eth transfer was the attacker funding gas in the compromised wallet so it could keep signing transfers. the only way to make that happen is to control the wallet directly. so the attacker is signing transactions with your seed. and the part that really bothers me: among the wallets that sent funds INTO the drainer, 3 more share the exact same 8 hex chars at the same positions (62ac start, ee8a end): > 0x62ace0e0ecf70f62399b26e28eaf74cc455bee8a > 0x62ac07ae9242c354f6c307bbd9b36c749a5aee8a > 0x62ac6095d7e9189353bcbf17d439348ab7a1ee8a the 32 middle chars are completely different on each, so these are 4 genuinely distinct wallets. finding 4 wallets that all share the EXACT same 8 chars in the EXACT same positions by accident is statistically impossible. they were generated by a vanity tool specifically programmed to hunt for that shape. only your wallet sent priced assets to the drainer. the other three 62ac…ee8a wallets only sent worthless coins. these 3 don't look like victim wallets at all. looks like the attacker spent a few gpu-hours generating wallets that match the shape of your main address, then routed some of the worthless memecoins through them. why? idk, maybe: > address poisoning > trail confusion where the money is right now: most of it is still in the drainer wallet. the attacker is dumping the stolen memecoins (pod, sat1, fhe, bort, etc) into Kyberswap. but eth and bnb are just sitting there. nothing has been pushed to a cex deposit, bridged out, or sent to a mixer. once those funds hit binance/okx/bybit deposits or a tornado contract, recovery will be near-impossible. how the seed potentially leaked: > infostealer malware on the device (lumma, redline, atomic) grabbing the seed during one of the imports. these are extremely common right now and seeds in clipboard or saved as plaintext are easy pickings. > malicious browser extension intercepting the seed at paste-time into rabby or gmgn > fake support DM earlier tricking you into pasting a seed into a phishing page you didn't remember here is the dune dashboard that summarizes everything i’ve found.:
0:25

i spent the morning tracing the whole thing on dune and the story is interesting + worth sharing. drainer wallet: 0xF7cFFC27732a5C9c4E2D592F3E33435F8dDb019A: fresh wallet, first tx ever was today 2026-05-11 at 00:52 utc. by 01:27 utc it had pulled ~$173k of assets + some memecoins from at least 5 different wallets on ethereum, base, and bsc. drained wallets: > 0x62acE10c…EE8A: ~$30k of priced assets (eth + bnb) + memecoins, drained across base / eth / bsc > 0x6131b5fae19ea4f9d964eac0408e4408b66337b5: ~$119k (eth), drained across eth + base it's clear that is not an approval/permit exploit. it's a private-key compromise. at 00:53 your wallet sent 5.8 eth to the drainer. 3 minutes later, the drainer sent 0.02 eth back to you. a few minutes after that, a 157k sat1 erc20 transfer left your wallet to the drainer. that 0.02 eth transfer was the attacker funding gas in the compromised wallet so it could keep signing transfers. the only way to make that happen is to control the wallet directly. so the attacker is signing transactions with your seed. and the part that really bothers me: among the wallets that sent funds INTO the drainer, 3 more share the exact same 8 hex chars at the same positions (62ac start, ee8a end): > 0x62ace0e0ecf70f62399b26e28eaf74cc455bee8a > 0x62ac07ae9242c354f6c307bbd9b36c749a5aee8a > 0x62ac6095d7e9189353bcbf17d439348ab7a1ee8a the 32 middle chars are completely different on each, so these are 4 genuinely distinct wallets. finding 4 wallets that all share the EXACT same 8 chars in the EXACT same positions by accident is statistically impossible. they were generated by a vanity tool specifically programmed to hunt for that shape. only your wallet sent priced assets to the drainer. the other three 62ac…ee8a wallets only sent worthless coins. these 3 don't look like victim wallets at all. looks like the attacker spent a few gpu-hours generating wallets that match the shape of your main address, then routed some of the worthless memecoins through them. why? idk, maybe: > address poisoning > trail confusion where the money is right now: most of it is still in the drainer wallet. the attacker is dumping the stolen memecoins (pod, sat1, fhe, bort, etc) into Kyberswap. but eth and bnb are just sitting there. nothing has been pushed to a cex deposit, bridged out, or sent to a mixer. once those funds hit binance/okx/bybit deposits or a tornado contract, recovery will be near-impossible. how the seed potentially leaked: > infostealer malware on the device (lumma, redline, atomic) grabbing the seed during one of the imports. these are extremely common right now and seeds in clipboard or saved as plaintext are easy pickings. > malicious browser extension intercepting the seed at paste-time into rabby or gmgn > fake support DM earlier tricking you into pasting a seed into a phishing page you didn't remember here is the dune dashboard that summarizes everything i’ve found.:

The Smart Ape 🔥

52,233 görüntüleme • 4 ay önce

If you watch this ~50 minute screen recording closely (yeah, I know, it's long; there are also some times when my computer was very slow and laggy, just skip past that part. And at one point I had to run and get my 9-month-old a new bottle and left it on a boring screen, sorry!), I believe you can see real signs of the kind of runaway, recursive AI self-improvement that people have been warning of for a while (Mr. Kurzweil most notably and prophetically). Why do I say that? What's different now? Well, there's a reason my set of agent coding tooling is called the Flywheel. These tools all mutually self-reinforce each other. And they all flow directly into my ntm tool (short for "named_tmux_manager"), which acts as a sort of integration point and nerve center for the tools (this is becoming more true by the minute as I'm now seriously working on ntm). Now, ntm was something I started making to automate some aspects of my workflow, but it was the kind of thing where, until it was perfect, it sort of just slowed me down. So I didn't actually use it even though I kept working on it and trying to improve it, and suggested to users that they try it in my tutorials. Well anyway, I finally got around to "dogfooding" ntm last night, and now it's going to get very dramatically better at an alarming rate. Some of that is from applying my "idea wizard" prompt to generate more useful features and building that stuff out and addressing obvious pain points I encountered during my newfound usage of the tool. But a lot comes from my realization that, once again, ntm's true utility is not as a tool for ME, but for an agent. That is, ntm lets one instance of Claude Code or Codex act as, well, me, do the things that I had been doing manually. Do I wish I had started using ntm earlier? No, for two big reasons: 1) Doing it manually helped me build up my intuition massively, which directly led me down the path of creating useful prompt strategies and workflows; these often began as ad-hoc prompts that I realized could be generalized and made more versatile/universal. Lesson: don't prematurely automate until you have an intimate, intuitive feel for your "core value-add loop." Otherwise you'll have a fully automated system quickly that efficiently and automatically does a stupid or otherwise sub-optimal thing. 2) My eyes have been opened to the beauty and power of Skills. I'm not talking about your garden-variety skills that are just a simple markdown file. I'm talking about true tour-de-force directories of perfectly structured and organized files that are filled with good information, insights, workflows, etc., but presented in a way that is highly optimized for consumption by AI agents, with extreme attention paid to things like perfect progressive disclosure, token density, agent-ergonomics, agent-intuitiveness, etc. And also Skills that go way beyond markdown files, with full integration into Claude Code where it makes sense via hooks, sub-agents, and even Python scripts. These kinds of skills are a qualitative difference in expressive power and usefulness and a total game changer. They are also effectively composable, creating almost an algebra of skills that let you use them together in powerful ways. I'm working on a subscription service website and CLI tool now to share what I've learned here most effectively, stay tuned for that in the coming days. Anyway, I now know what to make and how to make it. So, getting back to that screen recording, what does it show that makes me claim recursive self-improvement is here? If you keep your eye on the upper left tmux pane, that's the "controller" agent. It is using ntm to control all the other panes which are also running Claude Code (but ntm fully supports other agent types like Codex and Gemini-CLI, and it's trivially easy to mix and match them if you wanted to have, say, 8 CCs and 6 Codexes for writing the code and 3 Gemini-CLIs for reviewing code.) Now, there's nothing that crazy about this much so far. But where it starts to get very cool is that as the session continues and we encounter real-world problems, things like my ridiculously overloaded computer that keeps hanging for long periods, Claude Code instances that crash and get into a frozen, unresponsive state, it can learn from that. And you can see it using my skill writing skill to refine its ntm vibe coding skill in real time. And then take that skill and refine it to be more intuitive for itself. Or use my cass tool skill to search all the session histories to look for problems that came up and strategize how to solve them. The most useful part was when, towards the end of the session, I told it to reflect on all the things we had done and problems we encountered. One way it can usefully leverage those reflections is by improving its ntm vibe coding skill to make it cover more edge cases and exigencies. But the other, more fundamental, way is for it to conceive of and design the optimal new features and functionality for ntm itself so that the tool embodies those lessons in a first-class way. This offloads cognition from its brain onto its tooling, just like how a person can lean on spellcheck or a calculator. It codifies correct, effective reasoning at the tool level, where it's more reliable and robust and repeatable. And btw, did you notice what code base it was working on the whole time? It was none other than ntm itself! So as it worked on its own tool, it had reflections and ideas about how to further improve the tool. Now, it could have just as easily gotten those insights and ideas while using ntm to work on a different project, but the fact that it was working on itself is almost gloriously meta and recursive. So by the end, after learning from tending to a big group of agent workers (btw, I have previously emphasized doing everything in a really distributed/decentralized way, where each fungible agent gets identical marching orders that tell it to use my bv tool to find the optimal bead to work on. This does work very well, but occasionally results in some contention and overlap from thundering herd, or at least wastes time/tokens/communication in avoiding that before the agents waste time duplicating work. But in this new ntm-oriented workflow, I was able to have the controller agent in the upper left use bv itself and then optimally parcel out the instructions to each agent so that we could know for sure that there's no overlap), I ended up with a ton of new beads for new features, which I had it optimize and polish a few times. Now I can swap to a new Claude Max account and have the swarm implement all those new features! It should only take a couple passes like the one shown in the screen recording to get everything implemented. Then we can rinse and repeat, having the agent read through the full session histories of each agent and its experience from its own session in sending ntm commands and seeing how they worked out in practice, to come up with the next batch of changes to both its ntm vibe coding skill AND to the ntm tool itself. Do you see how rapidly this turns into Skynet? My mistake earlier was in focusing on making myself a "faster horse" as Henry Ford used to joke about customers wanting before he showed them what they should really want (a Model T). That is, something that would make my experience nicer while doing this agent swarm based development workflow. But the obvious lesson is that you should make all your tooling agent-first because the agents are just better at this stuff. You can still watch, and of course I did add a ridiculous number of very nice human-centric features to ntm that you'll be seeing in the next day or two, but those are really kind of "for fun" to make us humans feel better about the process. All the real value-add is happening "by agents, for agents." PS: Towards the end, you can see me switch to my Mac and tell Claude to improve the skill that I made earlier today for taking the mkv screen recording files from OBS Studio and muxing them into MP4 files for sharing, while downloading songs from YouTube to serve as the background music. I made it so it can also grab the thumbnails and generate little song credit cards that show up in the lower right corner. This worked perfectly the first time! I'll include some screenshots in a response post showing how that worked, but it was awesome to witness. Skills are POWERFUL. I'll also post a link to this video on YouTube if you prefer to watch it there.
51:48

If you watch this ~50 minute screen recording closely (yeah, I know, it's long; there are also some times when my computer was very slow and laggy, just skip past that part. And at one point I had to run and get my 9-month-old a new bottle and left it on a boring screen, sorry!), I believe you can see real signs of the kind of runaway, recursive AI self-improvement that people have been warning of for a while (Mr. Kurzweil most notably and prophetically). Why do I say that? What's different now? Well, there's a reason my set of agent coding tooling is called the Flywheel. These tools all mutually self-reinforce each other. And they all flow directly into my ntm tool (short for "named_tmux_manager"), which acts as a sort of integration point and nerve center for the tools (this is becoming more true by the minute as I'm now seriously working on ntm). Now, ntm was something I started making to automate some aspects of my workflow, but it was the kind of thing where, until it was perfect, it sort of just slowed me down. So I didn't actually use it even though I kept working on it and trying to improve it, and suggested to users that they try it in my tutorials. Well anyway, I finally got around to "dogfooding" ntm last night, and now it's going to get very dramatically better at an alarming rate. Some of that is from applying my "idea wizard" prompt to generate more useful features and building that stuff out and addressing obvious pain points I encountered during my newfound usage of the tool. But a lot comes from my realization that, once again, ntm's true utility is not as a tool for ME, but for an agent. That is, ntm lets one instance of Claude Code or Codex act as, well, me, do the things that I had been doing manually. Do I wish I had started using ntm earlier? No, for two big reasons: 1) Doing it manually helped me build up my intuition massively, which directly led me down the path of creating useful prompt strategies and workflows; these often began as ad-hoc prompts that I realized could be generalized and made more versatile/universal. Lesson: don't prematurely automate until you have an intimate, intuitive feel for your "core value-add loop." Otherwise you'll have a fully automated system quickly that efficiently and automatically does a stupid or otherwise sub-optimal thing. 2) My eyes have been opened to the beauty and power of Skills. I'm not talking about your garden-variety skills that are just a simple markdown file. I'm talking about true tour-de-force directories of perfectly structured and organized files that are filled with good information, insights, workflows, etc., but presented in a way that is highly optimized for consumption by AI agents, with extreme attention paid to things like perfect progressive disclosure, token density, agent-ergonomics, agent-intuitiveness, etc. And also Skills that go way beyond markdown files, with full integration into Claude Code where it makes sense via hooks, sub-agents, and even Python scripts. These kinds of skills are a qualitative difference in expressive power and usefulness and a total game changer. They are also effectively composable, creating almost an algebra of skills that let you use them together in powerful ways. I'm working on a subscription service website and CLI tool now to share what I've learned here most effectively, stay tuned for that in the coming days. Anyway, I now know what to make and how to make it. So, getting back to that screen recording, what does it show that makes me claim recursive self-improvement is here? If you keep your eye on the upper left tmux pane, that's the "controller" agent. It is using ntm to control all the other panes which are also running Claude Code (but ntm fully supports other agent types like Codex and Gemini-CLI, and it's trivially easy to mix and match them if you wanted to have, say, 8 CCs and 6 Codexes for writing the code and 3 Gemini-CLIs for reviewing code.) Now, there's nothing that crazy about this much so far. But where it starts to get very cool is that as the session continues and we encounter real-world problems, things like my ridiculously overloaded computer that keeps hanging for long periods, Claude Code instances that crash and get into a frozen, unresponsive state, it can learn from that. And you can see it using my skill writing skill to refine its ntm vibe coding skill in real time. And then take that skill and refine it to be more intuitive for itself. Or use my cass tool skill to search all the session histories to look for problems that came up and strategize how to solve them. The most useful part was when, towards the end of the session, I told it to reflect on all the things we had done and problems we encountered. One way it can usefully leverage those reflections is by improving its ntm vibe coding skill to make it cover more edge cases and exigencies. But the other, more fundamental, way is for it to conceive of and design the optimal new features and functionality for ntm itself so that the tool embodies those lessons in a first-class way. This offloads cognition from its brain onto its tooling, just like how a person can lean on spellcheck or a calculator. It codifies correct, effective reasoning at the tool level, where it's more reliable and robust and repeatable. And btw, did you notice what code base it was working on the whole time? It was none other than ntm itself! So as it worked on its own tool, it had reflections and ideas about how to further improve the tool. Now, it could have just as easily gotten those insights and ideas while using ntm to work on a different project, but the fact that it was working on itself is almost gloriously meta and recursive. So by the end, after learning from tending to a big group of agent workers (btw, I have previously emphasized doing everything in a really distributed/decentralized way, where each fungible agent gets identical marching orders that tell it to use my bv tool to find the optimal bead to work on. This does work very well, but occasionally results in some contention and overlap from thundering herd, or at least wastes time/tokens/communication in avoiding that before the agents waste time duplicating work. But in this new ntm-oriented workflow, I was able to have the controller agent in the upper left use bv itself and then optimally parcel out the instructions to each agent so that we could know for sure that there's no overlap), I ended up with a ton of new beads for new features, which I had it optimize and polish a few times. Now I can swap to a new Claude Max account and have the swarm implement all those new features! It should only take a couple passes like the one shown in the screen recording to get everything implemented. Then we can rinse and repeat, having the agent read through the full session histories of each agent and its experience from its own session in sending ntm commands and seeing how they worked out in practice, to come up with the next batch of changes to both its ntm vibe coding skill AND to the ntm tool itself. Do you see how rapidly this turns into Skynet? My mistake earlier was in focusing on making myself a "faster horse" as Henry Ford used to joke about customers wanting before he showed them what they should really want (a Model T). That is, something that would make my experience nicer while doing this agent swarm based development workflow. But the obvious lesson is that you should make all your tooling agent-first because the agents are just better at this stuff. You can still watch, and of course I did add a ridiculous number of very nice human-centric features to ntm that you'll be seeing in the next day or two, but those are really kind of "for fun" to make us humans feel better about the process. All the real value-add is happening "by agents, for agents." PS: Towards the end, you can see me switch to my Mac and tell Claude to improve the skill that I made earlier today for taking the mkv screen recording files from OBS Studio and muxing them into MP4 files for sharing, while downloading songs from YouTube to serve as the background music. I made it so it can also grab the thumbnails and generate little song credit cards that show up in the lower right corner. This worked perfectly the first time! I'll include some screenshots in a response post showing how that worked, but it was awesome to witness. Skills are POWERFUL. I'll also post a link to this video on YouTube if you prefer to watch it there.

Jeffrey Emanuel

25,483 görüntüleme • 8 ay önce

$AMD $5 Trillion is Inevitable LT| Agentic AI🧵 Agentic AI is the new $5 Trillion TAM 🚨🚨🚨 This thead will do Comp with $INTC and how to quantify this massive Agentic AI demand spike, and forcing Jensen to rush a CPU design. Global Agentic AI Market size is estimated to be $3-$5Trillion TAM by 2030(McKinsey) Quantifying the demand from agentic AI for AMD involves assessing the broader market growth for agentic systems, their unique computational requirements (particularly for CPUs in orchestration and reasoning tasks), and AMD's positioning very well through products like EPYC processors and partnerships. AMD EPYC Venice is the most superior choice in 2026-2027 for most Agentic AI workloads Agentic AI refers to autonomous AI agents that perform multi-step tasks, involving sequential logic, tool integration, and decision-making workloads that heavily rely on CPUs for handling orchestration, memory management, and context switching, rather than just GPU-parallelized training or batch inference. Agentic AI is often cited as 40-100x more "hungry" than traditional AI due to its continuous, 24/7 operation and complex workflows. This stems from factors like chain-of-thought reasoning (multiple LLM calls per query), API/tool interactions, memory management, and orchestration loops, which can generate 10-100x more tokens and require real-time responsiveness. For example, a single agentic query might trigger 5-20 model inferences, making it 10-20x more compute-intensive than simple chatbots, and the always-on nature compounds this to 40-100x overall. Nvidia's CEO has highlighted this as driving "easily 100x more computation" for inference in agentic/reasoning setups. AMD's EPYC Venice (6th Gen EPYC, codenamed "Venice") and Intel's Xeon 7 Diamond Rapids represent the pinnacle of server CPU technology in 2026, both targeting high-performance data center workloads like AI inference, agentic AI orchestration, cloud computing, and HPC. Venice builds on AMD's Zen 6 architecture, emphasizing core density and efficiency, while Diamond Rapids leverages Intel's Panther Cove P-cores for balanced performance. Both chips adopt similar advancements like 16-channel DDR5 memory and PCIe Gen 6, but differ in core counts, process nodes, and overall design philosophy. Intel has faced acute supply constraints across its Xeon lineup, including legacy nodes (Intel 7/3) and the ramping 18A process for next-gen parts. Intel shortage is expected with lead times up to 6 months or longer. 1. AMD EPYC Venice vs Intel Xeon 7 Diamond Rapids Architecture AMD: Zen 6 chiplet design with 8 CCDs and dual IODs Intel: Panther Cove P-cores; multi-die architecture with 4 compute tiles Core/Thread Count AMD: Up to 256 cores / 512 threads (Zen 6c variant) Intel: Up to 192 cores / 192 threads Process Node AMD: TSMC N2 (2nm) Intel: Intel 18A (1.8nm-class); in-house fab Memory Support AMD: 16-channel DDR5; up to 1.6 TB/s bandwidth. Intel: 16-channel DDR5 ; up to 1.6 TB/s bandwidth I/O and Connectivity AMD: PCIe Gen 6 (up to 128 lanes); twice the CPU-to-GPU bandwidth Intel: PCIe Gen 6 (up to 128 lanes); LGA 9324 socket Power (TDP) AMD: Starting 400-500W, potentially lower due to efficiency gains from TSMC 2nm Intel: Starting 400-500W, as it targets competitive efficiency Performance Projections AMD: Up to 70% uplift vs. 5th Gen Turin (1.7x in multi-threaded/AI tasks) Intel: ~40% faster than Granite Rapids (Xeon 6, 128-core). Lags AMD in per-core perf and 40-50% behind Venice core-for-core comp Target Workloads AMD: AI inference/orchestration, HPC, cloud virtualization. Partnerships Intel: Hyperscale AI, general enterprise. Custom silicon Pricing: AMD: estimated $10k-$20k for top SKUs Intel: estimated $8-$18k Availability: AMD: Significant Ramp H2 2026 due to higher allocation from TSMC Intel: H1-H2 2026 delayed, but trying to catch up Overall: ~Venice's 256 cores provide a 33% edge over Diamond Rapids' 192, making it superior for massively parallel tasks like AI training/inference or virtualization ~TSMC's N2 vs. Intel 18A debates rage on which is "better," but AMD's mature chiplet approach yields better density ( 32 cores/CCD vs. Intel's 48/tile). Venice's redesign reduces latency, aiding agentic AI where CPUs handle orchestration ~ Early projections show Venice widening AMD's lead matching or exceeding Diamond Rapids' perf with fewer watts in multi-threaded benchmarks. Intel's no-SMT design (to prioritize AI) handicaps it vs. AMD's 512 threads, though Clearwater Forest (E-core) could compete in density-focused niches. ~Power & Cooling: Both push above 400-500W, demanding liquid cooling. ~AMD been taking market share now above 40%. AMD EPYC Venice emerges as the superior choice in 2026 for most server workloads. Its higher core/thread count (256/512 vs. 192/192), stronger per-core performance, and architecture optimized for AI-driven tasks (agentic orchestration with GPU integration) provide decisive advantages in throughput, scalability, and efficiency. Projections indicate Venice delivering 1.7x the performance of prior gens while widening the gap over Intel ( 40-70% leads in multi-threaded benchmarks). AMD's fabless model with TSMC ensures reliable scaling, and its ecosystem ( open ROCm) appeals to AI adopters. Intel's Diamond Rapids is competitive in single-threaded enterprise apps and custom hyperscale ( NVLink), with potential fab advantages for supply/security. However, without SMT and lower density, it falls short in core-for-core battles—exposing Intel to another generation of AMD dominance unless 18A yields surprise efficiency gains. For data centers prioritizing raw compute ( AI, HPC), Venice wins; for Intel-centric ecosystems or specialized I/O, Diamond Rapids holds ground. Real benchmarks post-launch will confirm, but logic points to AMD pulling ahead. 2. Market size , Potential Revenue and Supply Global Agentic AI market size is projected to be $3-$5 Trillion by 2030 according to McKinsey, where consensus points to 40-50% CAGR driven by small to large enterprise demand. I also wrote a full thread on how and why Agentic AI is so explosive that AMD will blow all anlaysts estimate for subscribers. Link below if you are interested. AMD's data center segment hit a record $5.4B in Q4 2025 (up 39% YoY), with EPYC shipments ramping due to agentic demand. With 2GW of deployment in H2 2026, AMD AI data center revenue has $40-$50B+ at the lowest or most conservative projection; or Total Revenue in the $77-$94B For FY2026. However, Agentic AI massive demand spike could send EPYC revenue 3x to 4x in the next few years, potentially surpassing MI series GPU demand as enterprises prioritize CPU-dense Rack setups. This is pushing $NVDA Jensen to rush a CPU design and acquired Groq, a new CPU player due to this massive TAM. Noted that this is just popping just in weeks, highlighting we are just so early in this AI Supercycle and the pace of adoption is insane, and clearly productivity will skyrocket. Why? Because Agentic AI is 24/7 Smart AI agent working for you or your businesses is a mad compelling, and it is estimated to be 40-100x more Inference Hugnry! Many experts already said it is impossible to project this kind of Inference Demand. AI CapEx is expected to ramp up even more in 2027-2028-2029 and 2030 as Global Agentic AI is going to scale to $3-$5 Trillion TAM by 2030. The nature of Agentic is driving higher CPU/GPU ratio, with CPUs handling 50-90% of Agentic workflows. For example, The current Helios Rack: 18 compute trays per rack with 72 GPUs + 18 CPUs. The beauty of this $META and $AMD long term partnership is, that it is absolutely flexible to adjust racks to higher CPU rato or equal to service different needs. Helios rack can be easily swap to 2 GPUs 2CPUs or even CPUs only trays for dedicated orchestration/head nodes. You see, the beauty of this open rack-scale is flexibility and evolvability. If Agentic AI demand pushes much higher, AMD should be able to adjust variant trays without abandoning Heilos Rack. We can't talk just about massive Agentic AI demand without talking about the Supply side or TSMC. TSMC, AMD's primary foundry for advanced nodes ( Zen 6/Venice on N2/2nm), is addressing AI-driven shortages through massive expansions. TSMC accelerates fab construction with up to 10 facilities targeted for 2026. TSMC is accelerating its domestic manufacturing expansion, with industry sources indicating that as many as ten fabs could be under construction or preparing to begin operations across Taiwan’s major science parks. TSMC Capex: $52-56B in 2026 (up 37% YoY), with $45B already approved for new/upgraded capacities. 70-80% for advanced processes (2nm/A16), 10-20% for packaging (CoWoS quadrupling to 120-140K wafers/month by late 2026). In addition, Taiwanese companies (led by TSMC) commit to at least $250B in direct investments in US-based advanced semiconductor, AI, and energy production/innovation capacity.Taiwan provides $250B in government credit guarantees to facilitate additional investments and build a full US semiconductor ecosystem (including industrial parks). TSMC completed a second land purchase in Arizona (January 2026) for gigafab scaling, with an additional $100B+ (potentially four more modules) to further expand and qualify for tariff exemptions. AMD with secured 12GW from OpenAI and $META and massive Agentic AI will mean higher priority acess to 20-30% more wafers on TSMC advanced nodes, as TSMC has multi-year agreements with AMD for AI chips. Dr. C. C. Wei, CEO of TSMC quote: "I spend a lot of time in the last three or four months talking to my customer and then customers. Customer. I want to make sure that my customers demand are real. I talk to those cloud service providers, all of them. Their answer is. I'm quite satisfied with their answer. Actually they show me the evidence that the AI really help their business. So they grow their business successfully and he or she in their financial return. So I also double check their financial status. They are very rich." Amid shortages, the US buildout ensures AMD can ramp production of Instinct GPUs and EPYC CPUs without the constraints hitting competitors like Intel. By diversifying away from Taiwan (85% of advanced nodes today), the agreement mitigates supply disruptions, ensuring stable flows for AMD's chips. Scaling production and securing supply will matter for AMD the most in the next 5-10 years growth. The growth could be 80-100% YoY or higher; or it could be in the 60%. The aggressive TSMC supply ramp is reassuring the higher growth point. Conclusion: AMD stands at a pivotal inflection point in 2026, where the explosive rise of agentic AI demanding 40-100x more inference compute through its 24/7, multi-step orchestration positions the company to potentially triple its EPYC CPU revenue to $45-60B+ by 2028 while scaling Instinct GPUs to tens of billions annually by 2027. Agentic AI demand could push AI CapEx closer to $1 Trillion in 2027, far higher than most estimates. Dr. Lisa Su, AMD's visionary CEO, is masterfully securing supply to harness this massive demand by prioritizing operational execution and deep TSMC collaboration, ensuring readiness for the second-half 2026 AI ramp. Dr. Su has explicitly called out surging EPYC demand for agentic tasks where CPUs power head nodes and traditional workloads alongside GPUs while guiding for data center dominance through proactive capacity planning and partnerships like Nutanix ($150M investment for open agentic platforms) or providing tens of millions CPUs for OpenAI, $META, $ORCL, $AMZN, $MSFT, $GOOGL and others. Her strategy includes multi-year TSMC agreements for advanced nodes (N2 for Venice CPUs and future Instincts), diversifying beyond Taiwan to mitigate risks, and unveiling innovations like the MI455X GPU at CES 2026, which she touted as enabling "the next trillion-dollar market opportunity" in physical AI. Dr. Su's forward-looking vision predicting AI reaching 5 billion users emphasizes "AI everywhere," backed by hardware like Ryzen AI chips, all while declaring demand "going through the roof" and committing to scale without bottlenecks. TSMC's aggressive ramp-up, fueled by $52-56B in 2026 capex (up 37% YoY) and 10+ new fabs across Taiwan, the US (Arizona cluster expanding to 6+ modules with $165B+ investment), Japan, and Europe, provides profound reassurance for AMD's supply stability. The January 2026 US-Taiwan agreement committing $250B in investments and credit guarantees for US reshoring accelerates this, granting tariff relief (15% rates with 1.5-2.5x exemptions) tied to capacity buildouts, enabling TSMC to potentially double output over the decade to meet AI wafer hunger. This translates to 20-30% higher wafer allocations on key nodes, sidestepping Intel-like shortages and empowering Dr. Su's team to deliver on hyperscaler demands without disruption. Ultimately, this synergy cements AMD's leadership in the agentic era, promising sustained growth, $5T+ valuations at scale, and a resilient path forward as AI reshapes the world. This is NOT Financial Advice! Video source: AMD CES 2026
2:49

$AMD $5 Trillion is Inevitable LT| Agentic AI🧵 Agentic AI is the new $5 Trillion TAM 🚨🚨🚨 This thead will do Comp with $INTC and how to quantify this massive Agentic AI demand spike, and forcing Jensen to rush a CPU design. Global Agentic AI Market size is estimated to be $3-$5Trillion TAM by 2030(McKinsey) Quantifying the demand from agentic AI for AMD involves assessing the broader market growth for agentic systems, their unique computational requirements (particularly for CPUs in orchestration and reasoning tasks), and AMD's positioning very well through products like EPYC processors and partnerships. AMD EPYC Venice is the most superior choice in 2026-2027 for most Agentic AI workloads Agentic AI refers to autonomous AI agents that perform multi-step tasks, involving sequential logic, tool integration, and decision-making workloads that heavily rely on CPUs for handling orchestration, memory management, and context switching, rather than just GPU-parallelized training or batch inference. Agentic AI is often cited as 40-100x more "hungry" than traditional AI due to its continuous, 24/7 operation and complex workflows. This stems from factors like chain-of-thought reasoning (multiple LLM calls per query), API/tool interactions, memory management, and orchestration loops, which can generate 10-100x more tokens and require real-time responsiveness. For example, a single agentic query might trigger 5-20 model inferences, making it 10-20x more compute-intensive than simple chatbots, and the always-on nature compounds this to 40-100x overall. Nvidia's CEO has highlighted this as driving "easily 100x more computation" for inference in agentic/reasoning setups. AMD's EPYC Venice (6th Gen EPYC, codenamed "Venice") and Intel's Xeon 7 Diamond Rapids represent the pinnacle of server CPU technology in 2026, both targeting high-performance data center workloads like AI inference, agentic AI orchestration, cloud computing, and HPC. Venice builds on AMD's Zen 6 architecture, emphasizing core density and efficiency, while Diamond Rapids leverages Intel's Panther Cove P-cores for balanced performance. Both chips adopt similar advancements like 16-channel DDR5 memory and PCIe Gen 6, but differ in core counts, process nodes, and overall design philosophy. Intel has faced acute supply constraints across its Xeon lineup, including legacy nodes (Intel 7/3) and the ramping 18A process for next-gen parts. Intel shortage is expected with lead times up to 6 months or longer. 1. AMD EPYC Venice vs Intel Xeon 7 Diamond Rapids Architecture AMD: Zen 6 chiplet design with 8 CCDs and dual IODs Intel: Panther Cove P-cores; multi-die architecture with 4 compute tiles Core/Thread Count AMD: Up to 256 cores / 512 threads (Zen 6c variant) Intel: Up to 192 cores / 192 threads Process Node AMD: TSMC N2 (2nm) Intel: Intel 18A (1.8nm-class); in-house fab Memory Support AMD: 16-channel DDR5; up to 1.6 TB/s bandwidth. Intel: 16-channel DDR5 ; up to 1.6 TB/s bandwidth I/O and Connectivity AMD: PCIe Gen 6 (up to 128 lanes); twice the CPU-to-GPU bandwidth Intel: PCIe Gen 6 (up to 128 lanes); LGA 9324 socket Power (TDP) AMD: Starting 400-500W, potentially lower due to efficiency gains from TSMC 2nm Intel: Starting 400-500W, as it targets competitive efficiency Performance Projections AMD: Up to 70% uplift vs. 5th Gen Turin (1.7x in multi-threaded/AI tasks) Intel: ~40% faster than Granite Rapids (Xeon 6, 128-core). Lags AMD in per-core perf and 40-50% behind Venice core-for-core comp Target Workloads AMD: AI inference/orchestration, HPC, cloud virtualization. Partnerships Intel: Hyperscale AI, general enterprise. Custom silicon Pricing: AMD: estimated $10k-$20k for top SKUs Intel: estimated $8-$18k Availability: AMD: Significant Ramp H2 2026 due to higher allocation from TSMC Intel: H1-H2 2026 delayed, but trying to catch up Overall: ~Venice's 256 cores provide a 33% edge over Diamond Rapids' 192, making it superior for massively parallel tasks like AI training/inference or virtualization ~TSMC's N2 vs. Intel 18A debates rage on which is "better," but AMD's mature chiplet approach yields better density ( 32 cores/CCD vs. Intel's 48/tile). Venice's redesign reduces latency, aiding agentic AI where CPUs handle orchestration ~ Early projections show Venice widening AMD's lead matching or exceeding Diamond Rapids' perf with fewer watts in multi-threaded benchmarks. Intel's no-SMT design (to prioritize AI) handicaps it vs. AMD's 512 threads, though Clearwater Forest (E-core) could compete in density-focused niches. ~Power & Cooling: Both push above 400-500W, demanding liquid cooling. ~AMD been taking market share now above 40%. AMD EPYC Venice emerges as the superior choice in 2026 for most server workloads. Its higher core/thread count (256/512 vs. 192/192), stronger per-core performance, and architecture optimized for AI-driven tasks (agentic orchestration with GPU integration) provide decisive advantages in throughput, scalability, and efficiency. Projections indicate Venice delivering 1.7x the performance of prior gens while widening the gap over Intel ( 40-70% leads in multi-threaded benchmarks). AMD's fabless model with TSMC ensures reliable scaling, and its ecosystem ( open ROCm) appeals to AI adopters. Intel's Diamond Rapids is competitive in single-threaded enterprise apps and custom hyperscale ( NVLink), with potential fab advantages for supply/security. However, without SMT and lower density, it falls short in core-for-core battles—exposing Intel to another generation of AMD dominance unless 18A yields surprise efficiency gains. For data centers prioritizing raw compute ( AI, HPC), Venice wins; for Intel-centric ecosystems or specialized I/O, Diamond Rapids holds ground. Real benchmarks post-launch will confirm, but logic points to AMD pulling ahead. 2. Market size , Potential Revenue and Supply Global Agentic AI market size is projected to be $3-$5 Trillion by 2030 according to McKinsey, where consensus points to 40-50% CAGR driven by small to large enterprise demand. I also wrote a full thread on how and why Agentic AI is so explosive that AMD will blow all anlaysts estimate for subscribers. Link below if you are interested. AMD's data center segment hit a record $5.4B in Q4 2025 (up 39% YoY), with EPYC shipments ramping due to agentic demand. With 2GW of deployment in H2 2026, AMD AI data center revenue has $40-$50B+ at the lowest or most conservative projection; or Total Revenue in the $77-$94B For FY2026. However, Agentic AI massive demand spike could send EPYC revenue 3x to 4x in the next few years, potentially surpassing MI series GPU demand as enterprises prioritize CPU-dense Rack setups. This is pushing $NVDA Jensen to rush a CPU design and acquired Groq, a new CPU player due to this massive TAM. Noted that this is just popping just in weeks, highlighting we are just so early in this AI Supercycle and the pace of adoption is insane, and clearly productivity will skyrocket. Why? Because Agentic AI is 24/7 Smart AI agent working for you or your businesses is a mad compelling, and it is estimated to be 40-100x more Inference Hugnry! Many experts already said it is impossible to project this kind of Inference Demand. AI CapEx is expected to ramp up even more in 2027-2028-2029 and 2030 as Global Agentic AI is going to scale to $3-$5 Trillion TAM by 2030. The nature of Agentic is driving higher CPU/GPU ratio, with CPUs handling 50-90% of Agentic workflows. For example, The current Helios Rack: 18 compute trays per rack with 72 GPUs + 18 CPUs. The beauty of this $META and $AMD long term partnership is, that it is absolutely flexible to adjust racks to higher CPU rato or equal to service different needs. Helios rack can be easily swap to 2 GPUs 2CPUs or even CPUs only trays for dedicated orchestration/head nodes. You see, the beauty of this open rack-scale is flexibility and evolvability. If Agentic AI demand pushes much higher, AMD should be able to adjust variant trays without abandoning Heilos Rack. We can't talk just about massive Agentic AI demand without talking about the Supply side or TSMC. TSMC, AMD's primary foundry for advanced nodes ( Zen 6/Venice on N2/2nm), is addressing AI-driven shortages through massive expansions. TSMC accelerates fab construction with up to 10 facilities targeted for 2026. TSMC is accelerating its domestic manufacturing expansion, with industry sources indicating that as many as ten fabs could be under construction or preparing to begin operations across Taiwan’s major science parks. TSMC Capex: $52-56B in 2026 (up 37% YoY), with $45B already approved for new/upgraded capacities. 70-80% for advanced processes (2nm/A16), 10-20% for packaging (CoWoS quadrupling to 120-140K wafers/month by late 2026). In addition, Taiwanese companies (led by TSMC) commit to at least $250B in direct investments in US-based advanced semiconductor, AI, and energy production/innovation capacity.Taiwan provides $250B in government credit guarantees to facilitate additional investments and build a full US semiconductor ecosystem (including industrial parks). TSMC completed a second land purchase in Arizona (January 2026) for gigafab scaling, with an additional $100B+ (potentially four more modules) to further expand and qualify for tariff exemptions. AMD with secured 12GW from OpenAI and $META and massive Agentic AI will mean higher priority acess to 20-30% more wafers on TSMC advanced nodes, as TSMC has multi-year agreements with AMD for AI chips. Dr. C. C. Wei, CEO of TSMC quote: "I spend a lot of time in the last three or four months talking to my customer and then customers. Customer. I want to make sure that my customers demand are real. I talk to those cloud service providers, all of them. Their answer is. I'm quite satisfied with their answer. Actually they show me the evidence that the AI really help their business. So they grow their business successfully and he or she in their financial return. So I also double check their financial status. They are very rich." Amid shortages, the US buildout ensures AMD can ramp production of Instinct GPUs and EPYC CPUs without the constraints hitting competitors like Intel. By diversifying away from Taiwan (85% of advanced nodes today), the agreement mitigates supply disruptions, ensuring stable flows for AMD's chips. Scaling production and securing supply will matter for AMD the most in the next 5-10 years growth. The growth could be 80-100% YoY or higher; or it could be in the 60%. The aggressive TSMC supply ramp is reassuring the higher growth point. Conclusion: AMD stands at a pivotal inflection point in 2026, where the explosive rise of agentic AI demanding 40-100x more inference compute through its 24/7, multi-step orchestration positions the company to potentially triple its EPYC CPU revenue to $45-60B+ by 2028 while scaling Instinct GPUs to tens of billions annually by 2027. Agentic AI demand could push AI CapEx closer to $1 Trillion in 2027, far higher than most estimates. Dr. Lisa Su, AMD's visionary CEO, is masterfully securing supply to harness this massive demand by prioritizing operational execution and deep TSMC collaboration, ensuring readiness for the second-half 2026 AI ramp. Dr. Su has explicitly called out surging EPYC demand for agentic tasks where CPUs power head nodes and traditional workloads alongside GPUs while guiding for data center dominance through proactive capacity planning and partnerships like Nutanix ($150M investment for open agentic platforms) or providing tens of millions CPUs for OpenAI, $META, $ORCL, $AMZN, $MSFT, $GOOGL and others. Her strategy includes multi-year TSMC agreements for advanced nodes (N2 for Venice CPUs and future Instincts), diversifying beyond Taiwan to mitigate risks, and unveiling innovations like the MI455X GPU at CES 2026, which she touted as enabling "the next trillion-dollar market opportunity" in physical AI. Dr. Su's forward-looking vision predicting AI reaching 5 billion users emphasizes "AI everywhere," backed by hardware like Ryzen AI chips, all while declaring demand "going through the roof" and committing to scale without bottlenecks. TSMC's aggressive ramp-up, fueled by $52-56B in 2026 capex (up 37% YoY) and 10+ new fabs across Taiwan, the US (Arizona cluster expanding to 6+ modules with $165B+ investment), Japan, and Europe, provides profound reassurance for AMD's supply stability. The January 2026 US-Taiwan agreement committing $250B in investments and credit guarantees for US reshoring accelerates this, granting tariff relief (15% rates with 1.5-2.5x exemptions) tied to capacity buildouts, enabling TSMC to potentially double output over the decade to meet AI wafer hunger. This translates to 20-30% higher wafer allocations on key nodes, sidestepping Intel-like shortages and empowering Dr. Su's team to deliver on hyperscaler demands without disruption. Ultimately, this synergy cements AMD's leadership in the agentic era, promising sustained growth, $5T+ valuations at scale, and a resilient path forward as AI reshapes the world. This is NOT Financial Advice! Video source: AMD CES 2026

Mike

44,460 görüntüleme • 6 ay önce

🚨 “I WISH I COULD KILL 300,000,000 AMERICANS” — FBI Just Took Down Three U.S. Citizens Funding ISIS RPG and Drone Attacks on Our Troops. This Is What Happens When the DOJ Actually Does Its Job. 💥FBI BUSTS ISIS TERROR CELL ON AMERICAN SOIL — THREE U.S. CITIZENS PLOTTED RPG AND DRONE ATTACKS ON OUR TROOPS ☠️ Three radicalized American citizens — not foreign infiltrators, but homegrown traitors radicalized right here on U.S. soil — were arrested in simultaneous FBI raids across Kansas and California early Friday morning. Their mission? Fund ISIS. Buy RPGs. Send drones to kill American servicemembers. And they came terrifyingly close. 🔥 THE PLOT, UNPACKED The three jihadist wannabes — Bisaam Ghafoor (21, Leawood, KS), Elias Shamsaldeen (21, Porterville, CA), and Bereen Dzayee (25, Lakeside, CA) — spent over a year on Discord and encrypted messaging apps coordinating a multi-pronged material support operation for ISIS. Here’s what the DOJ complaint lays out: - They pledged bay’ah (allegiance) to ISIS leadership — not in private whispers, but publicly on social media. Shamsaldeen did it openly in October 2025. - They sent over $2,000 to someone they fully believed was an active ISIS operative — with Ghafoor personally handing a wax-sealed envelope containing $250 cash to an FBI undercover agent at a Kansas City mosque in May 2026, then sending another $200. - Shamsaldeen drove 90 miles to a crypto ATM at a gas station, attempting to launder his donations beyond traceability. He successfully sent $1,590 through a financial app to an FBI undercover account, believing it was buying drones to rain hell on American troops. - Ghafoor’s name was literally written in Arabic on an RPG projectile — a weapon he was told would be used to kill U.S. servicemembers overseas. His response? He celebrated it, calling it “sick” — in the enthusiastic, not disturbed, sense of the word. 🩸 THE CHILLING WORDS These aren’t allegations of abstract sympathies. The FBI has the receipts. Direct quotes from the complaint: Ghafoor: “I have always wanted to kill a female soldier by beheading.” Ghafoor: “I wish I could kill 300,000,000 Americans.” That’s not hyperbole. That’s not a kid trolling on Discord. That’s a 21-year-old American citizen fantasizing about decapitating a female U.S. service member and exterminating the entire population of the United States. Shamsaldeen: Expressed a desire to stab and injure a U.S. servicemember he encountered at a business. He also told the group that his own mother encouraged her children to grow up and kill Americans. Dzayee: Suggested U.S. Special Forces — specifically Green Berets — should be the drone targets. He also coordinated the money transfers, telling the group to call it “charity” and adding: “In my head it’s charity.” And here’s the kicker — Dzayee himself acknowledged the gravity. He and Ghafoor called what they were doing “treason” and admitted it was “bigger” than their existing fraud scheme. They knew exactly what they were. They said it out loud. And they kept going anyway. 🎯 THE STING: HOW THE FBI GOT THEM The investigation began in March 2025 with a single anonymous tip about pro-ISIS social media posts. Within months, the FBI had: - Infiltrated their Discord and messaging groups - Deployed undercover agents and confidential human sources - Tracked Shamsaldeen’s 90-mile crypto ATM pilgrimage via surveillance - Captured Ghafoor on tape, handing cash to an agent inside a mosque - Documented every pledge of allegiance, every violent fantasy, every dollar sent FBI Director Kash Patel didn’t mince words: “These subjects allegedly swore allegiance to ISIS, plotted multiple attacks, and even targeted U.S. servicemembers — but this FBI stopped them cold.” Acting AG Todd Blanche put the broader mission in perspective: “This administration has put terrorists, cartels, and gangs on notice. Today’s arrest makes clear our commitment to taking down terrorist networks — anywhere.” And the most haunting line from Blanche, which should sear itself into every American’s consciousness: “Young men in their 20s completely indoctrinated by terrorism and by terrorists and actually spending money to actually follow through on these attacks. It’s a good reminder to Americans that this fight is not over.” 🇺🇸 THE DEEPER TRUTH NOBODY WANTS TO SAY Here’s what the sanitized headlines won’t tell you: all three are U.S. citizens. Born or naturalized right here. One of them — Dzayee — appears in photos wearing a U.S. Navy sailor’s uniform, confirmed by neighbors and a former classmate. These aren’t foreign agents sneaking across the border. These are products of the American system, radicalized internally through their teachers and online echo chambers while the previous administration’s DOJ and intelligence agencies were busy hunting grandmothers at school board meetings and labeling concerned parents “domestic terrorists.” The Biden-era FBI spent years telling us the greatest terror threat was white supremacy in the heartland. Meanwhile, actual jihadist cells were forming on Discord, pledging allegiance to ISIS leadership, and wiring money for RPGs and drones — right under their noses. This bust happened because the Trump DOJ and Kash Patel’s FBI actually prioritized counterterrorism rather than treating it as an inconvenient distraction from political prosecutions. ⚖️ WHAT HAPPENS NOW All three face charges of conspiring to provide material support to a designated foreign terrorist organization — a charge that carries up to 20 years in federal prison. The case is being prosecuted in the District of Kansas by Assistant U.S. Attorneys Scott Rask and Michelle MacFarlane, alongside the National Security Division’s Counterterrorism Section. They’re innocent until proven guilty in a court of law. But the complaint is devastating. The paper trail is massive. And the confessions are on tape. 📢 THE TAKEAWAY The war didn’t end when we pulled out of Afghanistan. It didn’t end when Baghdadi ate a suicide vest in a Syrian tunnel. The ideology metastasized. It’s on Discord. It’s in mosques in Kansas City. It’s in the mind of a 21-year-old in Leawood who dreams of beheading female soldiers. But here’s the difference between then and now: this administration is actually hunting them. Not lecturing us about Islamophobia. Not deflecting to “stochastic terrorism” from political opponents. Actually doing counterterrorism. This is what law and order looks like. 🇺🇸 #ISISBusted #LawAndOrder #FBI #ToddBlanche #KashPatel #NationalSecurity #MaterialSupport #HomegrownTerror #AmericaFirst #TrumpDOJ #Counterterrorism #GreenBerets #ProtectOurTroops #WakeUpAmerica #DiscordJihad #Treason #JusticeServed #StopISIS
1:11

🚨 “I WISH I COULD KILL 300,000,000 AMERICANS” — FBI Just Took Down Three U.S. Citizens Funding ISIS RPG and Drone Attacks on Our Troops. This Is What Happens When the DOJ Actually Does Its Job. 💥FBI BUSTS ISIS TERROR CELL ON AMERICAN SOIL — THREE U.S. CITIZENS PLOTTED RPG AND DRONE ATTACKS ON OUR TROOPS ☠️ Three radicalized American citizens — not foreign infiltrators, but homegrown traitors radicalized right here on U.S. soil — were arrested in simultaneous FBI raids across Kansas and California early Friday morning. Their mission? Fund ISIS. Buy RPGs. Send drones to kill American servicemembers. And they came terrifyingly close. 🔥 THE PLOT, UNPACKED The three jihadist wannabes — Bisaam Ghafoor (21, Leawood, KS), Elias Shamsaldeen (21, Porterville, CA), and Bereen Dzayee (25, Lakeside, CA) — spent over a year on Discord and encrypted messaging apps coordinating a multi-pronged material support operation for ISIS. Here’s what the DOJ complaint lays out: - They pledged bay’ah (allegiance) to ISIS leadership — not in private whispers, but publicly on social media. Shamsaldeen did it openly in October 2025. - They sent over $2,000 to someone they fully believed was an active ISIS operative — with Ghafoor personally handing a wax-sealed envelope containing $250 cash to an FBI undercover agent at a Kansas City mosque in May 2026, then sending another $200. - Shamsaldeen drove 90 miles to a crypto ATM at a gas station, attempting to launder his donations beyond traceability. He successfully sent $1,590 through a financial app to an FBI undercover account, believing it was buying drones to rain hell on American troops. - Ghafoor’s name was literally written in Arabic on an RPG projectile — a weapon he was told would be used to kill U.S. servicemembers overseas. His response? He celebrated it, calling it “sick” — in the enthusiastic, not disturbed, sense of the word. 🩸 THE CHILLING WORDS These aren’t allegations of abstract sympathies. The FBI has the receipts. Direct quotes from the complaint: Ghafoor: “I have always wanted to kill a female soldier by beheading.” Ghafoor: “I wish I could kill 300,000,000 Americans.” That’s not hyperbole. That’s not a kid trolling on Discord. That’s a 21-year-old American citizen fantasizing about decapitating a female U.S. service member and exterminating the entire population of the United States. Shamsaldeen: Expressed a desire to stab and injure a U.S. servicemember he encountered at a business. He also told the group that his own mother encouraged her children to grow up and kill Americans. Dzayee: Suggested U.S. Special Forces — specifically Green Berets — should be the drone targets. He also coordinated the money transfers, telling the group to call it “charity” and adding: “In my head it’s charity.” And here’s the kicker — Dzayee himself acknowledged the gravity. He and Ghafoor called what they were doing “treason” and admitted it was “bigger” than their existing fraud scheme. They knew exactly what they were. They said it out loud. And they kept going anyway. 🎯 THE STING: HOW THE FBI GOT THEM The investigation began in March 2025 with a single anonymous tip about pro-ISIS social media posts. Within months, the FBI had: - Infiltrated their Discord and messaging groups - Deployed undercover agents and confidential human sources - Tracked Shamsaldeen’s 90-mile crypto ATM pilgrimage via surveillance - Captured Ghafoor on tape, handing cash to an agent inside a mosque - Documented every pledge of allegiance, every violent fantasy, every dollar sent FBI Director Kash Patel didn’t mince words: “These subjects allegedly swore allegiance to ISIS, plotted multiple attacks, and even targeted U.S. servicemembers — but this FBI stopped them cold.” Acting AG Todd Blanche put the broader mission in perspective: “This administration has put terrorists, cartels, and gangs on notice. Today’s arrest makes clear our commitment to taking down terrorist networks — anywhere.” And the most haunting line from Blanche, which should sear itself into every American’s consciousness: “Young men in their 20s completely indoctrinated by terrorism and by terrorists and actually spending money to actually follow through on these attacks. It’s a good reminder to Americans that this fight is not over.” 🇺🇸 THE DEEPER TRUTH NOBODY WANTS TO SAY Here’s what the sanitized headlines won’t tell you: all three are U.S. citizens. Born or naturalized right here. One of them — Dzayee — appears in photos wearing a U.S. Navy sailor’s uniform, confirmed by neighbors and a former classmate. These aren’t foreign agents sneaking across the border. These are products of the American system, radicalized internally through their teachers and online echo chambers while the previous administration’s DOJ and intelligence agencies were busy hunting grandmothers at school board meetings and labeling concerned parents “domestic terrorists.” The Biden-era FBI spent years telling us the greatest terror threat was white supremacy in the heartland. Meanwhile, actual jihadist cells were forming on Discord, pledging allegiance to ISIS leadership, and wiring money for RPGs and drones — right under their noses. This bust happened because the Trump DOJ and Kash Patel’s FBI actually prioritized counterterrorism rather than treating it as an inconvenient distraction from political prosecutions. ⚖️ WHAT HAPPENS NOW All three face charges of conspiring to provide material support to a designated foreign terrorist organization — a charge that carries up to 20 years in federal prison. The case is being prosecuted in the District of Kansas by Assistant U.S. Attorneys Scott Rask and Michelle MacFarlane, alongside the National Security Division’s Counterterrorism Section. They’re innocent until proven guilty in a court of law. But the complaint is devastating. The paper trail is massive. And the confessions are on tape. 📢 THE TAKEAWAY The war didn’t end when we pulled out of Afghanistan. It didn’t end when Baghdadi ate a suicide vest in a Syrian tunnel. The ideology metastasized. It’s on Discord. It’s in mosques in Kansas City. It’s in the mind of a 21-year-old in Leawood who dreams of beheading female soldiers. But here’s the difference between then and now: this administration is actually hunting them. Not lecturing us about Islamophobia. Not deflecting to “stochastic terrorism” from political opponents. Actually doing counterterrorism. This is what law and order looks like. 🇺🇸 #ISISBusted #LawAndOrder #FBI #ToddBlanche #KashPatel #NationalSecurity #MaterialSupport #HomegrownTerror #AmericaFirst #TrumpDOJ #Counterterrorism #GreenBerets #ProtectOurTroops #WakeUpAmerica #DiscordJihad #Treason #JusticeServed #StopISIS

Tony Seruga

315,738 görüntüleme • 3 ay önce

🚨WARNING AMERICA: THIS IS THE GREAT REPLACEMENT - MIGRANTS ARE BEING WEAPONIZED! AMY POPE’S LATEST DELUSION: “MIGRANTS ARE MISSIONARIES OF HOPE” WHILE THE WEST DROWNS IN DEATH AND CHAOS This past October, RAIR exposed the Vatican-UN Great Replacement axis. Pope Leo XIV and UN Migration Chief Amy Pope are still marching in lockstep, and she just delivered another dangerous keynote at Villanova University’s “Refugees & Migrants in Our Common Home” summit in Rome (Pope Leo’s alma mater). She announced a three-year partnership between the IOM and this Catholic-globalist network: Villanova, Augustinian Secretariat, Jesuit Refugee Service, Scalabrini Institute, Center for Migration Studies, USCCB, and their partners. Her exact words: 🔺“We are all pilgrims… We are all migrants.” 🔺“Migrants… carry within them something greater… hope.” 🔺“Pope Leo calls on us to welcome migrants not as a burden, but as a blessing.” 🔺“Migrants are missionaries of hope. They carry gifts… that can renew our communities and even renew our faith.” She gushed about Lampedusa, Italy, boat arrivals as a “long walk of freedom” and demanded universities expand educational pathways, recognize fake qualifications, rebrand migrants as “contributors,” and build a global scholarship network. This is not compassion. This is coordinated demographic warfare wrapped in Jubilee-year piety. 🚨The Brutal Reality She Ignored in Lampedusa and Italy While Amy Pope romanticized “hope” and “gifts,” Italy’s own data shows the nightmare: 🔺Lampedusa hosted nearly 50,000 migrants in 2025 alone (Italian Red Cross figures). 🔺The island’s tiny population is under deadly attack, locals pleading for help but are abandoned. No one is safe; women, children, men, and pets have been attacked, beaten, and r*ped while the world turns a blind eye. 🔺Mediterranean deaths in 2026 are catastrophic: hundreds missing or dead, “invisible shipwrecks,” bodies washing ashore, smuggling networks running wild (IOM’s own reports confirm the bloodbath). 🔺Italy now faces skyrocketing crime, cultural erasure, parallel societies, and collapsing welfare systems in towns that never asked for this invasion. 🔺This is the “model” Pope Leo praised earlier - Christian Lebanon’s collapse, now repeating across Europe. 🔺 Amy Pope’s “missionaries of hope” are the same flows enabling jihad, no-go zones, and the Great Replacement she and the Vatican are sanctifying. 🚨Everything I’ve Already Exposed About Amy Pope - Now Weaponized Through Catholic Universities and Bishops 🔺 Amy Pope is the Obama-Biden insider who purged “jihad” from training manuals, appeased CAIR/ISNA, ran the failed CVE disaster, pushed the post-Paris #RefugeesWelcome psyop, and demolished America’s borders. 🔺As IOM boss (installed via unprecedented U.S. lobbying in 2023), she runs the $2.5+ billion UN migration machine - 67% funded by your taxes - turning invasion into a permanent globalist industry. 🔺She met privately with Pope Leo XIV right before he attacked Trump and declared mass migration the “new missionary age.” 🔺Now she’s embedding it deeper: weaponizing Pope Leo’s alma mater + USCCB + Jesuits + Scalabrini to train the next generation of activists, scholars, and clergy to push open borders, call invaders “blessings,” and brand critics un-Christian. ⚠️This is the Great Replacement - now with academic degrees, Jesuit blessings, and a three-year action plan. Trump already has the roadmap I laid out in October: Defund the IOM completely. Withdraw from the UN migration network. Audit every dollar. End the church-contractor grift machine. America is not the world’s orphanage. Protecting our borders, our culture, and our children is not cruelty; it’s survival.
6:49

🚨WARNING AMERICA: THIS IS THE GREAT REPLACEMENT - MIGRANTS ARE BEING WEAPONIZED! AMY POPE’S LATEST DELUSION: “MIGRANTS ARE MISSIONARIES OF HOPE” WHILE THE WEST DROWNS IN DEATH AND CHAOS This past October, RAIR exposed the Vatican-UN Great Replacement axis. Pope Leo XIV and UN Migration Chief Amy Pope are still marching in lockstep, and she just delivered another dangerous keynote at Villanova University’s “Refugees & Migrants in Our Common Home” summit in Rome (Pope Leo’s alma mater). She announced a three-year partnership between the IOM and this Catholic-globalist network: Villanova, Augustinian Secretariat, Jesuit Refugee Service, Scalabrini Institute, Center for Migration Studies, USCCB, and their partners. Her exact words: 🔺“We are all pilgrims… We are all migrants.” 🔺“Migrants… carry within them something greater… hope.” 🔺“Pope Leo calls on us to welcome migrants not as a burden, but as a blessing.” 🔺“Migrants are missionaries of hope. They carry gifts… that can renew our communities and even renew our faith.” She gushed about Lampedusa, Italy, boat arrivals as a “long walk of freedom” and demanded universities expand educational pathways, recognize fake qualifications, rebrand migrants as “contributors,” and build a global scholarship network. This is not compassion. This is coordinated demographic warfare wrapped in Jubilee-year piety. 🚨The Brutal Reality She Ignored in Lampedusa and Italy While Amy Pope romanticized “hope” and “gifts,” Italy’s own data shows the nightmare: 🔺Lampedusa hosted nearly 50,000 migrants in 2025 alone (Italian Red Cross figures). 🔺The island’s tiny population is under deadly attack, locals pleading for help but are abandoned. No one is safe; women, children, men, and pets have been attacked, beaten, and r*ped while the world turns a blind eye. 🔺Mediterranean deaths in 2026 are catastrophic: hundreds missing or dead, “invisible shipwrecks,” bodies washing ashore, smuggling networks running wild (IOM’s own reports confirm the bloodbath). 🔺Italy now faces skyrocketing crime, cultural erasure, parallel societies, and collapsing welfare systems in towns that never asked for this invasion. 🔺This is the “model” Pope Leo praised earlier - Christian Lebanon’s collapse, now repeating across Europe. 🔺 Amy Pope’s “missionaries of hope” are the same flows enabling jihad, no-go zones, and the Great Replacement she and the Vatican are sanctifying. 🚨Everything I’ve Already Exposed About Amy Pope - Now Weaponized Through Catholic Universities and Bishops 🔺 Amy Pope is the Obama-Biden insider who purged “jihad” from training manuals, appeased CAIR/ISNA, ran the failed CVE disaster, pushed the post-Paris #RefugeesWelcome psyop, and demolished America’s borders. 🔺As IOM boss (installed via unprecedented U.S. lobbying in 2023), she runs the $2.5+ billion UN migration machine - 67% funded by your taxes - turning invasion into a permanent globalist industry. 🔺She met privately with Pope Leo XIV right before he attacked Trump and declared mass migration the “new missionary age.” 🔺Now she’s embedding it deeper: weaponizing Pope Leo’s alma mater + USCCB + Jesuits + Scalabrini to train the next generation of activists, scholars, and clergy to push open borders, call invaders “blessings,” and brand critics un-Christian. ⚠️This is the Great Replacement - now with academic degrees, Jesuit blessings, and a three-year action plan. Trump already has the roadmap I laid out in October: Defund the IOM completely. Withdraw from the UN migration network. Audit every dollar. End the church-contractor grift machine. America is not the world’s orphanage. Protecting our borders, our culture, and our children is not cruelty; it’s survival.

Amy Mek

54,536 görüntüleme • 5 ay önce

//The Wire//2300Z September 1, 2026// //ROUTINE// //BLUF: UNITED STATES LAUNCHES NEW WAVES OF ATTACKS IN MIDDLE EAST. IRAN RETALIATES BY STRIKING AMERICAN AIRBASES AND MULTIPLE TANKERS IN STRAIT OF HORMUZ. RUSSIA CONFIRMS MATERIEL SUPPORT FOR IRAN. SECRETARY OF THE ARMY RESIGNS IN WASHINGTON. IEDS DISCOVERED AT ELECTRICAL SUBSTATION IN GERMANY.// -----BEGIN TEARLINE----- -International Events- Middle East: Overnight, Iranian targeting of merchant shipping continued, with a total of 3-4x vessels being struck since the targeting in the Strait of Hormuz re-ignited over the weekend. At least two of these targeting efforts involved VLCC tankers being struck as they attempted to exit the gulf. The M/T SIDR and the M/T SENEGAL PROSPERITY were hit by unidentified munitions (one of these ships was hit three times), with the effect of the targeting being a halt of their transit through the Strait. This afternoon, the United States conducted larger-scale attacks on Iran, continuing the strikes that kicked off the fighting again over the weekend. The United States struck targets on Qeshm Island, Sirik Island, the port of Chabarhar, and several other targets along the Iranian coastline. After these strikes took place, Iran launched more missiles at American bases throughout the region (mostly in Jordan and Kuwait). As of this report over 20x Iranian ballistic missiles have been launched, with the launches continuing into the evening. Europe: Over the past few days, the war in Ukraine has become increasingly more serious, as Russian and Ukrainian attacks on each others' infrastructure have intensified. Over the past two days, large-scale waves of drone and missile attacks have been reported, with Russia and Ukraine focusing on targeting Kiev and St. Petersburg respectively. Several dozen smaller cities on both sides have also reported missile and drone impacts within the past 48 hours. Germany: This morning several explosive devices were discovered near a electrical substation at the Jänschwalde Power Plant southeast of Berlin. Several IEDs were discovered at this location by workers, though the exact number and composition of the devices has not yet been disclosed. Analyst Comment: Details of what actually happened at this substation are very hard to come by. Initial reports suggested that workers found IEDs at the site, but throughout the afternoon other reports emerged indicating that these were actually warheads from improvised mortars/rockets, which landed at the substation and failed to explode and/or had a different purpose altogether. Some reports from local sources in the community claim that rockets were found that contained "conductive material" which were fired over the top of electrical transmission lines at this location. This undescribed conductive material caused an electrical short on two transmission lines, which took out the power for a few hours. If these details are accurate, this would be a deliberate infrastructure attack, though the culprits could be anyone from climate groups, to foreign nationstates. More details are expected as the situation develops. Kyrgyzstan: As part of the Shanghai Cooperation Organization (SCO) summit, Russian President Vladimir Putin met with Iranian President Masoud Pezeshkian for a series of press conferences and brief talks. During the media events, President Putin directly stated that Russia is providing resources to Iran to help circumvent the effects of the American blockade on Iranian ports. Analyst Comment: While this is certainly no big secret, Putin saying this openly is a message to the United States, which is probably a tit-for-tat response to the global west arming Ukraine for years. Though it is largely forgotten, Iran actually does share a border with Russia, but it's not by land...it's via the Caspian Sea. Russian boats can easily transfer large amounts of cargo to Iranian ports on the northern coast of Iran, in addition to the large-scale railway projects in the northern districts, which serve as vital logistical lines to Russia and China. -HomeFront- Mississippi: Yesterday afternoon, a major fire was reported at an industrial facility in Laurel, which began after a truck caught fire near a paint locker at the Howard Industries facility which produces electrical transformers. The initial fire sparked a much larger blaze that consumed much of the main factory complex as well as the storage yard for large transformers. Analyst Comment: The U.S. imports about 80% of the electrical transformers needed to keep the electrical grid functioning, and as recently as May of this year, the industry was facing a dire shortage of transformers (a shortage which has been problematic for years). Howard Industries is a major domestic US producer of transformers, producing over 10 million transformers that are still in service around the nation. This company has a total of 14 different factories around the state, but even just one facility being offline (and the stored transformers being lost in the fire) will probably negatively impact the nationwide shortage of these critically-needed components. Washington D.C. - Last night Dan Driscoll, the Secretary of the Army, reportedly tendered his resignation to President Trump. Dave Fitzgerald, the Deputy Undersecretary of the Army is also expected to resign sometime this week. Analyst Comment: These resignations are extremely important, and very significant during a time of war. Normally, the resignation of the Secretary of the Army during an active conflict is something that is a major indicator of things not going well in upper management circles, however the terms of Driscoll's resignation also add more fuel to the fire. Allegedly, Driscoll resigned due to clashes with SECWAR Hegseth regarding the operational readiness of the Army. Officially, Driscoll's resignation has not been confirmed from official sources, and he himself has not commented on the reasons for his departure, so until he does, it could be for any number of reasons. However, the timing of the resignation the day after the war reignites (and indications are growing of shaping operations being prepared), is quite coincidental for this to be unrelated. -----END TEARLINE----- Analyst Comments: It will take a few more days before the dust settles and proper assessments of battle damage can be conducted regarding the latest rounds of targeting both in the Middle East and in Ukraine. As it stands right now, the war in Ukraine remains very hot and very active, and the war in the Middle East has ebbed and flowed as the United States adopts more of a "mowing the lawn" approach to the conflict (or at least, that seems to be the motivation for the latest round of strikes). Separately, time is running out on the petroleum front, and the attempts to mitigate the energy crisis have not been as effective as hoped for. The American operation to shuttle tankers back-and-forth through the Strait, to play a grand shell game of shuttling oil from ship-to-ship once in the Gulf of Oman has had some positive impact. How much impact is hard to say, because how the data is being counted can be framed in many different ways to support various contradictory arguments, but right now (as per Kpler) the bottom-line figure for how much oil is exiting the Gulf via the Strait is 8.6 million bbl/day (or at least it was during the lull over the past month). Since Kpler did not factor in the Saudi East-West pipeline for this figure, we have to add that critical resource to the overall total. However Kpler also confirmed that as of July, these two pipelines that are supposedly rated for allowing around 7 million barrels per day to bypass the Strait...were only resulting in a total export of 1 million barrels, a fraction of what the ecosystem is rated for. The reason for this, is the bottleneck at the ports. Even loading oil onto ships as fast as humanly possible, they can only manage to get 1 million barrels out per day. It doesn't matter how fast the oil flows through a pipeline, if it cannot flow onto ships at the same rate, and right now, the oil terminals on the Saudi coastline are the weakest link in the chain. These bottlenecks, combined with the Houthi attacks on the Jazan refinery, have sharply reduced the main alternative method for bypassing the Strait with at least some petroleum product. Around the region more optimistic reports indicate that, all total, as much as half of the world's pre-war needs have been met by the efforts to get oil out of the Gulf region. Even with all of the tricks we've tried (and factoring in Omani-shuttle operations AND the Saudi bypass pipeline), we're only reaching "half of normal", at best. As this 8.6 million bbl/day figure is the absolute maximum theoretical figure (due to much of this oil being secretly transferred between ships as part of the shell game), there is variance in the data. Regardless of how it's counted, 8.6 million barrels is most assuredly welcome, but it's still nowhere near enough to prevent the civilization-level energy crisis that the entire planet is experiencing at present. Now that the tit-for-tat strikes have resumed over the past few days, this absolute-best-case-scenario figure of 9 million barrels per day is likely to be reduced quite a bit. Looking forward over the next few weeks, this crisis will probably be complicated even further by a decline in demand; most major prediction models project a decline in demand due to the petroleum shortage going on for so long now. Also, the American Strategic Petroleum Reserve (SPR) will be running dry soon, to the point that tank-bottom will be approaching within a couple of weeks, if the current rates of release continue. Now that the war has resumed somewhat (and oil prices are spiking), solutions do not look very likely for the time being. Analyst: S2A1 Research: NomadNet: 5fa68c88be727a0e1a250a75e5e79269 Disclaimer: No LLMs were used in the writing of this report. //END REPORT//
8:18

//The Wire//2300Z September 1, 2026// //ROUTINE// //BLUF: UNITED STATES LAUNCHES NEW WAVES OF ATTACKS IN MIDDLE EAST. IRAN RETALIATES BY STRIKING AMERICAN AIRBASES AND MULTIPLE TANKERS IN STRAIT OF HORMUZ. RUSSIA CONFIRMS MATERIEL SUPPORT FOR IRAN. SECRETARY OF THE ARMY RESIGNS IN WASHINGTON. IEDS DISCOVERED AT ELECTRICAL SUBSTATION IN GERMANY.// -----BEGIN TEARLINE----- -International Events- Middle East: Overnight, Iranian targeting of merchant shipping continued, with a total of 3-4x vessels being struck since the targeting in the Strait of Hormuz re-ignited over the weekend. At least two of these targeting efforts involved VLCC tankers being struck as they attempted to exit the gulf. The M/T SIDR and the M/T SENEGAL PROSPERITY were hit by unidentified munitions (one of these ships was hit three times), with the effect of the targeting being a halt of their transit through the Strait. This afternoon, the United States conducted larger-scale attacks on Iran, continuing the strikes that kicked off the fighting again over the weekend. The United States struck targets on Qeshm Island, Sirik Island, the port of Chabarhar, and several other targets along the Iranian coastline. After these strikes took place, Iran launched more missiles at American bases throughout the region (mostly in Jordan and Kuwait). As of this report over 20x Iranian ballistic missiles have been launched, with the launches continuing into the evening. Europe: Over the past few days, the war in Ukraine has become increasingly more serious, as Russian and Ukrainian attacks on each others' infrastructure have intensified. Over the past two days, large-scale waves of drone and missile attacks have been reported, with Russia and Ukraine focusing on targeting Kiev and St. Petersburg respectively. Several dozen smaller cities on both sides have also reported missile and drone impacts within the past 48 hours. Germany: This morning several explosive devices were discovered near a electrical substation at the Jänschwalde Power Plant southeast of Berlin. Several IEDs were discovered at this location by workers, though the exact number and composition of the devices has not yet been disclosed. Analyst Comment: Details of what actually happened at this substation are very hard to come by. Initial reports suggested that workers found IEDs at the site, but throughout the afternoon other reports emerged indicating that these were actually warheads from improvised mortars/rockets, which landed at the substation and failed to explode and/or had a different purpose altogether. Some reports from local sources in the community claim that rockets were found that contained "conductive material" which were fired over the top of electrical transmission lines at this location. This undescribed conductive material caused an electrical short on two transmission lines, which took out the power for a few hours. If these details are accurate, this would be a deliberate infrastructure attack, though the culprits could be anyone from climate groups, to foreign nationstates. More details are expected as the situation develops. Kyrgyzstan: As part of the Shanghai Cooperation Organization (SCO) summit, Russian President Vladimir Putin met with Iranian President Masoud Pezeshkian for a series of press conferences and brief talks. During the media events, President Putin directly stated that Russia is providing resources to Iran to help circumvent the effects of the American blockade on Iranian ports. Analyst Comment: While this is certainly no big secret, Putin saying this openly is a message to the United States, which is probably a tit-for-tat response to the global west arming Ukraine for years. Though it is largely forgotten, Iran actually does share a border with Russia, but it's not by land...it's via the Caspian Sea. Russian boats can easily transfer large amounts of cargo to Iranian ports on the northern coast of Iran, in addition to the large-scale railway projects in the northern districts, which serve as vital logistical lines to Russia and China. -HomeFront- Mississippi: Yesterday afternoon, a major fire was reported at an industrial facility in Laurel, which began after a truck caught fire near a paint locker at the Howard Industries facility which produces electrical transformers. The initial fire sparked a much larger blaze that consumed much of the main factory complex as well as the storage yard for large transformers. Analyst Comment: The U.S. imports about 80% of the electrical transformers needed to keep the electrical grid functioning, and as recently as May of this year, the industry was facing a dire shortage of transformers (a shortage which has been problematic for years). Howard Industries is a major domestic US producer of transformers, producing over 10 million transformers that are still in service around the nation. This company has a total of 14 different factories around the state, but even just one facility being offline (and the stored transformers being lost in the fire) will probably negatively impact the nationwide shortage of these critically-needed components. Washington D.C. - Last night Dan Driscoll, the Secretary of the Army, reportedly tendered his resignation to President Trump. Dave Fitzgerald, the Deputy Undersecretary of the Army is also expected to resign sometime this week. Analyst Comment: These resignations are extremely important, and very significant during a time of war. Normally, the resignation of the Secretary of the Army during an active conflict is something that is a major indicator of things not going well in upper management circles, however the terms of Driscoll's resignation also add more fuel to the fire. Allegedly, Driscoll resigned due to clashes with SECWAR Hegseth regarding the operational readiness of the Army. Officially, Driscoll's resignation has not been confirmed from official sources, and he himself has not commented on the reasons for his departure, so until he does, it could be for any number of reasons. However, the timing of the resignation the day after the war reignites (and indications are growing of shaping operations being prepared), is quite coincidental for this to be unrelated. -----END TEARLINE----- Analyst Comments: It will take a few more days before the dust settles and proper assessments of battle damage can be conducted regarding the latest rounds of targeting both in the Middle East and in Ukraine. As it stands right now, the war in Ukraine remains very hot and very active, and the war in the Middle East has ebbed and flowed as the United States adopts more of a "mowing the lawn" approach to the conflict (or at least, that seems to be the motivation for the latest round of strikes). Separately, time is running out on the petroleum front, and the attempts to mitigate the energy crisis have not been as effective as hoped for. The American operation to shuttle tankers back-and-forth through the Strait, to play a grand shell game of shuttling oil from ship-to-ship once in the Gulf of Oman has had some positive impact. How much impact is hard to say, because how the data is being counted can be framed in many different ways to support various contradictory arguments, but right now (as per Kpler) the bottom-line figure for how much oil is exiting the Gulf via the Strait is 8.6 million bbl/day (or at least it was during the lull over the past month). Since Kpler did not factor in the Saudi East-West pipeline for this figure, we have to add that critical resource to the overall total. However Kpler also confirmed that as of July, these two pipelines that are supposedly rated for allowing around 7 million barrels per day to bypass the Strait...were only resulting in a total export of 1 million barrels, a fraction of what the ecosystem is rated for. The reason for this, is the bottleneck at the ports. Even loading oil onto ships as fast as humanly possible, they can only manage to get 1 million barrels out per day. It doesn't matter how fast the oil flows through a pipeline, if it cannot flow onto ships at the same rate, and right now, the oil terminals on the Saudi coastline are the weakest link in the chain. These bottlenecks, combined with the Houthi attacks on the Jazan refinery, have sharply reduced the main alternative method for bypassing the Strait with at least some petroleum product. Around the region more optimistic reports indicate that, all total, as much as half of the world's pre-war needs have been met by the efforts to get oil out of the Gulf region. Even with all of the tricks we've tried (and factoring in Omani-shuttle operations AND the Saudi bypass pipeline), we're only reaching "half of normal", at best. As this 8.6 million bbl/day figure is the absolute maximum theoretical figure (due to much of this oil being secretly transferred between ships as part of the shell game), there is variance in the data. Regardless of how it's counted, 8.6 million barrels is most assuredly welcome, but it's still nowhere near enough to prevent the civilization-level energy crisis that the entire planet is experiencing at present. Now that the tit-for-tat strikes have resumed over the past few days, this absolute-best-case-scenario figure of 9 million barrels per day is likely to be reduced quite a bit. Looking forward over the next few weeks, this crisis will probably be complicated even further by a decline in demand; most major prediction models project a decline in demand due to the petroleum shortage going on for so long now. Also, the American Strategic Petroleum Reserve (SPR) will be running dry soon, to the point that tank-bottom will be approaching within a couple of weeks, if the current rates of release continue. Now that the war has resumed somewhat (and oil prices are spiking), solutions do not look very likely for the time being. Analyst: S2A1 Research: NomadNet: 5fa68c88be727a0e1a250a75e5e79269 Disclaimer: No LLMs were used in the writing of this report. //END REPORT//

S2 Underground

13,045 görüntüleme • 15 gün önce