Loading video...

Video Failed to Load

Go Home

It's summer, and you know what that means? Project Justice is back for it's 5th appearance at Evo BYOC! ๐Ÿ—“๏ธ Friday 8/1, 4PM PT ๐ŸŽฎ PS4 ๐Ÿชช Signup: ๐ŸŽ Bonus prize pool: ๐ŸŽž๏ธ Trailer: S-men | ๐˜พ๐™๐™–๐™ž๐™ง๐™‚๐™๐™–๐™—๐™ก๐™š๐™จ ๐Ÿ”๐Ÿ”๐Ÿ”๐Ÿ”๐Ÿ”๐Ÿ”๐Ÿ”๐Ÿ” #projectjustice #evo #evo2025 #byoc

23,325 views โ€ข 1 year ago โ€ขvia X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

๐Ÿง‘โ€๐Ÿš€ Day 27 of the Cursor #vibejam Proudly sponsored by Cursor + bolt.new + GLIF + Tripo Prizes to win (submit your vibe coded game before May 1!) ๐Ÿ† $25,000 ๐Ÿฅˆ $10,000 ๐Ÿฅ‰ $5,000 ๐Ÿšจ๐Ÿšจ๐Ÿšจ๐Ÿšจ๐Ÿšจ๐Ÿšจ๐Ÿšจ๐Ÿšจ๐Ÿšจ๐Ÿšจ๐Ÿšจ๐Ÿšจ YOU HAVE JUST ONE DAY LEFT! ๐Ÿคฏ๐Ÿคฏ๐Ÿคฏ๐Ÿคฏ๐Ÿคฏ๐Ÿคฏ๐Ÿคฏ๐Ÿคฏ๐Ÿคฏ๐Ÿคฏ๐Ÿคฏ๐Ÿคฏ My favorite games from today: ๐Ÿฆซ Capybara Driver by leo, I posted it before but now it's finally done, it is so cool and cute and the 3d pixeley shakey style is so unique and original ๐Ÿ•ต๏ธโ€โ™€๏ธ Meta Infiltrator by jstaley, infilitrate at Meta HQ as Elon to steal AI secrets, inteeerestinggg ๐Ÿš— Ride Tales by Aurelien, drive anywhere in the world (not with Google 3d tiles but I think procedurally generated scenery!) ๐Ÿ” Bungr Inc. by JacobFinite, lets you run a burger restaurant ๐Ÿ“Š Mini stats: 540 games submitted 162,827 players 11,944,541 views Reply in this thread with updates on your current games to share your progress, and add tag #vibejam so I see and can include you in the daily tweet Wanna to participate? You can still start now and submit your game any time before May 1! (we started April 1 btw) There's now $40,000 in prizes for you to win, see threads below for more info. The Gold prize is $25,000, silver is $10,000 and bronze is $5,000!

@levelsio

64,293 views โ€ข 5 months ago

๐Ÿ”๐Ÿ‡ฟ๐Ÿ‡ฆ McMayhem at the McDonaldโ€™s! Only in Mzansi ๐Ÿ˜‚ Listenโ€ฆ ONLY in South Africa can you go for a R30 Big Mac special and end up getting a front-row seat to a live rugby match AND WWE in the same parking lot. Sooooo... 3 white okes vs 3 black okes, surrounded by a crowd of hyped-up spectators who had ZERO intention of helping โ€” just vibing like itโ€™s a township boxing tournament. Next thing, one massive white guy channels his inner Springbok and RUGBY TACKLES an aggressive black guy so hard, even the ancestors felt it. The crowd immediately shouted โ€œJEEEEEESUS!โ€ like they just witnessed a miracle at McChurch. SAPS arrivedโ€ฆ But shame, the members looked like they were reconsidering their career choices. You could SEE it in their eyes: โ€œI didnโ€™t sign up for this, I signed up to write traffic fines.โ€ They tried separating the okes with that gentle SA police technique: ๐Ÿ‘‰ โ€œStop it, guysโ€ฆ guysโ€ฆ yohโ€ฆ okay pleaseโ€ฆ okay STOP.โ€ While slowly backing away for safety. The black guys were getting heated, the white guys werenโ€™t backing down, and boom โ€” McMayhem continued. Meanwhile, people in the drive-thru kept ordering like: > โ€œHi, can I please get one Big Mac meal for R30โ€ฆ And also whatโ€™s happening outside? Are they filming Uzalo: Fast & Furious Edition?โ€ Inside, the McDonaldโ€™s staff didnโ€™t even flinch. Serving fries like: โžก๏ธ โ€œChaos outside? Yoh. Anyway, next order!โ€ Only in SA can six grown men fight outside a McDonaldโ€™sโ€ฆ And the REAL headline is still: ๐Ÿ‘‰ BIG MAC MEAL โ€” R30! Even the fight couldnโ€™t beat that special Satire commentary, we don't really know what happen

Vehicle Trackers

206,277 views โ€ข 10 months ago

