正在加载视频...

视频加载失败

Aspiration thrombectomy in STEMI with a heavy thrombus burden, maybe it’s time to take another look? Had a 37F with a huge RCA thrombus. Did 6 Penumbra aspiration runs and pulled out a large amount of clot. Hard to see how this would’ve resolved. Cases like this make you...

18,728 次观看 • 3 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

💡 Ready to witness the future of cardiovascular #innovation? Join Philippe Genereux as he unveils the highly anticipated results of the EARLY TAVR trial, debuting on Monday, October 28! Get an exclusive look at first-time presentations of key clinical trials and groundbreaking studies at #TCT2024! Don’t miss out—reserve your spot today: 📅 Explore the full schedule of late-breaking trials and cutting-edge science. Check it out here: #CardioX #CardioTwitter #CardioEd #CardioResearch Dan Burkhoff MD PhD David J. Cohen, MD, MSc George Dangas, MD, MACC, MSCAI Juan F. Granada Marty Leon Akiko Maehara Dr Roxana Mehran Sahil A. Parikh, MD Tricia Rawh TCT Conference jedicath աǟզǟʀ.ǟɦʍɛɖ إبراهيم الحربي Ibrahim Alharbi Abdelkader Almanfi, MD, FACC, FSCAI Hooman Bakhshi Alessandro Beneduce Nyal Borges Aaysha Cader BCaseMD Nishith Chandra Bailey Ann Richardson David L. Fischman Prof. Hector M. Garcia-Garcia Julia Grapsa Nadira Hamid Stefan Harb @AmandaLimaMD Evandro Martins F. MD Giorgio A. Medranda MD, FACC, FAHA, FSCAI Neisser M Srihari S. Naidu, MD sumonroy Michael Savage Muhammad Shuaib Abid Pooja Swamy, MD, FACC, FSCAI Ritu Thamman MD Anuradha Tunuguntla MD FACC FSCAI Poonam Velagapudi Edoardo Zancanaro MD Adriana C. Mares Niels R. Holm Abhishek Chaturvedi MD, FACC, FSCAI Krutarth Pandya Indah Sukmawati, MD Shariq Shamim MIЯVΛƬ #IC ༄ 。°
1:19

Sensitive content

💡 Ready to witness the future of cardiovascular #innovation? Join Philippe Genereux as he unveils the highly anticipated results of the EARLY TAVR trial, debuting on Monday, October 28! Get an exclusive look at first-time presentations of key clinical trials and groundbreaking studies at #TCT2024! Don’t miss out—reserve your spot today: 📅 Explore the full schedule of late-breaking trials and cutting-edge science. Check it out here: #CardioX #CardioTwitter #CardioEd #CardioResearch Dan Burkhoff MD PhD David J. Cohen, MD, MSc George Dangas, MD, MACC, MSCAI Juan F. Granada Marty Leon Akiko Maehara Dr Roxana Mehran Sahil A. Parikh, MD Tricia Rawh TCT Conference jedicath աǟզǟʀ.ǟɦʍɛɖ إبراهيم الحربي Ibrahim Alharbi Abdelkader Almanfi, MD, FACC, FSCAI Hooman Bakhshi Alessandro Beneduce Nyal Borges Aaysha Cader BCaseMD Nishith Chandra Bailey Ann Richardson David L. Fischman Prof. Hector M. Garcia-Garcia Julia Grapsa Nadira Hamid Stefan Harb @AmandaLimaMD Evandro Martins F. MD Giorgio A. Medranda MD, FACC, FAHA, FSCAI Neisser M Srihari S. Naidu, MD sumonroy Michael Savage Muhammad Shuaib Abid Pooja Swamy, MD, FACC, FSCAI Ritu Thamman MD Anuradha Tunuguntla MD FACC FSCAI Poonam Velagapudi Edoardo Zancanaro MD Adriana C. Mares Niels R. Holm Abhishek Chaturvedi MD, FACC, FSCAI Krutarth Pandya Indah Sukmawati, MD Shariq Shamim MIЯVΛƬ #IC ༄ 。°

Cardiovascular Research Foundation

16,807 次观看 • 1 年前

AI AGENTS 101 (58 minute free masterclass) send this to anyone who wants to understand ai agents, claude skills, md files, how to get the most out of AI etc in plain english: 1. chat vs agents - chat models answer questions in a back and forth while agents take a goal, figure out the steps, and deliver a result 2. agents don’t stop after one response. they keep running until the task is actually finishedno babysitting required 3. everything runs on a loop. they gather context, decide what to do, take an action, then repeat until done 4. the loop is the system. they look at files, tools, and the internet. decide the next step. execute and then feed that back into the next step. over and over until completion 5. the model is just one piece. gpt, claude, gemini are the reasoning layer. the key is model + loop + tools + context 6. mcp is how agents use tools. it connects things like browser, code, apis, and your internal software. once connected, the agent decides when to use them to get the job done 7. context beats prompt all day. you don't need to write perfect prompts. load your agent with context about your business, style, and goals and then simple instructions work 8. claude.md or agents.md is the onboarding doc it tells the agent who it is, how to behave, what it knows, and what tools it can use. this gets loaded every time before it starts 9. memory.md is how it improves. agents don’t remember by default. this file stores preferences, corrections, and patterns you tell the agent to update it, and it gets better over time 10. skills + harnesses make it usable. skills are reusable tasks like writing, research, analysis the harness is the environment like claude code or openclaw that runs everything. basiclaly, different interfaces, same system underneath this episode with remy on The Startup Ideas Podcast (SIP) 🧃 was one of the clearest ways of understanding a lot of the core concepts of ai agents could be the best beginners course for ai agents 58 mins. all free. no advertisers. i just want to see you build cool stuff. im rooting for you. send to a friend watch

GREG ISENBERG

375,365 次观看 • 4 个月前

Very powerful testimony by dr. Sabine Hazan "Thank you, senator. It's an honor to be here. The microbiome, our microbes in our guts, is our immunity and tells the story and will tell the story of COVID nineteen. And this is why as a gastroenterologist, I stepped into the pandemic. Through my experience, I will show you how difficult it was to conduct research and publish when the research goes against the national public health narrative." "Interference and delay in research happened and affects all of us. In early twenty twenty, my research genetic sequencing laboratory was the first lab to document the entire sequence of the virus in the stools as opposed to the PCR which is just a little piece of the virus." "We discovered that the virus lingered in the stools for up to forty five days. It took six months to publish this publication at a time where everybody needed to know that it was in your stools. My lab also showed that COVID nineteen in the stools was killed by hydroxychloroquine and azithromycin." "But unfortunately, azithromycin and hydroxychloroquine killed the microbiome. So therefore, vitamin c, d, and zinc was added. Three protocols were submitted to the FDA from our findings. Three studies were also put into in full transparencies to help doctors more effectively treat COVID because I knew data that nobody knew. 04/02/2020, FDA gave us an exempt letter for doing a clinical trial." "In other words, we did not need to do a clinical trial on hydroxychloroquine, z pack, vitamin c, d, and zinc as treatment or hydroxychloroquine, vitamin c, d, and zinc as prophylaxis. April 4, somebody must have called the FDA and said, I got another letter saying, I'm sorry, doctor Hazan. Exemption is denied. You must do a full on clinical trial. Here's the letter." "System pressures delayed us, and we got a green light to start recruiting by May 2020. By then, the media created fear around hydroxychloroquine. It was impossible to recruit. This drug was safely given for years for arthritis and lupus with no problems. My clinical trials companies were also banned and censored from advertising on Facebook, Instagram, and Twitter." "Remember, I do clinical trials for a living and never as a clinical trial doctor have I not been able to advertise to recruit for a trial on social media. I kept collecting stools of patients and noticed that patients with severe COVID had a certain bacteria that was missing compared to people that were highly exposed to COVID but never got COVID. That bacteria is called bifidobacteria. Bifidobacteria is an important and key microbe for immunity. It represents your trillion dollar industry of probiotics." "In fact, when you turn the bottle and you see the ingredient, it says bifidobacteria. It is present in newborns. This is why your newborns did not get a problem from COVID at the beginning, and it is absent in old people. The process of aging is loss of bifidobacteria. We published this paper, the lost microbes of COVID nineteen." "It took eight months to publish. If you follow the bifidobacteria like I did, you will notice, and we did notice anyways, that vitamin c actually increases bifidobacteria. This is why vitamin c is important when you take when you take care of viruses and, you know, you've all experienced taking vitamin c for a cold." "Well, we published this data where we showed vitamin c, if we give it to patients before and after, it increased the bifidobacteria. Ivermectin was also an interesting drug because Ivermectin, we noticed, also increased the bifidobacteria within twenty four hours of taking it." "Why Ivermectin? If you look at what Ivermectin is, it is a fermented product of a bacteria that is similar to bifidobacteria. In fact, they're in the same continent of microbes. They live. They're like sisters, brothers in the microbiome." "So I published. I knew that ivermectin increased bifidobacteria, but I said, nah. I can't go out there and start publishing that. That's gonna be too controversial. So I published a hypothesis that maybe what I was observing on the frontline treating patients with COVID, noticing that their oxygen saturation was increasing from ivermectin, was basically maybe ivermectin increased bifidobacteria." "The hypothesis on ivermectin was the most read hypothesis in the pandemic and was retracted after eight months of being on. When we cannot make a hypothesis, this is not science. December twenty twenty, at the same time that I was treating patients with COVID, I began collecting stools of my colleagues that were at home and started going into the hospital. And I said, can I get your stools before and after you get vaccinated? Because to me, this new technology of vaccines, I wanted to see what it was doing on the microbiome." "I discovered that messenger RNA vaccines killed the bifidobacteria. I knew I would never be able to publish this because it goes against the narrative. So I submitted it to my college, the American College of Gastroenterology, and presented it in October 2022. This abstract won a research award at the American College of Gastro beating 6,000 abstracts. That's from academic centers like Harvard and Mayo Clinic and MD Anderson." "This abstract got the attention of 18,000 GI doctors who all of a sudden started realizing maybe killing bifidobacteria is why I got COVID after my vaccine to begin with. Worse than that, and another abstract we presented, was the persistent damage of bifidobacteria from the vaccine." "What is going on here that the vaccine continues to kill the bifidobacteria? At the same time, we presented a link between loss of bifidobacteria and Crohn's disease, loss of bifidobacteria in Lyme disease, and loss of bifidobacteria in invasive cancer. It is nearly impossible to publish data that goes against the national public health narrative." "If doctors cannot publish the data, they cannot find solution to fix the problems. So in conclusion, I will finish with showing this. This represents clinical trials that I've done for pharmaceutical companies prior to COVID. Amongst them are vaccine studies. Yes." "I brought vaccines to the market. Proton pump inhibitors, cardiac drugs, biologics for all sorts of conditions. First, postpartum depression drug, drugs that never made it to the market because they killed people. Clinical trials doctors follow guidelines that allows the industry to provide safe drugs. These guidelines were not followed during the pandemic." "And because of that, everyone is affected. COVID should have been a time where humanity joined forces together and doctors needed to come together. It's a shame that it didn't happen. Interference with research affects all of us. This should not be political." "Science is a story that evolves. It's a multitude of experiments that allow us to see medicine, to give hopes to patients. Skepticism, challenging the current state of knowledge. Having an open mind must be allowed if we have any hope of moving science forward. What I saw this pandemic was not science. Thank you."

Camus

127,765 次观看 • 1 年前

CANCEL Your Weekend Plans, & Learn Claude Code Today. This Claude Code teaches more about vibe-coding in 30 mins than most tutorials do in hours. Save this, it'll change how you build forever People are building entire apps and charging clients $5,000 to $20,000 using Claude Code. This Claude Code video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumarfor daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.

Himanshu Kumar

85,668 次观看 • 2 个月前

CANCEL Your Weekend Plans, and Learn Claude Code Today. $5,000/month. $10,000/month. $20,000/month. People are building entire apps and charging clients thousands using Claude Code. You're still Googling 'how to center a div.' While you're binge-watching a show you won't remember next week, a 19 year old with zero coding experience just built a $5,000 SaaS product in one afternoon using the tool I'm about to break down. Same laptop. Same internet. Same 24 hours. He has Claude Code. You have Netflix. That's the only difference. This YouTube video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Save this post. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude.MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumar for daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.

Himanshu Kumar

101,105 次观看 • 3 个月前