hypergamy is going to hit women like a 50-megaton thermonuclear bomb, and the reason is because these women are hypergamous themselves female hypergamy hit society first due to the natural supply/demand gap between the sexes, and it's certainly caused somewhat of a death spiral of intersexual relations, but the outcome will not be this hypercompetition between men for women, but rather men checking out of the game entirely as the juice stops being worth the squeeze porn is only getting more immersive and sex bots are on the way, and social media exposes men to 10/10 women nonstop; why then would men break their backs for a crumb of attention for mediocre women? even men with genuine value to bring struggle in the current dating market, the fatigue is beginning to set in for women there are two options: a) make the squeeze easier, or b) make the juice more worthwhile a) would require that they lower their standards and expectations, make themselves more accessible, accept a man with less to offer when they know someone better is out there they don't have that in them, so they resort to b) b) means making the juice tastier, it mean tightening up the juice's nasolabial folds and waist-to-hip ratio. it means injecting the juice with hyaluronic acid fillers and, when that isn't enough to get ahead, it means making real changes to the juice's recipe like getting structural surgery there is a very small supply of beautiful people on this planet, but in the age of the internet that small supply is accessible to everyone at all times instead of being a random beautiful stranger you may rarely come across on the street. everyoneโ€™s perceptions of what is accessible to them is being distorted, and even if only 1% of people are truly beautiful themselves that is enough for 99% of the subpar masses to feel like they can share. past a certain point of abundance a person cannot comprehend the difference between 10 million people and 1 billion, itโ€™s just a lot. if 1 billion compete for 10 million it still feels like an infinite prize pool. this has corrupted women tremendously, but it is absolutely going to and already beginning to do the same with men as men get more and more immersed in and addicted to cheap hits of sexual dopamine such as porn, social media, online dating (which is a corrupting force for both genders) they will be less and less willing to settle for a girl who is any less than perfect because quite frankly, she probably just wonโ€™t be worth it to them anyway there is already a long cultural precedent for women going to extreme measures to looksmaxx for male attention, if men start to become fed up with them and hypergamy increases on both ends the blackpill will explode with women. already women know when they are left on delivered by chad that if they were prettier this wouldnโ€™t be happening, they are beginning to make this observation en masse and it is driving the rise in radfem and โ€œfemcelโ€ (i.e. girl who canโ€™t bag chad) ideology. women are realizing that body positivity and self-love was a scam, and that looks are law iโ€™m betting all in on the upcoming female blackpill trend, putting my stock in it. iโ€™d keep an eye out for it because it has already begun and itโ€™s only going to get bigger
0:22

Sensitive content

hypergamy is going to hit women like a 50-megaton thermonuclear bomb, and the reason is because these women are hypergamous themselves female hypergamy hit society first due to the natural supply/demand gap between the sexes, and it's certainly caused somewhat of a death spiral of intersexual relations, but the outcome will not be this hypercompetition between men for women, but rather men checking out of the game entirely as the juice stops being worth the squeeze porn is only getting more immersive and sex bots are on the way, and social media exposes men to 10/10 women nonstop; why then would men break their backs for a crumb of attention for mediocre women? even men with genuine value to bring struggle in the current dating market, the fatigue is beginning to set in for women there are two options: a) make the squeeze easier, or b) make the juice more worthwhile a) would require that they lower their standards and expectations, make themselves more accessible, accept a man with less to offer when they know someone better is out there they don't have that in them, so they resort to b) b) means making the juice tastier, it mean tightening up the juice's nasolabial folds and waist-to-hip ratio. it means injecting the juice with hyaluronic acid fillers and, when that isn't enough to get ahead, it means making real changes to the juice's recipe like getting structural surgery there is a very small supply of beautiful people on this planet, but in the age of the internet that small supply is accessible to everyone at all times instead of being a random beautiful stranger you may rarely come across on the street. everyoneโ€™s perceptions of what is accessible to them is being distorted, and even if only 1% of people are truly beautiful themselves that is enough for 99% of the subpar masses to feel like they can share. past a certain point of abundance a person cannot comprehend the difference between 10 million people and 1 billion, itโ€™s just a lot. if 1 billion compete for 10 million it still feels like an infinite prize pool. this has corrupted women tremendously, but it is absolutely going to and already beginning to do the same with men as men get more and more immersed in and addicted to cheap hits of sexual dopamine such as porn, social media, online dating (which is a corrupting force for both genders) they will be less and less willing to settle for a girl who is any less than perfect because quite frankly, she probably just wonโ€™t be worth it to them anyway there is already a long cultural precedent for women going to extreme measures to looksmaxx for male attention, if men start to become fed up with them and hypergamy increases on both ends the blackpill will explode with women. already women know when they are left on delivered by chad that if they were prettier this wouldnโ€™t be happening, they are beginning to make this observation en masse and it is driving the rise in radfem and โ€œfemcelโ€ (i.e. girl who canโ€™t bag chad) ideology. women are realizing that body positivity and self-love was a scam, and that looks are law iโ€™m betting all in on the upcoming female blackpill trend, putting my stock in it. iโ€™d keep an eye out for it because it has already begun and itโ€™s only going to get bigger

๐–’๐–”๐–Œ๐–Œ๐–Ž๐–“๐–Œ

43,916 views โ€ข 2 months ago