I asked Grok to summarize the overview I provided of the ongoing war between Karen Read and Aidan Kearney, in particular the section wherein I deploy the Manhattan Project to explain why Karen used better compartmentalization than Aidan (thus setting herself up for victory). The Manhattan Project Analogy: Ah, the Manhattan Project—Grant drops this as the "archetypal example" of compartmentalization, using it to explain why no one (not even insiders) sees the full picture in ops like Karen's or Aidan's. It's not just history; it's a blueprint for why leaks like this recording hit so hard. Here's Grant's breakdown, paraphrased and expanded for context: Historical Setup: During WWII, the U.S. raced to build the atomic bomb. Led by J. Robert Oppenheimer at Los Alamos, NM (desert isolation for secrecy), it involved ~130,000 people total—but zero full-picture access for most. Goal: Win the war without leaks (or Japanese spies spotting it). Core Mechanic: Siloed Knowledge: Los Alamos: Elite scientists (e.g., Oppenheimer) handled core R&D. Even here, info was need-to-know—e.g., Operation Paperclip Nazis like Wernher von Braun (V-2 rocket guy) worked alongside possible communist sympathizers, but no one knew the endgame. Oak Ridge, Tennessee: The "production" hub—a secret 20,000-person "government town" (still exists today). To hide from aerial recon, they draped canopies over the entire site to mimic forest. Workers (engineers, laborers) toiled in ignorance: Example: A guy feeds a single punch card (1940s code line) into a massive green computer. He doesn't know what it codes, why, or even the machine's purpose. Just: Insert, output, repeat. Multiply by thousands—boom, uranium enrichment without risk. Why It Worked: "You do that with all the people working on a project that's very top secret (except for a select few high up)." Weak links? Minimal. One leak doesn't topple it. Ties to the Drama: Grant flips this to modern players. Aidan's Version: Rudimentary—paralegals like Olivia/Tina handle PR/logins but don't see the "full picture" (e.g., his flip risks). Meredith O'Neill becomes the leak about the recording played for her at lunch because she is smart and she does eventually see too much (just like Lindsey Gaetani before her). Karen's Mastery: Pro-level. Her finance/academia fam (Bentley University ties) screams gov recruitment pipeline—academia as "front" for talent scouting (e.g., intel via international money flows). She "understands the apparatus" (DNI hierarchy), so she deploys limited hangouts/double agents like Natalie. Result: Aidan’s recording "signal flare" to Alan Jackson and David Yannetti (his flip threat) gets mirrored by Karen's public nuke after the recordings and Read's messages to Flipperhead are released—eroding Kearney's base without directly exposing Karen's crushing blow. Grant's Point: Kate Peter/Tully are "children" at this; Karen's moves (e.g., burning Aidan now) only make sense through this lens. It's not emotion—it's chess: "If you show Karen Read anything less than respect, she's gonna fucking own you." Grant wraps by noting Karen's parasocial "complex" (stronger than Aidan's "brand") gives her leverage. He admits partiality ("I think she's responsible for John's death") but respects her ops savvy—possibly from her dad or self-taught intel. **Transcript: Grant's Analysis on Karen Read's Tactical Maneuvering and Compartmentalization** [Warning against crossing Karen Read] Grant: Listen—I would have told you this. I probably said it on stream before. You are out of your mind if you fuck with Karen Read. Like—it's one thing if you are like on her level and matching wits with her—like she's gonna grudgingly show you respect. I'm telling you—I've seen it in her eyes—but you can't fuck with her, and you certainly can't threaten her. I would not do that. I don't know who the fuck her parents know. I don't know who she knows, but bro—like it's politics. She's smarter than you. Don't threaten her. What the fuck? And that is something—like if you show her anything less than respect, she's gonna fucking own you. And that's what she did. Because the respectful way to do it would have been like a diplomatic meeting. And they must have been at a point where Aidan couldn't get that. So he did the most disrespectful thing possible where he tried to like corner her through like extortion almost. That's what it sounds like—although Aidan denies it. That—listen—forget about like how a normal person would react. When you're talking about a very influential operator like Karen Read—who has this very savvy understanding of the public mind—you're fucked. Because she's gonna know immediately what you just did. And she's gonna counter it with the thing that's gonna hurt you the most. What's gonna hurt Aidan Kearney the most? His support being dwindled down to only his core loyalists. And if he's right—and you'll hear it in the conversation—if Aidan Kearney is right, that most of who he is is because Karen Read and her support—oh my goodness, folks—like that—that means that Karen controls whether Aidan can continue this fight. If Karen—when she—that's why I want to listen to this whole conversation—there's no doubt in my mind she's pulling his support and pulling the rug under him because she's afraid that either he cooperated or he's going to cooperate. If she pulls the rug from him—okay, listen—he might be able to escape the criminal charges, but do you think Aidan Kearney—a man who thrives, in my opinion, on attention, numbers—from knowing that your words are impacting someone or the platform is reaching people—do you think he's going to enjoy being in a position where he—the very people who made him—and it wasn't just Karen; it was her supporters—now loathe his existence? And he—not just that—they are like tactical operators. Clearly Karen knows how to do counter intel—especially if she sent Natalie as a double agent to get information from the state police using Kearney as leverage all the way back in 2023. She understands the world of intel. I don't know how—I think it's her dad. I'm pretty sure because—and it could be her too—because like you don't get involved in the world of international finance on a fucking—like—what is it—the sort of leisurely level. It's not a pastime. You either do it because like—you're really fucking good at making money from the stock market—or—and these two weren't; they're not that wealthy—or you're giving information to the government. Why do I say that? Because the world of international finance is the most valuable intel sector you could possibly imagine. You can commit or try to commit any number of international crimes if you're threatening the United States of America. But I guarantee you're moving money around to do it. So who's the best possible sources for that? High-level financial people. So I don't know if either they were a Jason—and they were also academics. Okay. And a lot—what folks have to understand is when I—when people say like academia—it does not mean that you are just smart. Anyone who—who's good at studying could become a professor and be in academia. What a lot of folks should understand is that academia is a front for the government. It has always been a front for the government. Where do you think they headhunt from? Academia—well like—at the higher you get up the academic ladder—all you're really doing is getting more and more involved in the government. I'm not saying anything that anyone involved with this does not know. Like high-level academics are involved with the government. That's like the backbone of our system. Now a lot of the actual education—I think it's gotten a little out of hand with some of these majors, some of these colleges and universities who are offering [them]. That's not the point. The point is to create a—curate a talent pool to make the United States stronger. And a lot of it is government recruitment. Okay. And so Karen Read being all the way up at the top at Bentley—which is a very interconnected university with the government, trust me—that just makes me think she understands this—whether she was a Jason. Listen—you can understand what the intelligence community does without being in it. I'm not in the intelligence community—I just report on the government. So I kind of see how it all works. You can understand it without being in it. But if you're in it—let me just tell you right now—if anyone Karen Read knew professionally—through family or otherwise—is in the government—and I'm not talking about a special agent like in the FBI or, you know, a case officer—I'm talking about in the apparatus of control. Okay. In the directorate of national intelligence somewhere—there's a hierarchy. All right. If she knows anyone who understands all that—that's why she was able to pull this off. Because it's not—that's why I'm not fawning or being gratuitous. I don't necessarily—I'm not partial to Karen Read. I think she has liability for John's death. What I am is cognizant of what she's capable of—so I can understand what's going on. A mind like that, okay—doesn't just do PR. PR was not going to help Karen Read here. Natalie and her PR and all that stuff—none of that was going to work. What Karen Read needed was counter intel and intel knowledge. [Explanation of compartmentalization via the Manhattan Project] When I say compartmentalization—what you all have to realize is I'm talking about how the Manhattan Project—that's like the archetypal example of compartmentalization—how the Manhattan Project to develop the bomb that won the war for the United States in World War II—how that worked. The way that that worked is you had Los Alamos, okay, in New Mexico with Oppenheimer and whatever the hell—some of the Operation Paperclip people—which I'm not very happy with. We took Otto von Braun—who developed the V2 rocket for the Nazis. We brought him over via Operation Paperclip. We implanted him at Los Alamos with fucking Oppenheimer. I'm pretty sure it was like a communist sympathizer. Anyway—we sent them down to Los Alamos—the actual research scientists working on the core of the bomb. But to develop a nuclear bomb—you need 20,000 people at the time working simultaneously on production. You're not going to do that at Los Alamos. One: why would you ever expose them to the inner workings of the tech? It's nuclear material. You are not going to have 20,000 people around it. That's why it was in the middle of a desert. Third of all—they would know too much. So what did they do? Okay—look up Oak Ridge, Tennessee. Oak Ridge, Tennessee is a town—it's a government town still to this day. It's one of the most—it's not as top secret as it used to be. But back in the day—like during World War II—they put fucking canopies over the whole thing—20,000-person town—canopies over all of it. So it would just look like trees from the air in case the Japanese managed to come and bomb us. They never did—thank God. But anyway—at least on the mainland—obviously they got Pearl Harbor, and we're still upset about that. But the point is Oak Ridge, Tennessee, okay—it had people employed across a number of disciplines, all right—and they would go into—I'm giving you an example—one guy would go into a room, all right, and he would walk up to a giant computer. It was an old computer—we're talking the '40s here—it was a big computer, like a big green box. He would take a punch card. Okay—this is how you used to code—write computer code—he would put—take one punch card with one line of code—put it in the machine—take it out—put it down. He had no idea what he was doing. He didn't know what the punch card had on it. He didn't even understand what the machine did. That's compartmentalization. He's like—you do that with all of the people working on a project that's very top secret. So if you're thinking as Karen Read—Aidan Kearney does like a rudimentary version of it—even Tully does a rudimentary version of it—and Kate Peter—compared to Karen Read—Karen Read, Alan Jackson—whatever—understand the intelligence community. I don't fucking know how, but they do. So they compartmentalize. That's how they have pulled this whole thing off. They compartmentalize—no one ever really saw the full picture. When you—if you are a schematic mind like that—when you do something like reveal that Aidan Kearney has sent you a recording of conversations between you because you want the public to know that Aidan is doing this to you—you are tactically sabotaging him. Why you do that at this moment—when you are an expert in counter intel—thus requires that level of understanding. You cannot just say, "Oh, I don't like Karen Read; she must be a moron." No—if you want to understand why she's acting—you have to think about her tactical intelligence—because then you can reconstruct what the goal of this move is. It can only be designed to kneecap his support. I mean—when I say kneecap—I'm not talking Tonya Harding beating the woman at the ice rink. I'm talking—you can make it so this man's numbers are lower than Kate Peter talking about Cyraxx—like 2,000 views of video, if that, all right. That's what it will come down to. And she wants him to feel that. I think that it's a little bit like—it's 97% tactical. It seems to be that this is the moment where she feels he needs to lose all his support—like right now. Second—it feels a little like a little personal—like it's not just that she's causing him to lose all his support. There are ways to do that without doing this. I believe what Karen's really done here is she's taken the one thing from Aidan that gives him the strength to keep going day to day—which is his public persona and image—his support—her support. And so he can go around saying all he wants—"I owe it to Karen; she made me"—do you think that's how he really feels? Or do you think he feels that he's the only reason she's where she is? Now—if that's how they each feel—you're at a stalemate. Aidan thinks he's the reason Karen got to where she is. Karen thinks that she's the reason Aidan has support and is known in the region. Who's right? Who's right? That's what this conversation is going to be about. And I'm telling you—Karen's right. Karen has more support than Aidan Kearney. Okay—it's just a basic—you can look at the numbers. Karen has more support than Aidan Kearney. Karen has more loyalists. Karen—I don't even understand the complex, okay—but her parasocial complex that she's created is stronger. You might call it a brand—I think that degrades the insidious nature of it. I call it a parasocial complex. That is stronger than Aidan Kearney's. [Transition to the conversation with greetings] So what we're going to listen to right now is—oh, hello, Francesca Towel. Oh—a lot of folks are coming in. Hello, Rose Water. Hello, Maureen. It's great to see you all. Hello, J.I.5. We're going to listen to this conversation. I'm going to explicate it for you. I think you have enough background to get it now—but just be aware—without this background—that would have made no sense whatsoever. I promise you. **Aidan:** Am I on? **Host/Other:** You're on. **Aidan:** So who are you? Who is this? **Chris:** Don't worry about it. It doesn't matter who I am. **Aidan:** Well, it does. You're some fucking kangaroo court motherfucker talking about her. What the fuck do you know about anything? **Chris:** Well, I know exactly what you've been doing. **Aidan:** So—well, what the fuck are the sites you're talking about? No—no—recites—what you talk about? No—receipts. I've got to shit up. Let's see him. Let's fucking see your receipts. **Lily:** Hang on, Aidan—you know me. I'm the host. I'm Lily. **Aidan:** Yes, Lily. Hi, Lily. How are you? I'm sorry. I'm just wondering... **Lily:** I know you may not know Chris, but you know me. And so I just wanted to say hello. **Aidan:** Yeah, no, but... Grant: Oh, I also want to let you know this comes with a warning. They use very vulgar language. Some of them are from Commonwealth realms countries. So the language they're using is not as offensive as it would be if you used it in America. Aidan uses some very offensive language. This is for the purposes of analysis and commentary. I do not condone, endorse, promote, or otherwise suggest anyone engage in the use of this language. I personally don't like it. I use the F word from time to time, okay? And maybe like the S word—but I do not say some of the terms they're going to use—especially because one of them is very offensive, okay, to women. And I'm sorry ahead of time that he uses it—but you should hear Aidan's true colors. **Aidan:** This koala motherfucker is up here making shit up, running his... [Recap of text messages and setup for listening] Grant: So what you have to realize is these texts you're seeing on the screen got released because of this conversation. You're going to hear Joe Flipperhead talking about them. Now in the text messages, you can see Joe reaches out to Karen—Joe Flipperhead. And Karen's going to say she's trying to bounce back, but life is not quite happening. "Had a falling out with Aidan as everyone eventually does. Found out Aidan's been taping our phone conversations and sharing them with people and then telling everyone he doesn't understand how I blew him off for Howie Carr. Some anonymous person sent David and Alan a 33-minute phone call I had with Aidan that was all recorded without my knowledge. That was my final straw. He's done a lot of sneaky stuff with me, but this is above and beyond." And then Joe Flipperhead's like, "Do you want your side out there? If yes, I'm with you. If not, all good—just let me know. Have a good weekend." Karen says, "Sure. I told many people my side. This is the last straw. Would never and have never betrayed him. Meanwhile, he has put me in harm's way in a huge way multiple times." Okay, so we're going to listen. "Okay, okay, all right, all right—no trolling. We should—we should be banning people like that. You have been banned. You have been banned. No trolling. Absolutely no trolling. Now gaslighting and manipulative subversion is the hallmark of a lot of the forces in the orbit of this case. So none of that. We have a lot of Blue Wall of Towel friends here. Don't stand for that. Hello, Christy Mack. Great to see you. Hello. Stay tuned, Wendy. Hello, Bunny. Hello, F.B.I.—my friend, F.B.I. DOJ corruption survivor. And hello, Meredith—which is not Meredith O'Neill. This is Meredith the Towel friend. It's great to see you all. And as I said, if you see anybody trolling in the chat—now is not the day for it. Towel's health is not well. And I think there are a lot of people who want to undermine the agency of the unheard and the vulnerable in this situation. There are a lot of people who want to gaslight right now because where this is going is explosive. And furthermore, we're about to listen to the conversation. So what you're going to hear in this conversation is it's going to be Aidan Kearney and Joe Flipperhead—who's named Nick—and a guy named Chris who Aidan Kearney calls a koala. They're going to be talking about what we just talked about. But remember—these text messages haven't been released. So Aidan doesn't actually know they're coming. He's being told of this and going on an X Space and reacting in real time. Now I'm going to pause from time to time, and I'll try to flesh out some of the less clear parts. But as we read through the transcript and as you see this all, I think it will be clear to you—clear to you—the implications. So let's listen."

Grant Smith Ellis

19,048 次观看 • 9 个月前

THE TRUTH ABOUT OCTOBER 7TH: Reports confirm that Netanyahu, the Mossad and the IDF deliberately allowed the October 7th attack by Hamas to take place. They knew one year in advance of the attack and did nothing to stop it. They deliberately stood down during the attack allowing many more innocent Israelis to be slaughtered in order to get domestic and international support for war in Gaza and Iran. HOW DID OCTOBER 7TH HAPPEN? On October 7th, Hamas was able to carry out its shocking terror attack against Israel, despite Israel’s intelligence, military and security apparatus commonly considered the best in the world. Israeli Prime Minister Benjamin Netanyahu himself tweeted and quickly deleted a statement denying any foreknowledge of the October 7th attack. “Under no circumstances and at no stage was Prime Minister Netanyahu warned of war intentions on the part of Hamas" the tweet said, before it was promptly deleted. Why did Netanyahu’s team delete that tweet? Because in fact he did have intelligence that there would be an attack by Hamas and tried to hide this from the world. Foreign security services, Israeli security services and the Israeli public all knew that Hamas was planning a violent, cross-border incursion where they would attempt to over-run and attack the kibbutz communities in southern Israel and take prisoners back to Gaza. And they also knew when. But it happened anyway. Why? Ten days before the attack, and then again three days before the attack, Egypt intelligence officials passed “repeated warnings” to the highest levels of Israel’s government. In one of these warnings, Egypts premiere intelligence minister General Abbas Kamel personally called Netanyahu and warned that Hamas was about to do “something unusual, a terrible operation.” Unnamed Egyptian officials told YNET News that they were shocked by Netanyahu’s “indifference to the news.” But Israel didn’t have to trust or believe Egypt, because actually, most of the warnings of the October 7th attack came from Israeli civilians and the Israeli military itself. The civilians and soldiers who brought these emergency warnings to the military were ignored and in some cases, strangely enough, threatened with legal action. In 2022, the IDF, through confidential sources, or spies, in Gaza, actually obtained the detailed Hamas Al Aqsa Flood attack plans. Codenamed “Jericho Wall” by Israel, the excursion plan called for a barrage of rockets to begin the attack and for gunmen to pour into Israel en masse via para-gliders, on motorcycles and on foot and take hostages back into Gaza, all of which happened on October 7th. Hamas followed the blueprint that Israel already had with shocking precision. So Israel had the attack blueprints, but were they taken seriously by the IDF? Yes, the plans were diligently studied. A presentation on the planned attack was given to senior officers in the IDF’S Gaza division. The presentation concluded with this sentence: “This invasion constitutes the gravest threat that IDF forces are facing in the defense of Israel” So in response to this, did Israel’s security establishment beef up and enhance their surveillance of Hamas militants on the other side of the border? No, stunningly, they actually did the exact opposite. They decided to entirely stop monitoring Hamas’s handheld radio traffic. Because they saw it “as a waste of effort” even though during that same time in 2022, Israelis living in the kibbutz communities near the Gaza border, most of whom have some type of military training due to Israel’s mandatory IDF service laws, were, according to Israeli media, picking up clear evidence that Hamas was “practicing the breaching of the fence and conquering kibbutzim and seizing hostages and destroying everything in their path.” Then, In April 2023, 6 months before the attack, again according to Israeli media, the IDF “restricted the ability” of Israelis living near the border “to monitor Hamas’ wireless traffic.” In September 2023, less than a month before the attack, the head of the IDF’s “Devil’s Advocate” intelligence unit, which challenges prevailing narratives within Israel’s military, twice alerted senior decision-makers in both the army and political spheres about Hamas’ plans for a large-scale cross-border military operation. He reiterated these warnings in person at Intelligence Branch strategic assessment sessions on September 26th and 27th. Just days before the attack. So it was clear to everyone that Hamas wasn’t only planning to do something horrible, but it was also clear what that horrible and evil thing was. According to a female IDF soldier who spoke to Israel’s channel 12 news program, she was constantly trying to warn her superiors about the gravity of Hamas training exercises. She was threatened with legal action. “We were told that if we continue to harass on this issue, you will stand trial.” So, Egypt knew, the Israeli military knew, and the Israeli civilians knew. Yet, two days before October 7th, the Israeli military took two entire commando brigades, or around 100 soldiers, away from the the soon to be breached locations of the Gaza border and sent them to the other side of the country, to the West Bank village of Huwara despite no Hamas presence being in Huwara and despite there being giant Israeli dance parties taking place right along the same border fence where violent, escalating and obvious Hamas drills of breaching and kidnapping were taking place. According to Israeli media reports, Lt. Col. Sahar Fogel, an operations officer at the IDF’s Gaza Division, opposed the approval of the Nova Party based on the last minute nature of its event application and the intensifying Hamas drills at the border and because if something were to happen, more soldiers were on holiday. It was the Jewish holiday of Sukkot. The Lt. Col. explained his opposition to the party’s approval to his superiors. He was instructed to allow the event. Israeli Newspaper Haaretz reported that other Gaza division officers privately “told of irregular conduct and pressure surrounding the approval of the party.” In February 2024, Elkana Federman, the head of security for the Nova festival gave an interview to Israel’s Channel 14 where he made a statement that hasn’t been reported on by any American media. “I had a guard at the festival who had served in the Re’im Division [near Gaza border], and a week before the festival he sent me a voice message, basically warning me, saying, ‘Elkana, something is going to happen over Sukkot. I just wanted to let you know, there are a lot of warnings, I passed the voice message on to local IDF officials and they told me everything was all right.” The Hamas attacks were violent and brutal. They have been likened to tragic events such as September 11th and the Holocaust, so it comes as a surprise that Benjamin Netanyahu and members of his Likud party have at times described the attacks as somewhat of a political gift. Nissim Vaturi, a member of Netanyahu’s Likud party in the Knesset, referred to the attack as sort of gift from God because they are being used to justify the current ongoing war, stating: “We were meant to fight this war against Hamas, as is happening now, and luckily for us it came from the heavens.” Israeli Prime Minister Benjamin Netanyahu explained that Israel didn’t have domestic or international support to invade or destroy Gaza. He said the October 7th Hamas attack solved both of those problems for him, stating “We couldn’t get the domestic consensus to make a definitive solution to the problem of Hamas. That is, no one would agree across the Israeli public to go in and basically destroy Hamas, go throughout Gaza and destroy Hamas. We didn’t have the international consensus either; nobody would understand why we are doing it. Both conditions were created because of the Hamas attack on Israel on October 7th.” Did the Israeli military, the Israeli intelligence community, and the political leadership of Israel allow this ghastly attack to happen to justify wiping out the population of Gaza? The evidence proves, yes. WHERE WAS THE IDF? During the October 7th attacks what did the Israeli military do? For hours they did nothing, it was a deliberate military stand down order. It's important to remember that Israel is just slightly bigger than the size of the state of New Jersey. But for some reason, once the Hamas attacks began, the time it took the Israeli army and rescue teams to arrive, fight and rescue Israelis at the different kibbutz communities and sites being attacked took anywhere from 4 hours to more than 20 hours. The New York Times has reported: “Thousands of soldiers were less than 40 minutes from the towns that were under attack.” A video that Israeli media obtained from an army helicopter, corroborated by Israeli survivors, prove that there were more than 500 Israeli soldiers directly outside of the Kibbutz entrance, fully armed, with Humvees and tanks but it took 10 hours for those soldiers to show up. Avital, a survivor of the Be’eri attack, described to Haaretz: “500 soldiers stood outside, with equipment and vehicles. I remember yelling at them, ‘We’re being slaughtered, come in, save us and no one said anything.” So why did it take so long for help to arrive? Haaretz reported: “At 7 A.M., the party organizers called Lt. Col. Elad Zandani, the man tasked with approving the festival and told him that terrorists were shooting the partygoers. He suggested that they fend for themselves. The first IDF forces arrived at the party scene at 3 P.M., that’s an 8 hour response time for one of the most efficient, capable and well militarized security forces in the world operating in a country the size of New Jersey with their Gaza division only a few miles away. And what makes this even more strange? Around 4 hours into the Hamas assault, at 10:46AM, Israel was already launching operations and bombing targets inside of Gaza. So, if Israel could begin an offensive attack into Gaza within 4 hours, why did it take more than 6 hours and in most cases more than 10 hours and even 20 hours in some cases to mobilize inside of their own country to stop the ongoing attack and to defend the lives of their own people? The New York Times quoted Ben Zion, an Israeli military reservist who spoke to Israeli media. He said his unit voluntarily left central Israel in a convoy at 1:30PM, they got together and left for the south on their own. He expected to see the roads packed with soldiers and equipment and armored vehicles heading south. “The roads were empty!” he recalled in an interview. Roughly seven hours into the fighting, he turned to the reservist next to him and asked: “Where’s the IDF?” The brutal and deadly Hamas terrorist attack of October 7th is so central to justifying Israel’s ongoing war in Gaza that Israel is actually outlawing questioning the October 7th government narrative. Israelis who spread information counter to the October 7th government narrative, which the Israeli Knesset calls “falsehoods and propaganda” could face up to 5 years in prison. Between the abundance of concrete evidence that suggests Israeli military allowed October 7th to happen by ignoring dozens of reliable and specific warnings, threatening soldiers with legal actions who tried to warn their military superiors and taking troops away from the area of the Gaza border that was attacked and now evidence that suggests there was some type of military stand down order in place on October 7th, it is important to ask, what was October 7th and what kind of war is the United States supporting? WHAT IS THE HANNIBAL DIRECTIVE? Images and videos of burnt cars, blacked and charred bodies and incinerated homes in southern Israel were plastered on every phone screen and television after the October 7th Hamas attack. The images and videos were used by the Israeli government to justify the military’s heavy handed tactics in their ongoing war against Hamas, But were all the images and videos actually the result of the Hamas attack? Innocent Israeli civilians were brutally killed by Hamas on October 7th, but there is evidence that proves the IDF killed their own Israeli citizens in what is known as the Hannibal Directive. To understand what the Israeli military did to their own civilians on October 7th, you have to understand the political aspirations of Hamas and what the goal of taking hostages is, it is political leverage. There are over 10,000 Palestinians in Israeli jails. 3,000 of whom haven’t been to trial or charged with a crime. When militant groups manage to capture Israeli civilians or soldiers it gives them leverage to force a prisoner swap and get some of their people out of Israeli prison. For example, in 1986, Hamas managed to kidnap 3 Israeli soldiers and bring them to Gaza. They demanded 1,150 Palestinian prisoners in return for these soldiers. After this, the military drafted a secret field order to prevent future kidnappings. It was called the "Hannibal Directive." The directive gets its name from the Carthaginian general who chose to poison himself rather than allow himself to be captured alive by the romans. In 2003, strangely enough on October 7th 2003, three Israeli soldiers were taken hostage and brought into Lebanon. Following the activation of the Hannibal Directive, IDF attack helicopters fired indiscriminately on 26 vehicles thus ensuring the death of their own soldiers and therefore robbing Lebanese militants of the ability to demand Israel make concessions. The Last known application of the Hannibal Directive was in 2014. In Rafah. Hamas fighters managed to capture an Israeli soldier, Lt. Hadar Goldin. Instead of allowing the lieutenant to be used as leverage by Hamas, the military killed him. Dropping bombs, missiles and shells on the area he was being held, killing the soldier and also over 100 Palestinian civilians. The scale of the Hannibal Directive on October 7th was entirely different from those of the past. A retired Israeli air force general, Nof Erez, described it during a podcast with Haaretz, an Israeli newspaper saying “The Hannibal Directive was apparently applied at a certain stage, because at the moment they understand there is a kidnapping, they immediately say, ‘Guys, this is Hannibal.’ But the Hannibal we trained for all of the last twenty years, is for a vehicle we know at what point of the fence it enters, on what side it drives, and maybe even on which road it drives. This was a Mass Hannibal.” We know the Hannibal Directive means to kill your own, so what does “mass Hannibal” mean? A large mainstream Israeli media outlet reported: “In the week after Black Shabbat, October 7th, soldiers of elite units, at the initiative of the Southern Command, checked about 70 vehicles that remained in the area between the Otaf settlements and the Gaza Strip. These are vehicles that did not reach Gaza, because on the way they were shot by a combat helicopter, an anti-tank missile or a tank, and at least in some cases everyone in the vehicle was killed.” 70 vehicles and in some cases, everyone in the vehicle was killed. These are Israelis killed by Israel. Again, only reported on in the Israeli media. Tuval Escapa, is a member of the security team for Kibbutz Be’eri. He set up a hotline so kibbutz residents could communicate with the Israeli army. He told Haaretz that “the commanders in the field made difficult decisions, including shelling houses on their occupants” in order to eliminate would-be hostages as well the terrorists. They shelled entire houses. Do we hear this in the American mainstream media? That the Israeli military targeted and destroyed over 70 cars with hellfire missiles that were filled with Israelis and that they decimated entire Israeli homes with tank shells? A report in Haaretz on October 20th notes that the Israeli military also carried out an airstrike on their own military base, the Erez crossing. That base was filled with Israeli Civil Administration officers and soldiers at the time. An Israeli woman named Yasmin Porat gave an interview with Israel Radio that the military “undoubtedly” killed numerous Israeli hostages during gun battles with Hamas militants. IDF General Barak Hiram, prevented hundreds of troops from entering Kibbutz Be’eri for hours on October 7th, when he finally allowed the IDF to go in, he ordered tanks to fire on multiple homes. The tank shells killed at least 12 Israeli hostages and 3 children. Recently the UN published an investigation confirming several of these facts, namely, that the IDF had in fact activated the Hannibal Directive on October 7th stating “The Commission is aware of allegations that Israeli Special Forces used the “Hannibal Directive” to prevent the capture of Israeli civilians and their transfer to Gaza, even at the cost of killing them" The Commission documented one statement by an ISF tank crew, confirming that the crew had applied the Hannibal Directive. The Israeli military, Israeli civilians and the United Nations all admit to the IDF purposely killing their own on October 7th. How many? It’s hard to know the exact number, but the imagery of charred bodies and incinerated cars and homes are still being used to this day to manufacture consent and support for Israel’s ongoing assault of the Gaza Strip, where more than 47,000 Palestinians have been killed including 15,000 innocent children. ISRAEL'S FINANCIAL SUPPORT FOR HAMAS: Israel and Netanyahu helped funnel over $1 Billion dollars to Hamas in order to keep Palestine from being recognized as a State. It was Netanyahu and Israel who helped create Hamas thinking that they could control them and would be able to use Hamas as an excuse for their continued military operations and occupation in Gaza. ISRAEL'S SECRET NUCLEAR WEAPONS: The front lines of the war between Israel and Hamas are expanding and moving beyond Gaza. Yemen’s Houthis intensified their involvement, going from simply attacking Israeli bound cargo ships to now navigating an armed drone over 1,200 miles, evading Israel’s Iron Dome defense system and managed to strike inside Tel Aviv causing a massive explosions. In addition to their ongoing war in Gaza, Israel has attacked or been attacked by Iraq, Lebanon, Syria and Iran. Meanwhile, the U.S. continues to promise Israel unconditional and limitless support. But has anyone even asked if this support is LEGAL? According to the 1976 Symington and Glenn Amendments of the Armed Foreign Assistance Act, which is now a part of the Arms Export Control Act, the United States cannot give foreign aid, whether that’s economic or military, to any nuclear armed state that is not a signatory to the Non-Proliferation Treaty, or the NPT, but the United States gives billions of dollars every year to Israel and according to all international arms organizations, Israel has anywhere from 90 to 400 nuclear warheads and Israel has not signed the NPT. So how does this legally happen? The United States and Israel simply pretend Israel does not have nuclear weapons, literally, that’s what’s done. It is called “Nuclear Ambiguity.” This nuclear ambiguity, which allows Israel to continue to receive billions from the U.S. and also operate and maintain their nuclear arsenal with absolutely no international oversight and zero regulation, is maintained and preserved through the threat of force. Due to a previously Top Secret gag order, all U.S. government agency employees and contractors are forbidden from discussing Israel’s nuclear weapons program. Even insinuating or mentioning information that’s already in the public domain is forbidden for all federal employees and contractors. It sounds hard to believe but let’s give an example: James Doyle used to work at Los Alamos National Laboratory as a nuclear security specialist. He violated this gag order. Doyle wrote an academic article arguing that Nuclear weapons do not do a good job at deterring countries from attacking one another, he wrote: “Nuclear weapons did not deter Egypt and Syria from attacking Israel in 1973, Argentina from attacking British territory in 1982 or Iraq from attacking Israel during the 1991 Gulf War.” A clear reference to Israel’s nuclear weapons. Doyle’s security clearance was promptly withdrawn, his home was raided, his computers were seized and he was fired from the Department of Energy. So apparently that’s how it works. In 2018, The New Yorker published a stunning report in which they discuss another way Israel’s nuclear ambiguity is enforced: secret presidential letters. According to former U.S. officials and former Israeli officials, every recent US administration since Clinton in 1993 has performed the same ritual as it came into office. They all agreed to undermine U.S. law by signing secret letters, brought to them by hand by their Israeli counterparts stipulating that they’ll never acknowledge what everyone knows: that Israel indeed has nuclear weapons. The National Archives is currently refusing to release the letters, arguing that even confirming their existence would violate the secrecy pact. So there’s a gag order that stops all federal employees and contractors from simply acknowledging Israel’s nuclear weapons and U.S. presidents sign secret letters promising not to acknowledge or pressure Israel to do anything relating to their proliferation status. That means asking questions like these are entirely off limits enforced by the threat of government violence or law fare. But all of this information leads to a series of questions: Where does Israel dispose of the toxic waste its program generates? Are Israel’s nuclear weapons ever used to coerce the U.S. into making adverse policy decisions? How about our allies? Besides apartheid South Africa, has Israel offered any of its nuclear weapons for sale to other foreign countries? To U.S. adversaries? Has Israel mounted nuclear weapons onto its German supplied Dolphin class submarines? Or their American supplied F-35 jets? No questions are allowed and what is the cost, the dollar amount, for Americans, of this “nuclear ambiguity” policy? To be exact, almost $240 billion dollars of military and economic aid has gone from the U.S. taxpayer since the passing of the Symington and Glenn Amendments. That’s far more than the United States spent rebuilding Europe under the Marshall Plan. And none of that quarter of a trillion dollars should have been allowed under U.S. law. That’s the price of keeping Israel’s secret. A quarter trillion and yet where is the International Atomic Energy Agency and international nuclear inspectors? The same ones who monitor every other nuclear armed country in the world? DOES ISRAEL PERSECUTE CHRISTIANS? Before the war, Israel’s Christian minority were already being targeted with dispossession and violence. In Jerusalem’s Old City, narrow streets line the ancient neighborhood and Jewish Israeli civilians spitting on and attacking Christian clergy members is commonplace in Israel. Evidence of this shows a video from a few days before October 7th of Christians in the Old City of Jerusalem carrying a cross while a group of Orthodox Jewish Israelis many of them children walk by and spit at the Christians. It’s become mainstream to believe Christians don’t belong in Israel and only Jewish people do. A few years ago, the mission, the Virgin Mary’s place of death, was attacked and vandalized by Israelis. The graffiti on the ancient walls read “Death to heretical Christians, the enemies of Israel,” and “May his name and memory be obliterated,” in reference to Jesus. According to Haaretz, at a Jewish school, the leader of an anti-assimilation group Bentzi Gopstien told students that it’s quote “mitzvah” or a “good deed” to burn and destroy Christian churches. Should Americans, especially Christian Americans be allowing billions of their tax dollars to be used to ethnically cleanse, attack and bomb Holy sites and Christian civilians? What has happened since Israel has launched its war against Hamas? Israel has displaced 2.4 million Palestinians in Gaza, 80% of the buildings and homes have been reduced to rubble, at least 45,000 Palestinians have been killed with 50% being women and children. In America, we’re told we should prioritize sending billions of U.S. taxpayer dollars to Israel over dealing with our own issues here at home because Israel needs to be able defend itself. Well, it seems like what initially appeared as a defensive war, is appearing more like an offensive war with the expansionist goal of the permanent military occupation of the Gaza Strip. Did the Israeli military, the Israeli intelligence community, and the political leadership of Israel allow this terrible attack to happen to justify wiping out the population of Gaza, a genocide justified by an attack that Israel could have stopped had they wanted to.