"There was a willingness to communicate. [The non-human entity] wanted to establish communication with us." ~JV ๐Ÿ’ฅ Has AI Figured Out the Identify of Gilbert? ๐Ÿ‘€ ๐Ÿ‘ฝ Did an Alien Volunteer to be Studied and Communicate with Humans in a Secret USG Facility? Is it Still There? ๐Ÿ‘ฝ "My understanding is that there were teams there that had been working with that being and perhaps other beings for a while." ~JV This is Pt. 1 - Pt. 2 has the AI sleuthing on the possible identity of Gilbert. Excellent job by Ross Coulthart. And if you wanna see my post on Gilbert, the alleged Alien Entity, Vallรฉe...and ALL Gilbert-related entries in FS V7 โฌ‡๏ธโฌ‡๏ธโฌ‡๏ธ I'm taking with this with a major grain of salt until we hear from Gilbert. Then, I'll revaluate.) ~ Ross Coulthart: "You write in your Forbidden Science (7) diaries, in October 2021 for the first time, you mention someone called Gilbert. It's a pseudonym, but essentially, it's a long-lost friend, a discreet master remote viewer at the level of Uri Geller and Ingo Swann." Jacques Vallรฉe: "Yes." (If your response to hearing Geller's name mentioned is, "Oh, he's been proven to be a fraud. See Johnny Carson,' then you haven't done your homework on Uri. Drs. Kit Green and Hal Puthoff on Geller. ~ Kit Green: "Anybody who has studied Geller and seen what he does and the films of what he does recognizes that there are profound differences between what Geller does and magician's tricks. Thereโ€™s not even a remotely qualified individual whoโ€™s ever investigated Geller who believes this orthodoxy โ€“ that itโ€™s all trickery. The RV [remote-viewing] experiments for me were astonishing. He was a superb remote viewer, he was a superstar." ~ Coulthart: "And Gilbert tells you that, through official channels, presumably, government channels, he was taken to participate in a controlled, personal exchange with a, supposed, alien. And you acknowledge in your diary that these revelations are explosive. "And by September 2023, you've received five closely-typed pages detailing how Gilbert says he was taken to a U.S. laboratory, sheltered inside rock, where military guides exposed him to what they explicitly told him was a living alien entity. Now, do you believe Gilbert's account, Jacques? I know at one stage you query: was this a fully veridical (truthful) account? Do you think Gilbert was telling you the truth?" Jacques Vallรฉe: "I have....I believe it for two reasons. You know, believe is a bad word. It's a religious word, it's a commitment, and so on. And everybody is free to believe whatever we want to believe. In science, you know, belief is a contingency. You face a phenomenon. You build a theory of a phenomenon, but the theory, there is no such thing as a theory without a way of testing it. "Now I have no way of testing what Gilbert has told me. I'm not going to reveal the rest of his data because that's his data, and I know there are plans to publish it in the proper way, so that everybody has access to it. I have the data, but it's not up to me to publish it. "There have been other cases, and I've had one personal occasion of coming face-to-face with an entity that is very similar to the entity that he describes. To my shame, I was so scared because this was unprepared. I was not intending to do that." Coulthart: "Are you saying that you had your own personal encounter with an entity? Vallรฉe: "Yes." Coulthart: "When did that happen?" Vallรฉe: "I had no communication with that entity because I was simply too scared, and I mention it in the book." ~Begin excerpt from FS V6~ Hummingbird. Saturday 27 October 2018. ...something brief and terrifying happened last night, far more tangible than a nightmare. As I review it, I have to accept an experience outside my body. All I know is that in the middle of the night I found myself propelled away into the kitchen, a tall being between me and the window. I couldnโ€™t see a face, but it was tall like me, human-like, solid. A few seconds later I woke up suddenly, back into my lying body, panting and whimpering, terrified. It had been absolutely, shockingly real. No transition, none of that slow lifting of the soul people describe. I had been translated from the bedroom, standing up, totally aware, next to the entity that hovered near me without touching, yet encompassing me in a formidable presence. This is as close to a full out-of-body experience as I have ever had. It left me whimpering and scared. (Not a fan of JV mentioning this dream-like/out-of-body experience in the same breath as Gilbert's, alleged face-to-face, physical encounter with a living entity.) ~End Excerpt from FS V6 - Back to JV with Coulthart~ Vallรฉe: "Now in [Gilbert's] case this was very structured. He was asked to be there. And, by the way, it's not classified. I asked him if it was classified, he said, 'No.' And this was 20 years ago, this is not recent." Coulthart: "So, let's go through some of the detail of what you do reveal in [FS 7]. In December 2024, you write that you've seen Gilbert's structured results, and he says he was, apparently, instructed to put specific questions directly to the entity. And it gets fascinating. "Some of the questions generated impressions and responses he couldn't decipher. And what you conclude is that there may be two different levels of NHI, non-human intelligence. Your interpretation, or your friend's interpretation of what he got from the being, is that the higher-level controllers are genuinely alien, whereas the small beings - perhaps the Grays associated with UFO encounters - may be primitive biological hybrids, specifically engineered for terrestrial operation. Is that your conclusion, Jacques?" Vallรฉe: "Well, again, I'm an information scientist. I try to look for patterns of things, so I don't look at one case, you know, separate from others. I look for patterns of cases. In Trinity, in Socorro, in Valensole, and now in the case in Brazil that was revealed recently. "We have a dozen entities. These entities were small; they were the size of, you know, a 10-year-old or 12-year-old kid. They had two eyes and a mouth. They were breathing air. They did not look like our astronauts with, you know, all kinds of suits and [a] support system. They were breathing air. You could understand the, you know, any sense from their eyes. Overall, their structure was human." "Over the years, there have been efforts to theorize in biology about what it would take to create a different kind of human adapted to certain things. We are going to face that problem in space. NASA has looked at that. But before NASA, you know, certainly in World War II, that question was raised already. "And there are...and I mentioned a case from an American biologist who came back from Russia with at least a rumor that the Russians were developing short humanoids for future space missions, because that would save, you know... The most expensive part in the space missions we have now, like the Moon, is the human pilot, okay? If we could do away with the human pilot, or if we could minimize that pilot, then the technology would be safer and would probably function better. "So that question had been discussed in biology. Now, the threshold was, you know, a moral threshold. Are we permitted to create? I mean, we are clearly at the position where, as you know, that the question arose in China recently. You know, was there an experiment to manipulate an egg and create them? So, those are very current questions in biology. "Could some of the beings be just operators? Because in Brazil, especially, they did not seem to be in control at all. And the same thing in Trinity. Trinity is a very important case." (Speculatively speaking: If Gilbert actually came face-to-face with a non-human entity, how would we know if it was one of the actual alien "controllers (as JV suggests)" and not a different type of lower-level, artificial-intelligence-fused being designed to trick us into thinking we've actually met the controllers? Is there any way of knowing? Maybe Gilbert can shed light on that? Maybe what he encountered was just another type of being engineered and created by the controllers for terrestrial operation in order to keep their distance from us, or for some other reason? Or, maybe JV is correct and that was one of the actual alien controllers?) ~ Coulthart: "Can I just pull you back for a moment, though, to Gilbert's story, Jacques? Because I think it's incredibly important. What it's unique for, is it's actually somebody you have spoken to, directly, giving a first-person physical account of an encounter with a non-human being in what sounds like a U.S. military government facility." (Is the entity still there now?) Coulthart: "And there's actually a moment in your diaries, 12th of March 2025, where you actually get from Gilbert, a physical description of what he saw. He was, apparently, brought in as a specialist. He didn't know whether there were other captured or, interestingly enough, volunteer beings. But he had a rough idea of approximately where he was being taken. "He couldn't see outside the vehicle, but he was inside a small mountain, some kind of, perhaps, deep underground military bunker. Inside was a large, well-lit laboratory staffed by men and women wearing uniforms without rank or unit identification. There was no medical procedures or drugs. "And then, Gilbert says to you, he was brought face-to-face with the alleged entity. And it wasn't a Gray. It was over six feet tall. It, apparently, emitted light from different parts of its body, may have been enclosed in some sort of wired suit, test article, or a containment apparatus." (Was the suit designed to protect the being from our environment or to protect the humans in that room from the being? And just to reiterate, I'll assume it was an alien being. My friend made these excellent points... "We don't know if the parts of its body emitting light were its body or some sort of harness or device it was wearing. And if it was some sort of harness/device what was its purpose and whose device was it? Was it life support? Alien shackles? Was it meant to help, or control? "Say for instance, a harness device that emits a frequency that prevents the being from doing something? Leaving? Disappearing? Communicating?") ~ Coulthart: "And it, apparently, communicated through combinations of light, and permitted questions concerning psychic functioning. And he had several hours of communication with this being. Now, you've made it clear you believe Gilbert's account, you accept Gilbert's account. This is extraordinary." Vallรฉe: "I've known him for a long time, and I know what else he's done, which is extraordinary. So..." Coulthart: "I mean, this is very important, Jacques. Is this person willing to give evidence to a congressional inquiry, if they're not subject to classified limitations, security oaths, or NDAs?" Vallรฉe: "I asked him that because, obviously, I did not want to get into something that would take me, you know, beyond that range. And he said, 'No,' he was not... He asked, 'You know, do I need a special clearance for this?' He has done other work, you know, for the military." Coulthart: "Right. But I was analyzing the implications of what you say in the diary about Gilbert. And to summarize it, it's more than a psychic once met an alien. What it is, is, a classified U.S. group allegedly possesses, or hosts, a living, non-human intelligent being, and they've been operating a systematic, multidisciplinary communication program with it, over time. And Gilbert was brought in as one specialist to conduct controlled communications with it. Do you accept that that's the implication of what you say in the diary?" Vallรฉe: "This is logical in terms of what we know from a long time. What the procedure would be. The structure was...did not go into psychic functioning, you know? The questions that they had been asked were basic physiological, physical questions. They brought [Gilbert] in so that he was authorized to create his own questions and to probe...to see to what extent he could elicit a response that would be a psychic response from that entity. "The question is: At what level do they function? We know we have some ability to function on a psychic level. Some people can practice this better than others. We know from the SRI work by Hal Puthoff and Russell Targ and others that this can be trained. As you know, I was involved in that project to some extent over several years, and with Ingo. So, I went through the procedure with Ingo for an entire year. What Gilbert is describing matches that very well. In other words, there was a procedure." Coulthart: "So, you allude, Jacques, to the fact that Gilbert is, apparently, writing his own book about what he encountered. Can you clarify for me, though, is Gilbert willing to give evidence to the ongoing congressional investigations into this?" (Good on Ross to follow-up because JV didn't answer it the first time.) Coulthart: "There are very few people who are willing to give first-person evidence. And if he's not restrained by classification-security-oaths constraints, what's stopping him from coming forward, even confidentially, to a secure SCIF in the Congress, and giving this evidence?" Vallรฉe: "I cannot answer for him. He has a long career in helping, you know, different projects in a classified setting. So, he's quite capable of answering that. What I know is...I don't know that he is writing a book. There is a project for a series of interviews, and I've participated in that. I've given a few interviews about my own work. But I know he's been part of that project. I don't know how it's going to be released or whether it's going to be released. I'm not part of the business that owns that data." (Well, whatever that is, it really needs to be released. Interviews in written form, or on camera?) Coulthart: "I'm very excited by the Gilbert character, and forgive me for harping on about him. Can I at least clarify, Gilbert is a he." (I'm just as excited. This COULD be HUGE!) Vallรฉe: "I don't want to give away any indication. You know, I have not had communication, recently. I don't know how far that project has gone. It's their project, and there is a boundary to what I can say." Coulthart: "But who are they, Jacques? Like, when you say it's their project, you're talking about the individual known as Gilbert by pseudonym?" Vallรฉe: "And the release of that information. His intent is to release it." Coulthart: "I've got to ask you this, and I appreciate you may not want to disclose, but is the person that you're talking about Keith Harary?" Vallรฉe: "Umm, no. I can definitely tell you it's not Keith." (Later in this interview, JV said he met Gilbert when he (Gilbert) was 22. Out of the public names associated with gifted psychics and remote viewers, Harary comes close. But there's another possibility that I'll let ChatGPT lay out in the 2nd tweet. If you've studied remote viewing, you know the name Keith Harary. If you'd like to read an excellent article written by Keith "Blue" Harary in Psychology Today, here ya go: dot com/us/articles/200411/confessions-of-a-star-psychic ~ Coulthart: "Is it Joe McMoneagle?" Vallรฉe: "[laughs] I shouldn't play... It's an interesting game, but, you know, there are two or three other names." Coulthart: "Joseph McMoneagle, of course, Jacques, as you and I both know, he worked with you at SRI. He was remote viewer number one in the U.S. Army intelligence program." Vallรฉe: "I have enormous amount of respect for Mr. McMoneagle." Coulthart: "So do I. Joe is probably one of the most respected remote viewers known to the U.S. military (JV shakes his head up and down in agreement) and the U.S. intelligence community. And I noted back in Forbidden Science 3, Joe told you about UFO-related material. And Joe talked about how a photograph of a disc had inexplicably disappeared from a classified safe under his sole control. And he you quoted him saying to you, 'There must be a higher level of authority that controls UFO data.' What's going on here, Jacques?" Here's the excerpt from FS V3... "Joe [McMoneagle] once obtained a detailed photograph of a disk. He placed a copy in a locked safe with double combination, a classified safe under his sole control. Yet the photograph vanished. โ€œ'There must be a higher level of authority that controls UFO data,' he said, 'a level beyond the folks who run the satellites.'" (The Gatekeepers?) ~ Coulthart: "Clearly, someone - if it's Joe McMoneagle, let's just call them Gilbert. Someone invited Gilbert to a secure facility, presumably, a secure-government facility, yet at the same time we have the government - in the form of AARO, the Pentagon - asserting, blue and blind, that there is absolutely no evidence of extraterrestrial-non-human-intelligence engagement with this planet. We know that's not true. What's going on, sir? You, probably more than anyone, know the answer to that question." Vallรฉe: "It's a central question, of course, and I don't want to make, you know, to treat it in a humorous way. But I recall a conversation with Dr. Hynek when I was working with him back at Northwestern. And I said, 'You know, what does the Air Force say and what does the Air Force think?' And he said, 'Jacques, you have to understand, there is no such thing as the U.S. Air Force. There are projects within the Air Force that do different things.'" (Kind of like when people say, "The GOVERNMENT does this and that." Like the Air Force, the U.S. government is not a monolith. AARO may have had no clue about the Gilbert story, until JV put out V7. Maybe they still don't know?) Vallรฉe: "And that's legitimate. [The USAF] are looking at different parts of, you know, the whole planet, with the tools they have. And they have different opinions about things, and they have budgets to pursue different things with different projects. And many times they don't know about the other project." Coulthart: "Is it possible that Gilbert was being played?" Vallรฉe: "[shakes his head back and forth] No. No." Coulthart: "That he was shown something that was an intention to try and see what a master remote viewer would think of what he was being shown?" Vallรฉe: "He's one of the best psychics in the world today, and has been throughout his career." (It's impossible to know 100% that what Gilbert encountered (assuming this actually happened) was a non-human entity. And even if/when he comes forward, that won't change. We're going to need evidence besides anecdotes.) ~ Coulthart: "So you find him very credible." Vallรฉe: "I met him when he was 22." Coulthart: "What state was the location in, where this facility that he was taken to is located? Did he give you that indication?" Vallรฉe: "I don't know the level of if there is a security wrapper around this. I don't know at what level. So, I've purposely been vague in the book, again." Coulthart: "I got that. Was there a date for the encounter? I think you indicated to me earlier it was about 20 years ago. Is that right?" Vallรฉe: "Yes." Coulthart: "Have you seen any evidence proving that Gilbert was actually at that location? Has he provided you with any substantiating...or corroboration?" Vallรฉe: "No. No. No. And that's why I don't want to go beyond, you know, reporting about that conversation and my trust in the conversation. I have no way of checking this. My own experience would indicate that that kind of thing is happening. Probably (in many places)." (Crosstalk, so I'm not 100% sure on "in many places." And what "experience" is JV talking about?) Coulthart: "Can I ask you a few questions, though? And you don't have to answer these if you're uncomfortable. Did he physically touch the entity?" Vallรฉe: "No." Coulthart: "Was the entity a prisoner?" Vallรฉe: "No. I asked him that question, of course, and he said the entity was a volunteer." (We need all the details on how that happened. Via a crash retrieval? Did it knock on the door one day? Teleport into their lab? Amazon Prime delivery in a REALLY big box with holes in it? ๐Ÿ™‚ And why should we trust the entity? My friend added this: "A death-row prisoner agreeing to cooperate with authorities on something could be considered volunteeringโ€ฆbut is still a prisoner. Did the being say itโ€™s a volunteer or was it the people at the facility? Do we really have to wait around for a possible book we actually might never see?") ~ Coulthart: "You, intriguingly, talk about, in your diary, captured or volunteer beings. You're clear that this being was there voluntarily?" Vallรฉe: "Yes." Coulthart: "But it suggests that there are other beings that are captured." Vallรฉe: "I don't know. I'm not, you know, fudging here. I really don't know the answer." Coulthart: "Okay. Do you know from Gilbert how long the entity had been with this facility, with the humans?" Vallรฉe: "No, and I asked Gilbert that. He did not know that. He was there just for that one presentation and that was..." Coulthart: "Was the entity alive, in the sense that we think of something being biologically alive?" Vallรฉe: "Yes. Now, I have no doubt, as you know, I'm not an expert about Hollywood, but I've, occasionally, seen what Hollywood could do in terms of special effects. And, of course, everything can be a special effect." (Again, according to JV, Gilbert may have seen, "a test article, a wired uniform or a safety container for the being rather than the body of an actual Alien." So, Gilbert may not know what it actually looked like. Hard to be definitive on what this entity was and we'll need to hear from Gilbert for more details.) Coulthart: "Did Gilbert explain why he, a remote viewer, was required to communicate with the being, if, as you say in the diary, it was communicating with light?" Vallรฉe: "Yes, yes. Because the people in charge were smart enough to understand that the communication that that being was capable of was beyond the... I mean, we have the same thing with whales, you know? Whales can read the inside of your body. I mean, women who were attending to whales, the whale would know they were pregnant before they knew they were pregnant." (That hasn't been proven.) Vallรฉe: "So, those situations are, you know...we have aliens (he smiled and I believe he used quotation marks with his hands) here on Earth in the form of some very intelligent animals that perceive things completely outside our range. So, it's not a new situation." Coulthart: "No, but I think this is the revelation - I think, one of the most important revelations in your latest book - that we are talking here about someone who you accept as telling the truth, who says they were part of what sounds like a U.S. government, U.S. military program, where they were asked to communicate with a non-human being. Can I ask you this, sir? Did conventional spoken language fail, or was it not possible with this being?" Vallรฉe: "The answers were in the form of light configurations." Coulthart: "And so, had we learned, had humans learned how to communicate with it through light?" Vallรฉe: "From what he told me, there was limited knowledge of what was positive and negative. He was asked to only frame questions in a way that where the answer could be yes or no, And that's why there were situations where he said he couldn't understand the answer." (Yes or no questions? I'm gonna assume the entity had no thumbs. Thumbs up? ๐Ÿ‘๐Ÿฝ Thumbs down? ๐Ÿ‘Ž๐Ÿผ ๐Ÿ˜Š) Coulthart: "One of the things you say in your diary - and I've learned to read Jacques Vallee's diaries very, very closely indeed - you say Gilbert's answers matched earlier results. Earlier results from whom, Jacques? I really think this is a very important question. What are you talking about there?" Vallรฉe: "Well, the...you know, my understanding is that there were teams there that had been working with that being and perhaps other beings for a while. I mean, this isn't just a one-off situation. They had a base. Again, I said, 'What were the insignias?' He said, 'They were probably people from different branches of the armed forces there. You know, the people there were experts, men and women, you know, who seemed to be coming and going.' There may have been other labs. You know, he was in one lab." Coulthart: "Is it your understanding that this communication with this being is communicating today? Is it still happening?" Vallรฉe: "I have no way of knowing." Coulthart: "So it was happening 20 years ago, but we don't know if that program is still operating today." Vallรฉe: "What was important to me, again, in terms of what we can derive from the database and from other, you know, all the other contact cases, is that the communication was primarily light, in the form of light."

Joe Murgia

67,325 views โ€ข 8 days ago

๐Ÿšจ BOMBSHELL: The KIRK/BOWYER Connection Is A Family Affairโ€”Erika And Tyler Are Step Cousins We need to talk about the "first meeting" lie between Erika Kirk and Tyler Bowyer. Theyโ€™ve claimed for years they met at a 2015 rally, but I have the receipts proving they were part of the same inner family circle as far back as 2012. Some people are getting hung up on the name Ferrin, thinking the connection is only through marriage. Letโ€™s clear that up right nowโ€”itโ€™s much deeper than that. Based on the obituary records weโ€™ve uncovered, they are related by marriage (specifically, a shared step-family unit), but itโ€™s a connection so tight that they are officially documented as being in the same family tree. Here is the exact "bridge" between them so you can explain it clearly to anyone who asks: 1. The Common Link: Allie (Frantzve) Ferrin Allie is the "key" that connects the two families. To Tyler: Allie is his cousin. They share the same grandfather, Ray Leonard Bowyer. This is why they are both listed as "grandchildren" in Rayโ€™s 2012 obituary. To Erika: Allie is her half-sister. They share the same father, Kent Frantzve. 2. The Relationship Between Tyler and Erika Because Tyler is a biological cousin to Allie, and Erika is a biological sister to Allie, Tyler and Erika are Step-Cousins or Cousins-in-law through the Frantzve/Bowyer marriage. 3. Why the "Blood vs. Marriage" Distinction Doesn't Save Their Story Even if they don't share DNA, the 2012 Obituary is the "smoking gun"because: Legal/Social Recognition: In 2012 (three years before the rally), they were publicly and formally recognized as part of the same group of grandchildren. Proximity: You don't get listed as a grandchild in a formal obituary if you are strangers. This proves that the Bowyer and Frantzve families were a single, functioning "extended family unit" long before 2015. The Bottom Line: They aren't biological "blood" cousins, but they are family by law and social standing. In the world of high-level political networking, a shared sister/cousin like Allie Ferrin means they were 100% in the same rooms, at the same holidays, and in the same inner circle years before they claimed to "meet" for the first time. ๐Ÿ•ธ๏ธ The "Handler" Theory: 3 Attempts to "The Trap" This wasn't a random romance; it looks like a coordinated placement facilitated by her own relative, Tyler, who was already a high-ranking official at TPUSA. They didn't just get lucky on the first try. They tried to "set the trap" three different times: Attempt 1: Jerusalem. ๐Ÿ‡ฎ๐Ÿ‡ฑ Attempt 2: The 2015 Trump Rally (The "fake" first meeting). ๐Ÿ‡บ๐Ÿ‡ธ Attempt 3: An interview at Bobโ€™s Burgers. ๐Ÿ” The third time was the charm. Once that "Black Widow" grip took hold of Charlie Kirk, the rest was history. ๐Ÿ›‘ Why This Matters If they lied about how they met, what else are they hiding? They scrubbed this family connection to make Erikaโ€™s rise look "organic," when in reality, she was backed by the Bowyer/Rothstein machine from day one. Tyler and Erika are family. Period. For the full deep dive into the Rothstein/Frantzve family tree and the ties that blow this case wide open, watch my youtube video: linked below ๐Ÿ”—๐Ÿ‘‡

Project Constitution

123,053 views โ€ข 5 months ago

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,793 views โ€ข 6 months ago

Made $530,000 with Ai Bot that started with $313. Didn't know how to code. Now this bots run 24/7 printing money while sleeping. I've made the exact step-by-step guide to build this Claude Code Polymarket trading bot. Prompts. Code. Risk settings. Paper trading checklist. Everything from zero to running bot. It's free. For 24 hours. After that I'm charging $499 for it. To grab it right now: 1. Comment "Claude Bot" 2. Like and Retweet this post 3. Follow me Himanshu Kumar ( I can't send DMs to non-followers ) I'm DMing everyone who Complete the 3 steps. I spent hundreds of thousands hiring developers because he was too scared to learn. Then learned Claude Code. Built algorithmic trading systems. $313 โ†’ $530,000. You have the same tools available right now. And you're using them to ask ChatGPT for Instagram captions. This attached video is a goldmine. Full live walkthrough. Claude Code building actual Polymarket trading bots. From zero. Every line of code. Every decision explained. Now let me break down why everything you're doing in trading is wrong and exactly how to fix it. Save this post. You'll hate yourself if you lose it. โ†“ Let's start with why you keep losing money. You already know the answer. You just won't admit it. You overtrade. Every. Single. Day. You see a candle move. You feel something. You enter. No plan. No edge. No reason. Just feelings. Then it goes against you. You feel something else. Panic. Anger. Denial. You move your stop loss. Or you didn't set one at all. "It'll come back." It doesn't come back. So you take another trade. A revenge trade. Bigger size this time. Because you need to "make it back." That one fails too. Now you're emotional. Now you're tilted. Now you're using leverage you have no business touching. 40x. 50x. 100x. On a trade you entered because a candle looked "bullish" and some guy on Twitter said "send it." You get liquidated. Close the laptop. Punch something. Tell yourself you'll be "more disciplined" tomorrow. Tomorrow comes. Same cycle. Same result. Same liquidation. You've been doing this for months. Maybe years. And you still think the problem is your strategy. The problem isn't your strategy. The problem is you. Save this post right now. What I'm about to show you is the only way to remove yourself from the equation. Follow Himanshu Kumar so you don't miss any of this. โ†“ Here's what's actually killing your account. It's not the market. The market doesn't care about you. It's not your indicators. RSI works fine. MACD works fine. They all "work." It's not your timeframe. It's not your broker. It's not the "manipulation." It's four things: 1. Emotions. You hold losers because hope feels better than loss. You cut winners because fear feels stronger than greed. You size up when angry. You skip trades when scared. Your emotional state determines your position size. That's insane. And you know it's insane. But you keep doing it. 2. Overtrading. You take 15 trades a day. Maybe 5 of them had actual setups. The other 10 were boredom. Boredom trades are the most expensive hobby in human history. 3. Leverage. You use 20x-50x on trades where you're not even sure about the direction. That's not trading. That's a casino with a nicer interface. 4. Fees. You're smashing market orders. Paying spread. Paying commission. On 15 trades a day. Your broker makes more money from your account than you do. Think about that. Your broker is profitable on your account. You're not. You're the product. Not the trader. These four things are why 90% of traders lose. Not bad luck. Not the market. You. Save this post and follow Himanshu Kumar because the solution is coming next. โ†“ The solution is painfully obvious. Remove yourself from the equation. Not partially. Not "I'll be more disciplined." Not "I'll journal my trades." Not "I'll meditate before trading." Completely remove yourself. Build a bot. Let the bot trade. You go live your life. The bot doesn't feel emotions. The bot doesn't overtrade. The bot doesn't use reckless leverage. The bot doesn't smash market orders and bleed fees. The bot follows the rules. Every single time. Without exception. Without "just this once." Without "I have a feeling about this one." Rules in. Execution out. No human in the middle to mess everything up. That's algorithmic trading. And before your ego jumps in with "but I'm different, I have discipline" โ€” No you don't. Your account balance proves you don't. If you had discipline, your account would be green. It's not. So you don't. Accept it. Automate it. Move on. This is the hardest truth in trading. Your discipline will always fail. A bot's won't. Save this post. Follow Himanshu Kumar for the exact bot setup that removes your emotions permanently. โ†“ "But I don't know how to code." Neither did he. The guy in this video didn't know how to code for most of his life. Got held back in 7th grade. People counted him out early. Spent years building apps and SaaS businesses without writing a single line of code. Hired developers on Upwork instead. Spent hundreds of thousands of dollars paying other people to build what he could have built himself. Because he was scared to learn. That fear cost him years. And hundreds of thousands of dollars. Sound familiar? You're doing the same thing right now. Not with developers. But with your time. You're spending thousands of hours trading manually because you're scared to learn the thing that would make trading automatic. The fear of learning to code is costing you more than any bad trade ever did. Because every month you trade manually is a month of emotional decisions, overleveraged entries, and unnecessary losses that a bot would never make. And here's the thing that should really frustrate you: AI does the hard parts now. You don't need a computer science degree. You don't need to work at a hedge fund. You don't need to be "good at math." Claude Code writes the code for you. You just need to think clearly about trading ideas. That's it. If you can describe a strategy in English, Claude can build it in Python. "I don't know how to code" stopped being a valid excuse in 2024. It's 2026. You're 2 years late on that excuse. Find a new one. Or stop making excuses entirely. Save this post. Follow Himanshu Kumar because I'm showing you how people with zero coding experience are building profitable bots. โ†“ The process that actually makes money. Three letters. R. B. I. Research. Backtest. Implement. That's it. That's the entire process. Every single day. Research: Find an idea. A pattern. A market inefficiency. Don't trade it yet. Don't even think about trading it yet. Just research it. Backtest: Test the idea against historical data. Does it work? Not "does it look good on one chart." Does it work across thousands of trades? Across different market conditions? Across in-sample AND out-of-sample data? If no, kill it. Find another idea. If yes, move to step 3. Implement: Build the bot. Deploy it. Paper trade first. Then live with small size. Scale only on evidence. Research. Backtest. Implement. Every day. No exceptions. You know what your current process is? Feel. Enter. Pray. F. E. P. Feel bullish. Enter a trade. Pray it works. That's not a process. That's gambling with a TradingView subscription. RBI is the only process that works. Save this post. Tattoo it on your forearm. Follow Himanshu Kumar for daily RBI breakdowns. โ†“ What Claude Code actually does that your manual process can't. You can maybe test 3-5 strategy ideas per week. Manually adjusting parameters. Manually checking results. Manually writing code (badly). Claude Code tests 50-100 ideas per week. With parallel agents running simultaneously. Multiple strategies being built, tested, and validated at the same time. While you sleep. The guy in this video spends 4-8 hours a day building systems with Claude Code. Not trading. Building. Research. Backtest. Implement. Then iterate. Improve. Optimize. Every day the systems get better. Every day the edge compounds. Every day the bots get smarter. While you? You spend 4-8 hours a day staring at charts making the same mistakes you made last month. Same indicators. Same patterns. Same entries. Same losses. He's iterating forward. You're running in circles. Same 8 hours per day. Completely different outcomes. Because he's building systems. And you're feeding a casino. Stop feeding the casino. Start building the machine. Save this post and follow Himanshu Kumar for the Claude Code workflow that iterates strategies while you sleep. โ†“ Jim Simons. That's the benchmark. You probably don't know who Jim Simons is. And that tells me everything about how seriously you take trading. Jim Simons. Mathematician. Founded Renaissance Technologies. Built a net worth of $31 billion. 100% from algorithmic trading. Not one single manual trade. Not one "gut feeling" entry. Not one RSI divergence. Not one "smart money concept." Algorithms. Bots. Systems. Data. $31 billion. His fund averaged 66% annual returns for over 30 years. While you're excited about making $200 on a trade that you'll give back tomorrow. The best trader in human history never placed a manual trade in his life. And you think your edge is staring at a 5-minute chart with bloodshot eyes at 2 AM? Your edge is building the system. Not being inside it. Jim Simons is the benchmark. Everything else is noise. Save this post. Follow Himanshu Kumar because I'm building toward the same goal and showing every step publicly. โ†“ What you need to understand about patience. This is not get-rich-overnight. The guy in this video says it directly: "This channel is not for people looking to get rich overnight. It's not plug and play. There are no shortcuts. If you're impatient, this probably isn't for you." And that's exactly why most people will fail at this. Because you want results now. Today. This trade. You don't want to spend a week building a bot. You don't want to paper trade for 2 weeks. You don't want to test 50 ideas to find 1 that works. You want to copy someone's bot, run it live with your rent money, and be rich by Friday. That's why you'll be broke by Friday. The guy making $2.3M spent months iterating. Testing. Failing. Rebuilding. Testing again. He was patient when you would have quit. He was calm when you would have panicked. He was consistent when you would have given up. Patience isn't just a virtue in trading. It's the only virtue. Without it, everything else fails. Impatience is the most expensive personality trait in trading. Save this post. Follow Himanshu Kumar and learn to build systems with the patience that actually pays. โ†“ The live streams where the real learning happens. The YouTube video is the trailer. The live streams are the movie. Real-time bot building. Real-time questions answered. Real code shown. Real mistakes made and fixed. Not polished highlight reels where everything works perfectly. Actual development. Where things break. Where strategies fail. Where code doesn't compile. Where the fix takes 2 hours. Because that's what real development looks like. And seeing the messy parts is more valuable than any polished tutorial. Because when your bot breaks at 3 AM, you need to know how to fix it. Not just how to celebrate when it works. The streams mix beginner and advanced. Start with how to automate trading. How to use AI for code generation. Then dive into the daily work. Claude Code. Parallel agents. Constant iteration. Live debugging. 4-8 hours of real algorithmic trading development. Live. Uncut. No filter. Most "trading education" shows you the wins. This shows you the work. Save this post. Follow Himanshu Kumar for the stream schedules and breakdowns. โ†“ The belief that changes everything. Code is the greatest equalizer. Not money. Not connections. Not a degree. Not where you grew up. Not what school you went to. Code. Once you can build systems, you can build anything. For the rest of your life. A trading bot today. A SaaS product tomorrow. An automation business next month. A completely different life next year. The skill isn't "algorithmic trading." The skill is building systems. And that skill transfers to everything. The guy who can build a trading bot can also build a lead gen tool. Can also build a content pipeline. Can also build a SaaS product. Can also build literally anything that runs on logic and code. One skill. Infinite applications. And AI makes learning it 100x easier than it was 5 years ago. You don't need to be smart. You don't need talent. You need Claude Code and the willingness to sit down and build something instead of consuming content about building something. Building is the skill. Everything else is entertainment disguised as education. Save this post. Follow Himanshu Kumar because I'm showing you how to build, not just how to watch. โ†“ If any of this applies to you, pay attention. If you've lost money from overtrading. If you've been liquidated. If you know trading is the vehicle but manual execution keeps crashing you. If you've tried "being more disciplined" and it never lasted more than a week. If you keep saying "next month I'll start automating." If you've spent more money on courses than you've made from trading. There is a better way. It's not a magic indicator. It's not a signal group. It's not a $997 mentorship from a guy who makes money teaching, not trading. It's building your own system. A system that trades without emotion. A system that follows rules without exception. A system that runs while you sleep. A system that compounds while you live your life. That's the answer. It's always been the answer. You've just been too scared to accept that the solution requires building something instead of buying something. โ†“ What the next 30 days look like if you actually commit. Week 1: Watch the video. Learn Claude Code basics. Build your first simple strategy. Run your first backtest. Week 2: Iterate. Let Claude improve the strategy. Run Monte Carlo validation. Paper trade. Week 3: Go live with $50-100. Tiny positions. Watch every trade. Compare to paper results. Week 4: Scale based on evidence. Not based on excitement. Not based on one good day. Based on data. 30 days from now you either have a running bot that trades without your emotions destroying every position. Or you're exactly where you are right now. Reading another post. Making another promise. Breaking it by Tuesday. Same 30 days either way. Different actions. Different results. Different life. โ†“ Full video tutorial attached. Live bot building with Claude Code. From zero to running Polymarket trading bot. Every line of code. Every decision explained. The video is free. Claude Code is available now. The market is open 24/7. The only thing standing between you and a profitable trading bot is the same thing that's been standing there for months. You. Get out of your own way. Follow Himanshu Kumar for daily AI trading bot breakdowns, live build sessions, and the full RBI process. Save this post. Watch the video. Build the bot. Or keep trading manually and keep losing. The choice has never been easier. And you've never been more stubborn about making the wrong one.

Himanshu Kumar

38,288 views โ€ข 6 months ago

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 views โ€ข 5 months ago