Truth Justice ™

603,047 次观看 • 1 年前

Ron Unz (The Unz Review) discusses his intellectual upbringing and involvement in Holocaust research with Holocaust researcher Germar Rudolf (Germar Rudolf (* 1964)) and free market activist Jorge Besada. 00:28 Jorge introduces German chemist and leading Holocaust researcher Germar Rudolf who spent nearly 4 years in jail for writing a chemistry report that questions the mainstream mass-gassings narrative and thus allegedly “inciting racial hatred”. 02:54 Jorge introduces Jewish-born entrepreneur and author Ron Unz who has degrees in Physics and Ancient History from Harvard. Runs 05:00 Jorge briefly explains how from freedom emerges economic and intellectual competition which inadvertently turns mankind into a super-computer as companies innovate and copy each other’s innovations, as well as superior morals as hard-working people motivate everyone else to be likewise. 05:50 Ron tells us about his life, Jewish cultural influence-identity or lack thereof, early views on Holocaust. 09:15 Ron begins to get suspicious regarding Holocaust due to disastrous-flawed media coverage of Iraq war after 9/11. Mainstream media lost credibility. 10:42 Ron digitizes old publications and discusses ramifications of doing so. 14:20 Ron archives Reason magazine and eventually stumbles upon Holocaust-related issue and controversy surrounding it. 18:04 Ron praises issue and brings up fact that 2 leading editors were Jewish. 21:22 Arthur Butz, another prominent Holocaust mass-gassings doubter has Masters in Electrical Engineering from MIT. 21:50 Ron emphasizes how Libertarians were early prominent leaders in spreading Holocaust-doubt-revisionism. 23:28 Ron speculates that the Reason issue relating to the Holocaust was due to the coming release of Arthur Butz’s ‘The Hoax of the Twentieth Century’ 26:24 Ron praises Butz’s book and especially so Nicholas Kollerstrom’s ‘Breaking the Spell. The Holocaust: Myth & Reality’ 30:27 Jorge mentions how since Libertarians are better defenders of freedom, they get the benefits of superior competition of ideas and busting of myths-lies which helps explain why so many are Holocaust revisionists-deniers. Asks Ron a out how important was for him to lear that freedom giant Murray Rothbard, who is likely Milei’s favorite economist, was a revisiojnist-Denier. Ron elaborates. 34:55 Ron describes how it was books that were pro-mainstream-Holocast that persuaded him the most about the myth-story of the Holocaust. Discusses Deborah Lipstadt. 40:42 Ron brings up how lead soviet prosecutor in Nuremberg Trials , Andrey Vyshinsky, was same fraudulent prosecutor who oversaw Stalin’s bogus ‘Great Purge-‘Shows Trials’. 41:30 Ron brings up how aspects of Holocaust mythology are abandoned with time like alleged mass-gassings or death camps on German soil. 45:05 Ron mentions how Robert Faurisson(french revisionist) stressed how neither Churchill’s, nor, Eisenhower’s, nor Charles de Gaul’s massive post-war writings mentioned anything about the Holocaust. 48:56 Ron brings up book ‘The Jewish Threat: Anti-semitic Politics Of The U.s. Army’ by Joseph W. Bendersky, and how not a single American intelligence officer or top generals believed in holocaust stories. 50:15 Ron discusses John Beaty’s book ‘The Iron Curtain Over America’ 1:14:40 Ron argues that the reason why neither Churchill, nor Eisenhower, nor Charles de Gaul mentioned anything about the Holocaust is because they didn’t believe it and didn’t want to be seen as having fallen for war-time propaganda-myths in posterity. 1:17:29 Germar mentions how John Beaty may not have been able to better back his claims about intelligence officers not believing holocaust because it was not until year 2000 that UK finally released secret information about decrypts, so Beaty would have been breaking law. 1:19:18 Jorge brings up how Churchill knew the Soviets had committed the Katyn Forest massacre and introduced fake evidence at Nuremberg Trial blaming Germans for it, thus knew mass-gassings also likely fabrications thus not risk including them in his books to look like a fool in the future. 1:22:08 Ron discusses the Venona project, US spying on soviet spies working high up in Roosevelt admin. Even top American who kept project running and held erroneous anti-Jewish ideas, never believed anything about holocaust. 1:28:09 Jorge, backing Beaty’s claim that Jews were overwhelmingly responsible for bringing about WWII to destroy Hitler, brings up leading Zionist Chaim Weizmann stating that WWII “is our war..We are…giving this war our financial support on which the entire war production is based, we are…providing our full propaganda power which is the moral energy that keeps this war going.” The solution to Hitler’s anti-Jewish fallacies was NOT a world war that killed 80+ million people. 1:29:39 Ron brings up how an increasing number of books today make similar point, but not as portraying Jews as dragging us into an unnecessary war, but as heroes helping annihilate the evil Hitler. 1:31:07 Ron disagrees with Jorge’s earlier statement and downplays Jew’s importance compared to Roosevelt's desire to have a war to allegedly get the US out of depression. 1:34:50 Ron brings up importance of Kristallnacht for getting Roosevelt and Jews to push war vs. Germany. 1:38:29 Germar further elaborates on how Nazi government’s cruel handling of Kristallnacht (forbade insurance companies to pay Jews, large collective fine on Jews as well) did make it easy for many to further vilify Nazi government and help move to war. 1:43:58 Jorge: ‘What are 3-5 major arguments the layperson came make to criticize mainstream holo myths?’ Ron mentions digging where hundreds of thousands of bodies are supposed to be buried. 1:49:12 Germar explains how ‘deep penetrating radar’ and other things have been tried and still no evidence to support mainstream claims. 1:52:43 Jorge summarizes simple arguments against mainstream myth discussed: 1) ground checks fail to show mass graves,2) Nuremberg Trial obvious fake evidence introduced by Soviets like brain bashing pedal-driven machine, atomic bomb-like device to blow up 20,000 Jews, etc. 3) Top Soviet prosecutor Andrey Vyshinsky being same liar as in Moscow ‘Show Trials’ 4) All secret communications from Auschwitz reveal nothing about gassings, 5) Nothing in Churchill, Eisenhower, Charles de Gaul writings, 6) Main Russian archivists admit there is nothing in archives supporting Holocaust, 7) Chemical analysis per Germar 8) massive continuous downward revisions of alleged exterminations. 1:58:52 Germar elaborates on history of massive downward revisions on total deaths. 2:05:28 Ron mentions how after creation of Israel and Israel’s pivot to America, Stalin-Soviets no longer pushed Holocaust. 2:10:55 Jorge summarizes how the mainstream Holocaust myth (NOT conspiracy) evolved. Holocaust exaggerations began as way for Poles-Soviets-Communists to punish Germany but understandably attracted and was amplified by Jews, especially Zionist ideology-believing ones. Per Germar, the key leading historian and judges who did most to create mainstream holocaust myth were not even Jewish. 2:13:00 Ron agrees with summary and believes that most of today’s Holocaust academics are not lying as part of some grand conspiracy by believe their mythical narrative. 2:14:26 Jorge brings up astute ending to Ron’s Holocaust article where he compared Holocaustianity to Socialist mythology and the USSR, both myths similarly superficially examined, sustained by coercion, and that could quickly collapse. 2:16:40 Jorge asks Ron: “Where do you see things headed?” 2:17:40 Jorge asks… Mahmoud Abbas, Bashar al Assad, Alexander Dugin, Judge Napolitano frequent guest Phil Giraldi all are prominent doubters, Sergey Lavrov loves watching Napolitano… How much of the Russia-Ukraine war is due to Zionism and are there significant chances that many high up in Russian government are Holocaust doubters-revisionists? 2:22:41 Jorge blames the seeming irrationality of US government looking for conflict with Russia and China as inevitable outgrowth of Holcaustianized Zionism which has made Bibi our Pope getting more than one standing ovation per minute in US congress. Ron mentions how of course everyone is a next Hitler to be militarily destroyed. 2:24:52 Ron sees massive collapse of the West which will bring down Holocaust myths with it. 2:25:55 Germar asks Ron about personal repercussions regarding his open Holocaust skepticism, lost friendships, etc. 2:34:15 Jorge brings up why Ron is such a vital intellectual. Unlike David Duke or Candace Owens who bring up good information about Jewish-related chaos, Ron is a secular Jew who does NOT make many fallacies Candace and David make like in Candace’s case referring to Bibi being influenced by Satan etc. And hopefully major podcasters like Joe Rogan soon host Ron. 2:36:06 Ron : “Maybe if one of these people had me on it could be the straw that breaks the camels back” 2:36:17 Jorge brings up how we are clearly seeing how similar to CovidMania, AntisemiteMania is about to emerge and fortunately this is leading more and more people to have the urgency and courage to deal with Zionist and Holocaust myths before it is too late. 2:39:30 Germar brings up Ron asking Germar to post his books. Ron explains he wanted to convert them to HTML but realized few were reading them that way to just abandoned the idea, especially since Germar’s site already provides all PDFs and more. 2:42:02 Jorge! “We almost went 3 hours! We will do this again!”

Jorge Besada

16,100 次观看 • 9 个月前