Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

🇲🇽 Juan Hernandez data 🇲🇽 🚀 Wins Nunthorpe on flying machine (Bacio) 🚁 Gets on another flying machine (helicopter) ✈ Before boarding third flying machine (plane) 😮 Next ride 5300 miles away at Del Mar. Two more Grade 1 rides there before the weekend is over. Racing TV |...

Race_iQ's profile picture

RaceiQ

7,925 subscribers

43,837 Aufrufe • vor 1 Monat •via X (Twitter)

SportNachrichten & Politik
LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

The National Transportation Safety Board said on Tuesday that evidence recovered from the ​Amazon Prime Air 767 flight data recorder suggested the pilots considered aborting the landing ‌after the aircraft touched down. The NTSB said ⁠30 seconds before the end of the flight data recording, the nose landing gear and ​right main landing gear touched down on the runway at a speed of 158 knots (181 ​mph), while 19 seconds before the end of the recording, the left main landing gear touched down at a speed of 134 knots. A few seconds later, the brakes were released and the throttles were increased to ​values consistent with go-around thrust, indicating a late attempt to abort the landing and ​get back in the air. But 11 seconds before the end of the recording, throttles were reduced to idle ‌power ⁠and brakes were reapplied. The final ground speed was 65 knots at the end of the recording. The NTSB said there was no indication in the recorded data that speed brakes or thrust reversers were deployed to help slow the plane. NTSB Chair ​Jennifer Homendy told reporters that investigators would interview both of the pilots on ​Wednesday and then release details from the cockpit voice recorder. Homendy is leading a team of 32 ​investigators at Miami International ​Airport. She said ⁠the NTSB was able to release one of two runways closed since the accident to allow for departures from an easterly direction late ​on Tuesday. The Amazon cargo plane was on its third flight of ​the day, coming ⁠from San Juan, Puerto Rico. It had flown from Cincinnati to Miami and from Miami to San Juan earlier on Sunday before the crash at 1:53 p.m. EDT (1753 GMT). The captain, 55, ⁠received his ​type rating for the 767 in May and has ​7,145 hours of flight time, while the first officer, 37, received his type rating on the 767 in April ​2025 and has 2,655 flying hours, the NTSB said.
1:07

The National Transportation Safety Board said on Tuesday that evidence recovered from the ​Amazon Prime Air 767 flight data recorder suggested the pilots considered aborting the landing ‌after the aircraft touched down. The NTSB said ⁠30 seconds before the end of the flight data recording, the nose landing gear and ​right main landing gear touched down on the runway at a speed of 158 knots (181 ​mph), while 19 seconds before the end of the recording, the left main landing gear touched down at a speed of 134 knots. A few seconds later, the brakes were released and the throttles were increased to ​values consistent with go-around thrust, indicating a late attempt to abort the landing and ​get back in the air. But 11 seconds before the end of the recording, throttles were reduced to idle ‌power ⁠and brakes were reapplied. The final ground speed was 65 knots at the end of the recording. The NTSB said there was no indication in the recorded data that speed brakes or thrust reversers were deployed to help slow the plane. NTSB Chair ​Jennifer Homendy told reporters that investigators would interview both of the pilots on ​Wednesday and then release details from the cockpit voice recorder. Homendy is leading a team of 32 ​investigators at Miami International ​Airport. She said ⁠the NTSB was able to release one of two runways closed since the accident to allow for departures from an easterly direction late ​on Tuesday. The Amazon cargo plane was on its third flight of ​the day, coming ⁠from San Juan, Puerto Rico. It had flown from Cincinnati to Miami and from Miami to San Juan earlier on Sunday before the crash at 1:53 p.m. EDT (1753 GMT). The captain, 55, ⁠received his ​type rating for the 767 in May and has ​7,145 hours of flight time, while the first officer, 37, received his type rating on the 767 in April ​2025 and has 2,655 flying hours, the NTSB said.

Breaking Aviation News & Videos

424,103 Aufrufe • vor 1 Monat

Yann LeCun just told the most well-funded industry in human history it is solving the wrong problem. LeCun: “Babies learn this around the age of eight or nine months, that objects don’t float, they fall.” No dataset. No labels. No reward signal. A nine month old drops a spoon and builds a physics engine no machine can match. LeCun: “Most of us can learn to drive in about 20 or 30 hours of training without ever crashing, causing any accident.” Twenty hours. Tesla has built the most capable driving system on the road. It took billions of miles of data to get there. A sixteen year old gets there over a long weekend. Not because the teenager is the better driver. Because the teenager is not learning to drive. They are deploying a model of reality they have been building since birth. LeCun: “If we drive next to a cliff, we know that if we turn the wheel to the right, the car is going to run off the cliff and nothing good is going to come out of this.” You simulate the crash. You see the wreckage. You feel the fall. You turn the wheel. None of it was real. All of it was intelligence. Every AI has to crash a thousand times to learn what you imagined once and never did. That is not a performance gap. That is an architecture gap. LeCun: “The main problem we need to solve is how do we learn models of the world.” Not bigger models. Not more compute. Not another trillion tokens. World models. A machine that can run reality forward before it acts. The industry is scaling language. LeCun says language is a compression of thought. Not thought itself. You understood gravity before you could say the word. You grasped cause and effect before your first sentence. The deepest intelligence you will ever possess was built in total silence. And every lab on Earth is trying to reconstruct the mind from words alone. Physics does not care about your context window. A baby who learns that cups fall in a kitchen already knows that rocks fall off cliffs. No retraining. No fine-tuning. One model. Every environment. That is what intelligence actually is. Not prediction. Not pattern matching. Not scale. A simulation of reality so precise you rehearse the future before it exists. Every infant on Earth builds one. No machine ever has.
1:45

Yann LeCun just told the most well-funded industry in human history it is solving the wrong problem. LeCun: “Babies learn this around the age of eight or nine months, that objects don’t float, they fall.” No dataset. No labels. No reward signal. A nine month old drops a spoon and builds a physics engine no machine can match. LeCun: “Most of us can learn to drive in about 20 or 30 hours of training without ever crashing, causing any accident.” Twenty hours. Tesla has built the most capable driving system on the road. It took billions of miles of data to get there. A sixteen year old gets there over a long weekend. Not because the teenager is the better driver. Because the teenager is not learning to drive. They are deploying a model of reality they have been building since birth. LeCun: “If we drive next to a cliff, we know that if we turn the wheel to the right, the car is going to run off the cliff and nothing good is going to come out of this.” You simulate the crash. You see the wreckage. You feel the fall. You turn the wheel. None of it was real. All of it was intelligence. Every AI has to crash a thousand times to learn what you imagined once and never did. That is not a performance gap. That is an architecture gap. LeCun: “The main problem we need to solve is how do we learn models of the world.” Not bigger models. Not more compute. Not another trillion tokens. World models. A machine that can run reality forward before it acts. The industry is scaling language. LeCun says language is a compression of thought. Not thought itself. You understood gravity before you could say the word. You grasped cause and effect before your first sentence. The deepest intelligence you will ever possess was built in total silence. And every lab on Earth is trying to reconstruct the mind from words alone. Physics does not care about your context window. A baby who learns that cups fall in a kitchen already knows that rocks fall off cliffs. No retraining. No fine-tuning. One model. Every environment. That is what intelligence actually is. Not prediction. Not pattern matching. Not scale. A simulation of reality so precise you rehearse the future before it exists. Every infant on Earth builds one. No machine ever has.

Dustin

122,444 Aufrufe • vor 3 Monaten

Media buying is changing faster than most people realize. Don't believe me? True Classic runs 100% of their Meta spend through automated media buying in Triple Whale 🐳. Meta is their biggest channel. When a brand hands you their biggest channel, that's the ultimate trust. My wife and I built Madison Braids, and I lived in those ad accounts for years. Media buying is simple in theory, brutal in practice. In theory: find the winners, cut the losers, keep the creative fresh. In practice? You turn into a day trader. Glued to the dashboard, refreshing hourly, combing through spreadsheets, second-guessing every move. And I'll admit the part nobody likes to: some days my mood was dictated by the ROAS in my own account. Numbers up, I'm flying. Numbers down, the whole day goes with it. That's a brutal way to run a business and a worse way to live. More data never fixed it. More dashboards, more "insights"...none of it gave me an hour back. It just gave me more to comb through. That's why we built Moby Automations. You hand Moby the repetitive work and it runs on a schedule, on your live Triple Whale data. And because it's built on frontier LLMs, it keeps getting sharper, reasoning through your data the way a good buyer would, not just following rules. "Check my Meta campaigns every morning and give me actions based on my scaling rules." "Find my fatigued creatives every week and build new variants from what's working." Moby does the work and queues every action for your approval. You stay in control. Your team gets their time back. But here's why I'm actually excited. It's bigger than time saved. This is work that should be done by a machine. Hand it over, and you get back the parts that matter: your focus, your creativity, your humanity. That's the real leverage. The machine watches the data. You go find the next channel, the next opportunity, the next bet that grows the business. That's our play. Moby Automations are live. Go put one to work.
1:50

Media buying is changing faster than most people realize. Don't believe me? True Classic runs 100% of their Meta spend through automated media buying in Triple Whale 🐳. Meta is their biggest channel. When a brand hands you their biggest channel, that's the ultimate trust. My wife and I built Madison Braids, and I lived in those ad accounts for years. Media buying is simple in theory, brutal in practice. In theory: find the winners, cut the losers, keep the creative fresh. In practice? You turn into a day trader. Glued to the dashboard, refreshing hourly, combing through spreadsheets, second-guessing every move. And I'll admit the part nobody likes to: some days my mood was dictated by the ROAS in my own account. Numbers up, I'm flying. Numbers down, the whole day goes with it. That's a brutal way to run a business and a worse way to live. More data never fixed it. More dashboards, more "insights"...none of it gave me an hour back. It just gave me more to comb through. That's why we built Moby Automations. You hand Moby the repetitive work and it runs on a schedule, on your live Triple Whale data. And because it's built on frontier LLMs, it keeps getting sharper, reasoning through your data the way a good buyer would, not just following rules. "Check my Meta campaigns every morning and give me actions based on my scaling rules." "Find my fatigued creatives every week and build new variants from what's working." Moby does the work and queues every action for your approval. You stay in control. Your team gets their time back. But here's why I'm actually excited. It's bigger than time saved. This is work that should be done by a machine. Hand it over, and you get back the parts that matter: your focus, your creativity, your humanity. That's the real leverage. The machine watches the data. You go find the next channel, the next opportunity, the next bet that grows the business. That's our play. Moby Automations are live. Go put one to work.

Maxx Blank 🐳

306,002 Aufrufe • vor 4 Monaten

Walter Isaacson reveals the wild story of Elon Musk making a U-turn mid-flight on Christmas Eve to raid his own server facility "And the engineer, and I'm sitting there in the meeting and he's getting really dark and they don't know how to deal with him because this is like a month after he took over Twitter. So they don't know this dude. And they say, well, no, I'm sorry, Elon, we can't do it. And that, and he'd say, you can do it in six weeks. And by the end of the meeting, he said, you can do it in six days." "He gets really dark and he decides he's going to fire them, but it's December 23rd. So it's like two days before Christmas. He does fire them." "But the next day, Christmas Eve, he's flying from San Francisco to Austin, Texas to go home for Christmas. He's with two young cousins on the plane who are engineers. And one of them says, why don't we just take those servers out ourselves?" "Elon Musk makes a U-turn in his airplane, tells the pilot to go to Sacramento. They were already over Nevada. They land. He rents, there are like four of them on the plane. They rent a truck, a sort of what we call a U-Haul truck, a rental truck. And they go to the server facility, and the guard there is like flummoxed. It's Christmas Eve, and they're forcing their way in, and they're looking at the servers, and one of the engineers says,"
1:10

Walter Isaacson reveals the wild story of Elon Musk making a U-turn mid-flight on Christmas Eve to raid his own server facility "And the engineer, and I'm sitting there in the meeting and he's getting really dark and they don't know how to deal with him because this is like a month after he took over Twitter. So they don't know this dude. And they say, well, no, I'm sorry, Elon, we can't do it. And that, and he'd say, you can do it in six weeks. And by the end of the meeting, he said, you can do it in six days." "He gets really dark and he decides he's going to fire them, but it's December 23rd. So it's like two days before Christmas. He does fire them." "But the next day, Christmas Eve, he's flying from San Francisco to Austin, Texas to go home for Christmas. He's with two young cousins on the plane who are engineers. And one of them says, why don't we just take those servers out ourselves?" "Elon Musk makes a U-turn in his airplane, tells the pilot to go to Sacramento. They were already over Nevada. They land. He rents, there are like four of them on the plane. They rent a truck, a sort of what we call a U-Haul truck, a rental truck. And they go to the server facility, and the guard there is like flummoxed. It's Christmas Eve, and they're forcing their way in, and they're looking at the servers, and one of the engineers says,"

Kenzo

1,450,241 Aufrufe • vor 3 Monaten

Local AI 101: open models, Hugging Face, and businesses to build (38 min masterclass) I still think cloud AI is the default for most things, and honestly it should be, the frontier models are the strongest and easiest to use. But something shifted in the last 4-5 months. You can now run genuinely good open models directly on your own laptop, or even your phone. And once you actually try it, it changes how you think about what AI is even for. LOCAL AI, CLEARLY EXPLAINED: 1. The model is the brain doing the thinking. Gemma, Llama, Mistral, and Qwen are the main families, and each is better at different things, some at reasoning, some at coding, some small enough to run on a phone. 2. Hugging Face is the warehouse where you find them. You go there to see what each model is good at, check the license, and grab the compressed versions that run on a normal computer. 3. The software is what runs the model on your machine. Start with LM Studio if you're not technical, it feels like a normal app where you search, download, and start chatting. Ollama is the one you reach for when you want to plug a model into your own apps. 4. The workflow is the actual product you build on top of it all. That's what I'm ideating around for some businesses to create. I think local AI just made a specific kind of business way easier to start. Find an industry that: 1. Sits on sensitive data they'd never paste into ChatGPT 2. Does the same review over and over 3. Runs on software from 2003 Then build a local AI tool that does that review on their own machine, so the data never leaves the building! Take home health agencies. Nurses write visit notes all day, and if a note is missing a detail, the billing gets denied or the audit flags it. Here's how I'd start: 1. Find 5 small agencies. Offer to review a batch of their notes for them. 2. Run the notes through Gemma locally (free, private, no cloud). Read every output yourself. 3. Write down the 20 issues that keep showing up: missing vitals, vague med changes, notes that don't support the billed level. 4. That list of 20 is your checklist. The checklist is the product. 5. Turn it into a local desktop app that flags those 20 things before a note gets submitted. You just went from a service anyone could offer to a product nobody else has, and you learned exactly what to build by doing the work by hand first. Same recipe works for restoration contractors (draft the damage report on-site before the tech leaves) and wealth advisors (catch the compliance landmine in a client email before it sends). Basically the framework is sensitive data, repeated review, ancient software. I think there are tons of businesses like this! Almost none of it clicked for me until I actually started using local AI. So if you take one thing from this, go run a model on your own machine once. Also a fun thing to try with your friends. Feel free to send this to a friend. The episode is live for free on The Startup Ideas Podcast (SIP) 🧃 (thanks to Google for sponsoring today's episode and supporting local AI) I feel like local AI one of those things you need to try for it to really click. Run one model on your own machine and you'll see what I mean! I go way deeper in the full 38 minute masterclass, the models, the setup, and the businesses to build. Link below. LINK TO WATCH: OR WATCH BELOW ON X What do you think of local AI?
38:45

Local AI 101: open models, Hugging Face, and businesses to build (38 min masterclass) I still think cloud AI is the default for most things, and honestly it should be, the frontier models are the strongest and easiest to use. But something shifted in the last 4-5 months. You can now run genuinely good open models directly on your own laptop, or even your phone. And once you actually try it, it changes how you think about what AI is even for. LOCAL AI, CLEARLY EXPLAINED: 1. The model is the brain doing the thinking. Gemma, Llama, Mistral, and Qwen are the main families, and each is better at different things, some at reasoning, some at coding, some small enough to run on a phone. 2. Hugging Face is the warehouse where you find them. You go there to see what each model is good at, check the license, and grab the compressed versions that run on a normal computer. 3. The software is what runs the model on your machine. Start with LM Studio if you're not technical, it feels like a normal app where you search, download, and start chatting. Ollama is the one you reach for when you want to plug a model into your own apps. 4. The workflow is the actual product you build on top of it all. That's what I'm ideating around for some businesses to create. I think local AI just made a specific kind of business way easier to start. Find an industry that: 1. Sits on sensitive data they'd never paste into ChatGPT 2. Does the same review over and over 3. Runs on software from 2003 Then build a local AI tool that does that review on their own machine, so the data never leaves the building! Take home health agencies. Nurses write visit notes all day, and if a note is missing a detail, the billing gets denied or the audit flags it. Here's how I'd start: 1. Find 5 small agencies. Offer to review a batch of their notes for them. 2. Run the notes through Gemma locally (free, private, no cloud). Read every output yourself. 3. Write down the 20 issues that keep showing up: missing vitals, vague med changes, notes that don't support the billed level. 4. That list of 20 is your checklist. The checklist is the product. 5. Turn it into a local desktop app that flags those 20 things before a note gets submitted. You just went from a service anyone could offer to a product nobody else has, and you learned exactly what to build by doing the work by hand first. Same recipe works for restoration contractors (draft the damage report on-site before the tech leaves) and wealth advisors (catch the compliance landmine in a client email before it sends). Basically the framework is sensitive data, repeated review, ancient software. I think there are tons of businesses like this! Almost none of it clicked for me until I actually started using local AI. So if you take one thing from this, go run a model on your own machine once. Also a fun thing to try with your friends. Feel free to send this to a friend. The episode is live for free on The Startup Ideas Podcast (SIP) 🧃 (thanks to Google for sponsoring today's episode and supporting local AI) I feel like local AI one of those things you need to try for it to really click. Run one model on your own machine and you'll see what I mean! I go way deeper in the full 38 minute masterclass, the models, the setup, and the businesses to build. Link below. LINK TO WATCH: OR WATCH BELOW ON X What do you think of local AI?

GREG ISENBERG

33,698 Aufrufe • vor 1 Monat

🇺🇸 UFO CLOSE CALL? PILOT REPORTS “SILVER CANISTER” FLOATING NEAR PLANE A pilot flying over Rhode Island called air traffic control with the kind of report that instantly turns a normal day into a group chat story. He said a mysterious object, shaped like a “small silver canister,” was hovering just feet from his wingtip at around 3,500 feet and “appears to be standing still.” The controllers asked for more detail, but the pilot said it did not look like a drone or a balloon and did not seem attached to anything, it was just “hovering” there on its own. They sounded as baffled as anyone, with one voice calling it “Creepy!” before another added the line every pilot dreams of hearing midair: “Good luck with the aliens!” No official explanation is given in the report, and the FAA did not immediately comment. So what was it: a super-close drone, a floating science project, or the world’s most awkward fly-by? Source: VASAviation, New York Post
1:40

🇺🇸 UFO CLOSE CALL? PILOT REPORTS “SILVER CANISTER” FLOATING NEAR PLANE A pilot flying over Rhode Island called air traffic control with the kind of report that instantly turns a normal day into a group chat story. He said a mysterious object, shaped like a “small silver canister,” was hovering just feet from his wingtip at around 3,500 feet and “appears to be standing still.” The controllers asked for more detail, but the pilot said it did not look like a drone or a balloon and did not seem attached to anything, it was just “hovering” there on its own. They sounded as baffled as anyone, with one voice calling it “Creepy!” before another added the line every pilot dreams of hearing midair: “Good luck with the aliens!” No official explanation is given in the report, and the FAA did not immediately comment. So what was it: a super-close drone, a floating science project, or the world’s most awkward fly-by? Source: VASAviation, New York Post

Mario Nawfal

75,830 Aufrufe • vor 9 Monaten

Sam Altman just told you what OpenAI is actually building. Not a chatbot. Not a search tool. Not an assistant. Altman: “Go look around my computer… read my messages… listen to my meetings… intermediate my interactions for me.” That is not a product pitch. That is the CEO of the most valuable AI company on Earth describing what he personally wants. For himself. Every day. Read his messages. Listen to his meetings. Act on his behalf. Make decisions before he knows a decision needs making. Altman: “I don’t have to think. I don’t have to ask you questions.” Every model of AI ever built runs on the prompt. You ask. It responds. You direct. It executes. The human initiates. The machine follows. Altman is describing the death of that model. The agent does not wait. It already read the email. It already heard the meeting. It already knows what you need before you form the thought. You do not operate the machine. The machine operates around you. Then came the line that makes everything else real. Altman: “You can know everything about my life. Start suggesting more things I should build.” He is not asking the AI to execute his ideas. He is asking it to generate them. From his files. His history. His patterns. His entire context. The agent does not just remove friction. It removes the blank page. You never stall. You never run dry. You never sit wondering what to build next. The machine already mapped your market, your gaps, your momentum. It tells you what comes next before you think to ask. But the individual product is not the story. Altman went further. Altman: “Automated companies… where the AI can do not just coding work, but huge amounts of what it takes to run and operate a company.” Not fully automated. He was precise about that. But accelerated to the point where one person with the right stack does what used to take departments. The billion-dollar company did not reach that valuation because the product was worth a billion. It got there because it took a thousand people to deliver it. When an agent absorbs the work of a hundred of those people, the math of every industry rewrites itself. The startup that needed fifty employees and three years of runway now needs five people and six months. The company that took a decade to scale now compounds in quarters. The person holding the line between their data and their tools is not protecting their privacy. They are protecting their ceiling. Because the cost of this leverage is total transparency. You do not get the agent that acts without being asked unless you give it everything. Your messages. Your calendar. Your files. Your patterns. Your life. Altman is not hiding that tradeoff. He is building it as the product. The people who accept it will operate at a speed the people who refuse cannot touch. Right now, two versions of the future are separating. One where you direct the machine. One where the machine already knows. Altman chose. He is building it. The question is not whether this happens. The question is which side of it finds you.
1:40

Sam Altman just told you what OpenAI is actually building. Not a chatbot. Not a search tool. Not an assistant. Altman: “Go look around my computer… read my messages… listen to my meetings… intermediate my interactions for me.” That is not a product pitch. That is the CEO of the most valuable AI company on Earth describing what he personally wants. For himself. Every day. Read his messages. Listen to his meetings. Act on his behalf. Make decisions before he knows a decision needs making. Altman: “I don’t have to think. I don’t have to ask you questions.” Every model of AI ever built runs on the prompt. You ask. It responds. You direct. It executes. The human initiates. The machine follows. Altman is describing the death of that model. The agent does not wait. It already read the email. It already heard the meeting. It already knows what you need before you form the thought. You do not operate the machine. The machine operates around you. Then came the line that makes everything else real. Altman: “You can know everything about my life. Start suggesting more things I should build.” He is not asking the AI to execute his ideas. He is asking it to generate them. From his files. His history. His patterns. His entire context. The agent does not just remove friction. It removes the blank page. You never stall. You never run dry. You never sit wondering what to build next. The machine already mapped your market, your gaps, your momentum. It tells you what comes next before you think to ask. But the individual product is not the story. Altman went further. Altman: “Automated companies… where the AI can do not just coding work, but huge amounts of what it takes to run and operate a company.” Not fully automated. He was precise about that. But accelerated to the point where one person with the right stack does what used to take departments. The billion-dollar company did not reach that valuation because the product was worth a billion. It got there because it took a thousand people to deliver it. When an agent absorbs the work of a hundred of those people, the math of every industry rewrites itself. The startup that needed fifty employees and three years of runway now needs five people and six months. The company that took a decade to scale now compounds in quarters. The person holding the line between their data and their tools is not protecting their privacy. They are protecting their ceiling. Because the cost of this leverage is total transparency. You do not get the agent that acts without being asked unless you give it everything. Your messages. Your calendar. Your files. Your patterns. Your life. Altman is not hiding that tradeoff. He is building it as the product. The people who accept it will operate at a speed the people who refuse cannot touch. Right now, two versions of the future are separating. One where you direct the machine. One where the machine already knows. Altman chose. He is building it. The question is not whether this happens. The question is which side of it finds you.

Dustin

87,680 Aufrufe • vor 6 Monaten

HERE BE TEN FACTS: 1. This is not an ad. 2. I am not being paid for this not-ad. 3. This not-ad will play on the next WEAPONIZED (as far as i know). 4. The next WEAPONIZED will feature CDR David Fravor (i believe). 5. I bought two flying saucers - that desire teeth. 6. One is for a friend’s daughter. 7. There WILL be a Congressional hearing on UFOs / 13 NOV 2024 (from what I know at this time) “Come hell or high water”. 8. On 13 NOV 2024 [or before] YOU WILL KNOW MORE about UFOs/UAP, than you do today. 9. As of this moment - you can get a UFO that desires teeth too… here : GO GO UFO - TRANSPARENCY 🛸 BTW - I want to find the ACTUAL artist of this UFO design. Hit me up at Editor@ExtraordinaryBeliefs.com if you are THE artist - as long as you are not A.I. 🤖 You’ve now done been told. If you are confused - you need to listen to hear. Enjoy! 🧨👊🏼👀🥋🪖🦅🪐🛸🇺🇸 Good night, and good luck.
9:06

HERE BE TEN FACTS: 1. This is not an ad. 2. I am not being paid for this not-ad. 3. This not-ad will play on the next WEAPONIZED (as far as i know). 4. The next WEAPONIZED will feature CDR David Fravor (i believe). 5. I bought two flying saucers - that desire teeth. 6. One is for a friend’s daughter. 7. There WILL be a Congressional hearing on UFOs / 13 NOV 2024 (from what I know at this time) “Come hell or high water”. 8. On 13 NOV 2024 [or before] YOU WILL KNOW MORE about UFOs/UAP, than you do today. 9. As of this moment - you can get a UFO that desires teeth too… here : GO GO UFO - TRANSPARENCY 🛸 BTW - I want to find the ACTUAL artist of this UFO design. Hit me up at [email protected] if you are THE artist - as long as you are not A.I. 🤖 You’ve now done been told. If you are confused - you need to listen to hear. Enjoy! 🧨👊🏼👀🥋🪖🦅🪐🛸🇺🇸 Good night, and good luck.

Jeremy Kenyon Lockyer Corbell

50,027 Aufrufe • vor 1 Jahr

The UFOs were here again tonight! I was out there with them and just came back in. Something is going on! They’re going to do another big event soon, or something big is about to happen in the world! This isn’t normal—they normally don't come this many times so close together. There were so many tonight I couldn’t count them all! I’ll show everyone what they look like at a distance with the plasma field off. I have them on other cameras doing this too, but the color Starlight camera shows it best. They blink really fast when in large groups like tonight. I don't know if they do that to try and mimic aircraft or why they do it. I see them very closeup here and they are nothing like an aircraft! I use radar apps and satellite tracking apps so I know what everything is flying all around this area. I have been doing this since 2005. I also track the military aircraft that don't show up on radar and I have cameras that can zoom in on them miles away. The UFOs are blinking way faster than any aircraft navigation lights blink when the plasma field is not glowing. They don't blink like this all the time when the plasma is not glowing. They do it many times when in the larger groups for some reason. Some also turned their plasma fields on. Two C-17s and a C-130 flew over on a training mission shortly before the UFOs appeared and were still in the area, so there’s a good chance some USAF pilots saw them tonight. Some of the SOLL pilots have seen them here before over the years when the UFOs jump in behind or above them or near them. They never harm the aircraft. We’ve seen them approach SOLL aircraft many times over the years when the aircraft fly over at tree top level training here and they cause no harm to them. I have the UFOs with the SOLL aircraft on videos together. They just let them know they are here. One of the sphere UFO appeared right in front of a Life Star helicopter beside our house also; the pilot saw it, pulled back, and the UFO instantly jumped away without touching the helicopter or harming it. The small lights higher up crossing the sky are Starlink satellites and there are a few aircraft crossing higher up. The UFOs are all the reddish orange lights blinking fast near the tree line and you can see some of them light the plasma field up. One of the UFOs fly's in a circle pattern while the plasma is lit up.
4:09

The UFOs were here again tonight! I was out there with them and just came back in. Something is going on! They’re going to do another big event soon, or something big is about to happen in the world! This isn’t normal—they normally don't come this many times so close together. There were so many tonight I couldn’t count them all! I’ll show everyone what they look like at a distance with the plasma field off. I have them on other cameras doing this too, but the color Starlight camera shows it best. They blink really fast when in large groups like tonight. I don't know if they do that to try and mimic aircraft or why they do it. I see them very closeup here and they are nothing like an aircraft! I use radar apps and satellite tracking apps so I know what everything is flying all around this area. I have been doing this since 2005. I also track the military aircraft that don't show up on radar and I have cameras that can zoom in on them miles away. The UFOs are blinking way faster than any aircraft navigation lights blink when the plasma field is not glowing. They don't blink like this all the time when the plasma is not glowing. They do it many times when in the larger groups for some reason. Some also turned their plasma fields on. Two C-17s and a C-130 flew over on a training mission shortly before the UFOs appeared and were still in the area, so there’s a good chance some USAF pilots saw them tonight. Some of the SOLL pilots have seen them here before over the years when the UFOs jump in behind or above them or near them. They never harm the aircraft. We’ve seen them approach SOLL aircraft many times over the years when the aircraft fly over at tree top level training here and they cause no harm to them. I have the UFOs with the SOLL aircraft on videos together. They just let them know they are here. One of the sphere UFO appeared right in front of a Life Star helicopter beside our house also; the pilot saw it, pulled back, and the UFO instantly jumped away without touching the helicopter or harming it. The small lights higher up crossing the sky are Starlink satellites and there are a few aircraft crossing higher up. The UFOs are all the reddish orange lights blinking fast near the tree line and you can see some of them light the plasma field up. One of the UFOs fly's in a circle pattern while the plasma is lit up.

Ranger H

17,563 Aufrufe • vor 10 Monaten

🔥 BIG REVEAL | METAL RAMPAGE - FIRST COMBATANTS DEPLOYED 🔥 The engines are online. The wasteland is waking up. And the first machines of destruction have entered the arena. Before the executioners. Before the poisoners. There were the pioneers. Two vehicles built to survive the impossible. Two legends that shaped the battlefield. ⚡ Pulsar The Untouchable Transporter 🛞 When the mission is suicidal, when the cargo must arrive no matter the cost, there’s only one name the underground trusts. Pulsar. This high-performance sports machine wasn’t built for chaos. It was built to outsmart it. Lightweight. Surgical. Precise. While others smash their way through combat, Pulsar slips between bullets, traps, and explosions like a ghost at full throttle. Speed is its armor. Control is its weapon. Its signature ability, Shockwave, releases a kinetic burst that repels nearby threats, clearing space and punishing anyone who dares get too close. No collisions. No scratches. No mistakes. Pulsar doesn’t fight the battlefield. It escapes it. And still wins. ❄️ Ice Scream The Frozen Executioner ☢️ At first, you hear the music. A distorted jingle. Slow. Broken. Wrong. Then the temperature drops. Ice Scream is a relic of the old world, a ruined ice cream truck reborn as a cryogenic war machine, dragging death behind it like frostbite. Beneath its rusted shell lies an experimental freezing core capable of locking entire zones in sub-zero terror. Where it drives, engines stall. Armor cracks. Movement stops. Its special ability, Deep Freeze, unleashes a devastating cryo blast that immobilizes enemies in range, turning fast fights into helpless executions. It doesn’t chase. It traps. It doesn’t destroy fast. It freezes everything… then finishes the job. Ice Scream doesn’t bring treats. It delivers winter. Permanent winter. 🚨 METAL RAMPAGE IS COMING 🚨 Pulsar runs the cargo. Ice Scream controls the field. Reaper executes. Widowmaker corrupts. Different roles. Different strategies. One battlefield. Metal Rampage isn’t just vehicular combat. It’s tactical warfare on wheels. 🗓 Launch next month ⚙️ More combatants incoming 🔥 The rampage begins soon Choose your machine. Claim your role. Dominate the wasteland. $NAKA #MetalRampage #BUIDL
0:54

🔥 BIG REVEAL | METAL RAMPAGE - FIRST COMBATANTS DEPLOYED 🔥 The engines are online. The wasteland is waking up. And the first machines of destruction have entered the arena. Before the executioners. Before the poisoners. There were the pioneers. Two vehicles built to survive the impossible. Two legends that shaped the battlefield. ⚡ Pulsar The Untouchable Transporter 🛞 When the mission is suicidal, when the cargo must arrive no matter the cost, there’s only one name the underground trusts. Pulsar. This high-performance sports machine wasn’t built for chaos. It was built to outsmart it. Lightweight. Surgical. Precise. While others smash their way through combat, Pulsar slips between bullets, traps, and explosions like a ghost at full throttle. Speed is its armor. Control is its weapon. Its signature ability, Shockwave, releases a kinetic burst that repels nearby threats, clearing space and punishing anyone who dares get too close. No collisions. No scratches. No mistakes. Pulsar doesn’t fight the battlefield. It escapes it. And still wins. ❄️ Ice Scream The Frozen Executioner ☢️ At first, you hear the music. A distorted jingle. Slow. Broken. Wrong. Then the temperature drops. Ice Scream is a relic of the old world, a ruined ice cream truck reborn as a cryogenic war machine, dragging death behind it like frostbite. Beneath its rusted shell lies an experimental freezing core capable of locking entire zones in sub-zero terror. Where it drives, engines stall. Armor cracks. Movement stops. Its special ability, Deep Freeze, unleashes a devastating cryo blast that immobilizes enemies in range, turning fast fights into helpless executions. It doesn’t chase. It traps. It doesn’t destroy fast. It freezes everything… then finishes the job. Ice Scream doesn’t bring treats. It delivers winter. Permanent winter. 🚨 METAL RAMPAGE IS COMING 🚨 Pulsar runs the cargo. Ice Scream controls the field. Reaper executes. Widowmaker corrupts. Different roles. Different strategies. One battlefield. Metal Rampage isn’t just vehicular combat. It’s tactical warfare on wheels. 🗓 Launch next month ⚙️ More combatants incoming 🔥 The rampage begins soon Choose your machine. Claim your role. Dominate the wasteland. $NAKA #MetalRampage #BUIDL

Nakamoto.Games

11,060 Aufrufe • vor 8 Monaten

//The Wire//2300Z February 5, 2026// //ROUTINE// //BLUF: ARIZONA POLICE HELICOPTER CRASHES DURING SMALL ARMS ENGAGEMENT IN FLAGSTAFF. MORE DETAILS EMERGE REGARDING CHINESE BIOLAB IN VEGAS.// -----BEGIN TEARLINE----- -HomeFront- Nevada: More details have come to light regarding the Chinese Biolab discovered in Las Vegas a few days ago. After the story became public, several eyewitnesses have come forward to local media groups, with additional testimony that provides more context. One of the housekeepers that serviced the Vegas residence where the biolab was discovered had actually previously reported the facility to the FBI on January 9, 2026. Per this testimony, herself and several other cleaning staff members became severely ill after working in the residence back in April of 2025. Analyst Comment: Eyewitness testimony must always be considered with a grain of salt, however if this report is accurate, the FBI would have been aware of this facility (and the fact that random people were being infected by whatever biological materials were there), for much longer than they let on. Arizona: Early this morning, a downed-aircraft incident was reported as one Arizona DPS helicopter crashed in the vicinity of a an active shooter situation. The incident began as officers responded to call of domestic violence on W Shellie Drive at approximately 08:31 pm last night. As officers arrived on scene, the suspect engaged the officers with small arms fire, which kicked off a protracted small arms firefight that continued over the next two hours. During this time, the suspect fired upon officers from multiple rooftops throughout the area, maneuvering between multiple positions throughout the engagement. Approximately two hours into the firefight, an Arizona DPS helicopter (Registration: N56AZ, Callsign: RANGER 56) arrived on scene to assist officers on the ground in understanding where the suspect was hiding. Shortly after the helicopter arrived on scene, the aircraft crashed in the elevated terrain a short distance from the initial reported shooting location. Both the pilot and the onboard paramedic were killed in the crash. The initial suspect that began the engagement was arrested at almost the same time as the crash, and has been hospitalized with non-life threatening small arms wounds. -----END TEARLINE----- Analyst Comments: So far, official statements by the Arizona Department of Public Safety don't confirm exactly what happened regarding the helicopter crash in Flagstaff last night. No answers were provided during this morning's press conference, nor was any causal link mentioned between the engagement on the ground, and the helicopter crash. Since the crash itself was catastrophic, it will take some time for an investigation to determine if any small arms rounds struck the helicopter or not. It would not be the first time that hardened criminals, when backed into a corner, fired off a burst of small arms fire at a police helicopter, which resulted in catastrophe. Considering the detail of the suspect being located on rooftops during this engagement, this is the most likely theory at the moment. Otherwise, there is not much information in the public realm to state with confidence that this is exactly what happened. The ADS-B feed of the flight path does not provide much context, other than one detail which might be useful for investigators. As the aircraft arrived on scene, the pilot began a low-pass flyover of the target compound, directly over the residence that the shooting was reported at. After this low-pass over the target compound, the aircraft was observed climbing out to the north and west, before flying in an erratic manner. Locals reported hearing many gunshots and explosions in the general direction of this residence, shortly before the helicopter was observed crashing. Immediately before impact, the ADS-B feed for the aircraft abruptly halts, indicating that the aircraft at least partially broke apart before impacting the ground. From the time of the low-pass (where small arms fire may have damaged the aircraft), to the very last transponder ping, approximately 10 minutes had elapsed. This is enough time for a mayday call to be made over the radio, if the crew noticed that they might have taken effective ground fire. As such, the flight data recorder information for this period of time will be crucial for determining the cause of the crash. However, due to the strategic implication of an aircraft possibly being shot down by small arms fire, it would be prudent to consider this a possible SAFIRE (Surface-to-Air Fire) incident at the present time. Analyst: S2A1 Research: Disclaimer: No LLMs were used in the writing of this report. //END REPORT//
4:01

//The Wire//2300Z February 5, 2026// //ROUTINE// //BLUF: ARIZONA POLICE HELICOPTER CRASHES DURING SMALL ARMS ENGAGEMENT IN FLAGSTAFF. MORE DETAILS EMERGE REGARDING CHINESE BIOLAB IN VEGAS.// -----BEGIN TEARLINE----- -HomeFront- Nevada: More details have come to light regarding the Chinese Biolab discovered in Las Vegas a few days ago. After the story became public, several eyewitnesses have come forward to local media groups, with additional testimony that provides more context. One of the housekeepers that serviced the Vegas residence where the biolab was discovered had actually previously reported the facility to the FBI on January 9, 2026. Per this testimony, herself and several other cleaning staff members became severely ill after working in the residence back in April of 2025. Analyst Comment: Eyewitness testimony must always be considered with a grain of salt, however if this report is accurate, the FBI would have been aware of this facility (and the fact that random people were being infected by whatever biological materials were there), for much longer than they let on. Arizona: Early this morning, a downed-aircraft incident was reported as one Arizona DPS helicopter crashed in the vicinity of a an active shooter situation. The incident began as officers responded to call of domestic violence on W Shellie Drive at approximately 08:31 pm last night. As officers arrived on scene, the suspect engaged the officers with small arms fire, which kicked off a protracted small arms firefight that continued over the next two hours. During this time, the suspect fired upon officers from multiple rooftops throughout the area, maneuvering between multiple positions throughout the engagement. Approximately two hours into the firefight, an Arizona DPS helicopter (Registration: N56AZ, Callsign: RANGER 56) arrived on scene to assist officers on the ground in understanding where the suspect was hiding. Shortly after the helicopter arrived on scene, the aircraft crashed in the elevated terrain a short distance from the initial reported shooting location. Both the pilot and the onboard paramedic were killed in the crash. The initial suspect that began the engagement was arrested at almost the same time as the crash, and has been hospitalized with non-life threatening small arms wounds. -----END TEARLINE----- Analyst Comments: So far, official statements by the Arizona Department of Public Safety don't confirm exactly what happened regarding the helicopter crash in Flagstaff last night. No answers were provided during this morning's press conference, nor was any causal link mentioned between the engagement on the ground, and the helicopter crash. Since the crash itself was catastrophic, it will take some time for an investigation to determine if any small arms rounds struck the helicopter or not. It would not be the first time that hardened criminals, when backed into a corner, fired off a burst of small arms fire at a police helicopter, which resulted in catastrophe. Considering the detail of the suspect being located on rooftops during this engagement, this is the most likely theory at the moment. Otherwise, there is not much information in the public realm to state with confidence that this is exactly what happened. The ADS-B feed of the flight path does not provide much context, other than one detail which might be useful for investigators. As the aircraft arrived on scene, the pilot began a low-pass flyover of the target compound, directly over the residence that the shooting was reported at. After this low-pass over the target compound, the aircraft was observed climbing out to the north and west, before flying in an erratic manner. Locals reported hearing many gunshots and explosions in the general direction of this residence, shortly before the helicopter was observed crashing. Immediately before impact, the ADS-B feed for the aircraft abruptly halts, indicating that the aircraft at least partially broke apart before impacting the ground. From the time of the low-pass (where small arms fire may have damaged the aircraft), to the very last transponder ping, approximately 10 minutes had elapsed. This is enough time for a mayday call to be made over the radio, if the crew noticed that they might have taken effective ground fire. As such, the flight data recorder information for this period of time will be crucial for determining the cause of the crash. However, due to the strategic implication of an aircraft possibly being shot down by small arms fire, it would be prudent to consider this a possible SAFIRE (Surface-to-Air Fire) incident at the present time. Analyst: S2A1 Research: Disclaimer: No LLMs were used in the writing of this report. //END REPORT//

S2 Underground

11,259 Aufrufe • vor 8 Monaten

🚨BOMBSHELL: Another SPY Plane Caught Overhead EXACTLY When Tyler Robinson Turned Himself In —Was Tyler Robinson "Processed" by MILITARY Intelligence?!😱 If you thought the AXEL 10 spy plane over UVU was a "coincidence," wait until you see what Baron Coleman just uncovered about the day Tyler Robinson turned himself in. There is a second "spy plane" and its flight path should terrify anyone who still believes the official narrative. 🛩️ MEET AXEL 21: THE BROTHER PLANE On September 11th, 2025—the exact day Tyler Robinson surrendered in St. George, Utah—another high-altitude spy plane from the US Army’s HADES program was in the air. The Flight: AXEL 21 (a different tail number, but the same elite sensor suite) left Ontario, CA, headed for El Paso, TX. The Detour: Instead of flying a straight line, this plane flew Northwest, directly into Utah airspace. The "Stall Speed" Pass: Just like AXEL 10 did over the Charlie Kirk assassination site, AXEL 21 dropped its altitude and slowed down to a mere 126 knots—nearly stall speed for a jet of this caliber—directly over St. George. 🕵️‍♂️ WHY ST. GEORGE? WHY THEN? This plane didn't show up on local landing schemes because it wasn't "supposed" to be there. The Timing: It arrived on the scene around 2:35 Zulu and circled for 45 minutes. * The Mission: This happened exactly as Tyler Robinson was turning himself in at the Washington County Sheriff's Office. The Capability: This isn't just a plane. The HADES program utilizes Rapcon X AI-driven systems and ASARS-2B radar. It can deploy drones, read encrypted communications in real-time, and track mobile targets with terrifying precision. 👁️ "DID WE PULL IT OFF?" Baron Coleman asks the question the FBI doesn't want to answer: Why was one of the most sophisticated pieces of intelligence-gathering machinery in the world hovering over a peaceful surrender? Was the Army using the AXEL 21 sensor suite to ensure their "Patsy" was successfully in custody? Were they monitoring the ground to make sure no "unauthorized" witnesses were present? "Did we pull it off? ... That machine decided to fly over Tyler Robinson turning himself in... I think the timing is important." — Baron Coleman 🧩 THE PATTERN IS CLEAR Sept 10th: AXEL 10 flies "low and slow" over UVU during the assassination. Sept 11th: AXEL 21 flies "low and slow" over St. George during the surrender. This is Multi-Domain Operations happening on American soil, targeting American citizens. The "HADES" program was designed for deep sensing in war zones—so why is it being used as a tactical overhead for the Charlie Kirk investigation? Is Tyler Robinson really the assassin, or was he tracked, monitored, and "processed" and set up by a high-level military intelligence operation? Let’s get the truth trending. 👇 FOLLOW Baron Coleman and be sure to watch his FULL episode linked below. 👇
5:30

🚨BOMBSHELL: Another SPY Plane Caught Overhead EXACTLY When Tyler Robinson Turned Himself In —Was Tyler Robinson "Processed" by MILITARY Intelligence?!😱 If you thought the AXEL 10 spy plane over UVU was a "coincidence," wait until you see what Baron Coleman just uncovered about the day Tyler Robinson turned himself in. There is a second "spy plane" and its flight path should terrify anyone who still believes the official narrative. 🛩️ MEET AXEL 21: THE BROTHER PLANE On September 11th, 2025—the exact day Tyler Robinson surrendered in St. George, Utah—another high-altitude spy plane from the US Army’s HADES program was in the air. The Flight: AXEL 21 (a different tail number, but the same elite sensor suite) left Ontario, CA, headed for El Paso, TX. The Detour: Instead of flying a straight line, this plane flew Northwest, directly into Utah airspace. The "Stall Speed" Pass: Just like AXEL 10 did over the Charlie Kirk assassination site, AXEL 21 dropped its altitude and slowed down to a mere 126 knots—nearly stall speed for a jet of this caliber—directly over St. George. 🕵️‍♂️ WHY ST. GEORGE? WHY THEN? This plane didn't show up on local landing schemes because it wasn't "supposed" to be there. The Timing: It arrived on the scene around 2:35 Zulu and circled for 45 minutes. * The Mission: This happened exactly as Tyler Robinson was turning himself in at the Washington County Sheriff's Office. The Capability: This isn't just a plane. The HADES program utilizes Rapcon X AI-driven systems and ASARS-2B radar. It can deploy drones, read encrypted communications in real-time, and track mobile targets with terrifying precision. 👁️ "DID WE PULL IT OFF?" Baron Coleman asks the question the FBI doesn't want to answer: Why was one of the most sophisticated pieces of intelligence-gathering machinery in the world hovering over a peaceful surrender? Was the Army using the AXEL 21 sensor suite to ensure their "Patsy" was successfully in custody? Were they monitoring the ground to make sure no "unauthorized" witnesses were present? "Did we pull it off? ... That machine decided to fly over Tyler Robinson turning himself in... I think the timing is important." — Baron Coleman 🧩 THE PATTERN IS CLEAR Sept 10th: AXEL 10 flies "low and slow" over UVU during the assassination. Sept 11th: AXEL 21 flies "low and slow" over St. George during the surrender. This is Multi-Domain Operations happening on American soil, targeting American citizens. The "HADES" program was designed for deep sensing in war zones—so why is it being used as a tactical overhead for the Charlie Kirk investigation? Is Tyler Robinson really the assassin, or was he tracked, monitored, and "processed" and set up by a high-level military intelligence operation? Let’s get the truth trending. 👇 FOLLOW Baron Coleman and be sure to watch his FULL episode linked below. 👇

Project Constitution

103,902 Aufrufe • vor 6 Monaten

JUST IN: A drone just hit a fuel tank at the busiest airport in the Middle East. The Dubai Media Office confirmed it 23 minutes ago. “A drone incident in the vicinity of Dubai International Airport (DXB) affected one of the fuel tanks. Dubai Civil Defence teams are currently working to bring the fire under control. No injuries have been reported so far.” That is the official statement from Dubai Media Office, posted in English and Arabic, with thousands of views in the first half hour. The fuel tank is burning. Civil Defence is on scene. The airport that processed 87 million passengers last year, the global hub that connects 260 destinations across six continents, the physical embodiment of everything Dubai built over three decades, has a fuel tank on fire because a drone that costs less than a business-class seat through Terminal 3 reached the aviation fuel supply that keeps the hub operational. This is the third confirmed drone incident at or near DXB since the war began. On 11 March, two drones struck near the airport, injuring four people. On 1 March, drones hit AWS data centres in the same corridor. Today, the target was not a server farm or a residential tower. It was aviation fuel. The escalation is vertical: from data to shelter to the liquid that makes the airport function. Fuel tanks at international airports are not incidental targets. They are the circulatory system of aviation. DXB operates on jet fuel stored in tank farms adjacent to the runways. A sustained fire in a fuel tank does not merely delay flights. It grounds the refuelling infrastructure that determines whether aircraft depart at all. Civil Defence is containing this fire. The question is not whether this fire is contained. The question is whether the next drone reaches the next tank, and whether the insurance market, the airline route planners, and the 87 million annual passengers calculate that a 94% interception rate over an airport fuel farm is sufficient assurance to book the ticket. The cumulative toll on the UAE since 28 February: 294 ballistic missiles, 15 cruise missiles, over 1,600 drones. Six dead. 141 injured. AWS data centres struck. Creek Harbour and 23 Marina towers burning from debris. The Burj Al Arab facade hit. Jebel Ali Port targeted. Fujairah oil zone fires. The Iranian Hospital closed. Five schools shuttered. Twenty-one people charged for filming. And now a fuel tank at the airport that defines the city burning while Civil Defence teams work to contain what the air defence system intercepted everywhere except here. The $600 million daily regional tourism loss was calculated before a fuel tank at DXB caught fire. The DFM Real Estate Index was down 21.4% before a fuel tank at DXB caught fire. The $20 billion DFC insurance facility had zero confirmed takers before a fuel tank at DXB caught fire. Every metric of economic damage that existed this morning is now being recalculated against a new data point: the airport itself is no longer outside the target set. Dubai built the busiest airport in the Middle East to prove the Gulf was open for business. Iran just proved it is open for drones. The fuel tank is burning. Civil Defence is responding. No injuries reported. And somewhere in the Gulf, a Shahed that cost $20,000 to $35,000 just imposed a repricing event on an aviation hub worth hundreds of billions by reaching the one target that converts a “drone incident” from a security event into an infrastructure crisis: the fuel that keeps the planes flying. Full analysis!
0:20

JUST IN: A drone just hit a fuel tank at the busiest airport in the Middle East. The Dubai Media Office confirmed it 23 minutes ago. “A drone incident in the vicinity of Dubai International Airport (DXB) affected one of the fuel tanks. Dubai Civil Defence teams are currently working to bring the fire under control. No injuries have been reported so far.” That is the official statement from Dubai Media Office, posted in English and Arabic, with thousands of views in the first half hour. The fuel tank is burning. Civil Defence is on scene. The airport that processed 87 million passengers last year, the global hub that connects 260 destinations across six continents, the physical embodiment of everything Dubai built over three decades, has a fuel tank on fire because a drone that costs less than a business-class seat through Terminal 3 reached the aviation fuel supply that keeps the hub operational. This is the third confirmed drone incident at or near DXB since the war began. On 11 March, two drones struck near the airport, injuring four people. On 1 March, drones hit AWS data centres in the same corridor. Today, the target was not a server farm or a residential tower. It was aviation fuel. The escalation is vertical: from data to shelter to the liquid that makes the airport function. Fuel tanks at international airports are not incidental targets. They are the circulatory system of aviation. DXB operates on jet fuel stored in tank farms adjacent to the runways. A sustained fire in a fuel tank does not merely delay flights. It grounds the refuelling infrastructure that determines whether aircraft depart at all. Civil Defence is containing this fire. The question is not whether this fire is contained. The question is whether the next drone reaches the next tank, and whether the insurance market, the airline route planners, and the 87 million annual passengers calculate that a 94% interception rate over an airport fuel farm is sufficient assurance to book the ticket. The cumulative toll on the UAE since 28 February: 294 ballistic missiles, 15 cruise missiles, over 1,600 drones. Six dead. 141 injured. AWS data centres struck. Creek Harbour and 23 Marina towers burning from debris. The Burj Al Arab facade hit. Jebel Ali Port targeted. Fujairah oil zone fires. The Iranian Hospital closed. Five schools shuttered. Twenty-one people charged for filming. And now a fuel tank at the airport that defines the city burning while Civil Defence teams work to contain what the air defence system intercepted everywhere except here. The $600 million daily regional tourism loss was calculated before a fuel tank at DXB caught fire. The DFM Real Estate Index was down 21.4% before a fuel tank at DXB caught fire. The $20 billion DFC insurance facility had zero confirmed takers before a fuel tank at DXB caught fire. Every metric of economic damage that existed this morning is now being recalculated against a new data point: the airport itself is no longer outside the target set. Dubai built the busiest airport in the Middle East to prove the Gulf was open for business. Iran just proved it is open for drones. The fuel tank is burning. Civil Defence is responding. No injuries reported. And somewhere in the Gulf, a Shahed that cost $20,000 to $35,000 just imposed a repricing event on an aviation hub worth hundreds of billions by reaching the one target that converts a “drone incident” from a security event into an infrastructure crisis: the fuel that keeps the planes flying. Full analysis!

Shanaka Anslem Perera ⚡

1,101,554 Aufrufe • vor 7 Monaten

A Stanford statistician built a dice-rolling machine to prove board game companies have been selling you loaded dice for a hundred years. The machine drops dice inside a glass chamber, records every landing, and runs the sequences through statistical tests. Every mass-produced die it tested was biased. Every Monopoly die. Every Yahtzee cube. Every D&D twenty-sider. Every casino die below one hundred dollars. The bias is so small the human eye cannot see it in one game. It is so consistent it drains a player over a night at a real table. His name is Persi Diaconis. He is 79. He ran away from home at fourteen to learn card magic from Dai Vernon. He came back twenty years later with a PhD in statistics from Harvard and became the person casinos, magicians, and mathematicians all quietly consult when they need to know how something actually shuffles, rolls, or falls. This eight-minute Numberphile clip is Diaconis explaining exactly what the machine found. The dots on a die are drilled holes. The paint filling them weighs less than the plastic that was removed. The six face is lighter than the one face. Every die you have ever owned has been tilted by a fraction of a gram since the day it left the factory. Casinos already knew. A single die at the Bellagio costs one hundred and fifty dollars, is discarded after eight hours of use, and is engineered so the paint in the pits weighs exactly what the plastic did. That is the whole difference between a game piece and a regulated instrument. Here is what Diaconis proved on the record. A cheap six-sided die favors the six face over thousands of rolls. A plastic twenty-sided die can favor certain numbers by a substantial margin depending on how the corners are cut. A thirty-sided die, unless the internal geometry is spherical, rolls some faces two to three times more often than others. One retired executive rolled a single die three and a half million times before it physically wore round. Euclid worked out part of this in 300 BC. Diaconis has spent forty years finishing the rest. "There is no such thing as a fair die. There are only dice fair enough for the purpose you are using them for." Fairness is not a property of the die. It is a property of the die plus the throw plus the surface. Change any one and the same die stops being fair. The video is free. Diaconis's papers are free on his Stanford page. Everyone who has ever argued over a roll has been trusting a piece of plastic they never checked. The math is free. The willingness to admit your die is loaded is a much rarer commodity than fairness.
8:12

A Stanford statistician built a dice-rolling machine to prove board game companies have been selling you loaded dice for a hundred years. The machine drops dice inside a glass chamber, records every landing, and runs the sequences through statistical tests. Every mass-produced die it tested was biased. Every Monopoly die. Every Yahtzee cube. Every D&D twenty-sider. Every casino die below one hundred dollars. The bias is so small the human eye cannot see it in one game. It is so consistent it drains a player over a night at a real table. His name is Persi Diaconis. He is 79. He ran away from home at fourteen to learn card magic from Dai Vernon. He came back twenty years later with a PhD in statistics from Harvard and became the person casinos, magicians, and mathematicians all quietly consult when they need to know how something actually shuffles, rolls, or falls. This eight-minute Numberphile clip is Diaconis explaining exactly what the machine found. The dots on a die are drilled holes. The paint filling them weighs less than the plastic that was removed. The six face is lighter than the one face. Every die you have ever owned has been tilted by a fraction of a gram since the day it left the factory. Casinos already knew. A single die at the Bellagio costs one hundred and fifty dollars, is discarded after eight hours of use, and is engineered so the paint in the pits weighs exactly what the plastic did. That is the whole difference between a game piece and a regulated instrument. Here is what Diaconis proved on the record. A cheap six-sided die favors the six face over thousands of rolls. A plastic twenty-sided die can favor certain numbers by a substantial margin depending on how the corners are cut. A thirty-sided die, unless the internal geometry is spherical, rolls some faces two to three times more often than others. One retired executive rolled a single die three and a half million times before it physically wore round. Euclid worked out part of this in 300 BC. Diaconis has spent forty years finishing the rest. "There is no such thing as a fair die. There are only dice fair enough for the purpose you are using them for." Fairness is not a property of the die. It is a property of the die plus the throw plus the surface. Change any one and the same die stops being fair. The video is free. Diaconis's papers are free on his Stanford page. Everyone who has ever argued over a roll has been trusting a piece of plastic they never checked. The math is free. The willingness to admit your die is loaded is a much rarer commodity than fairness.

Flandermaxx

296,959 Aufrufe • vor 2 Monaten

Apparently, doing laundry is now an extreme sport. 🧺 Using Seedance 2.5 on Higgsfield Prompt : STYLE: Photorealistic live-action miniature-person FX, cinematic macro photography, ultra-shallow depth of field, realistic household environment, dynamic handheld camera, dramatic practical lighting, realistic physics, highly detailed textures, premium viral commercial aesthetic, 4K. Create a 30-second cinematic adventure featuring one athletic miniature woman at approximately 1 : 5 scale. Maintain her exact face, hairstyle, outfit, body proportions, shoes and scale consistently throughout. She begins inside a massive laundry room surrounded by enormous household objects. She sprints across a giant washing machine, jumping over spinning buttons and detergent bottles. A huge laundry basket tips over, sending socks and clothes tumbling across the floor like an avalanche. She runs across the moving pile, using a hanging shirt as a rope to swing toward a massive ironing board. She lands on the ironing board and races across its surface as a large iron slides toward her. She narrowly jumps over it and grabs a dangling power cord, swinging onto a towering detergent bottle. She climbs over the bottle cap and leaps onto a huge pile of folded towels. Suddenly, a washing machine door opens and a powerful burst of warm air sends several lightweight clothes flying around her. She grabs a towel, uses it like a parachute for a short controlled glide, and lands on a giant laundry hamper. She then rides a rolling laundry cart through the room, dodging falling clothes and spinning wheels before jumping onto a massive clothesline. She runs along the line toward a giant window and finally climbs onto the curtain rod, looking across the enormous laundry room as the camera pulls far backward to reveal just how tiny she really is. Use dynamic macro tracking, dramatic low angles, smooth aerial-style movements, strong foreground parallax, realistic reflections, shadows, depth of field, fabric physics, believable human movement, detailed household textures, seamless transitions and cinematic practical lighting. SFX: Footsteps, fabric movement, washing-machine hum, buttons clicking, detergent bottles rattling, clothes falling, metal impacts, cart wheels, air rushing, fabric flapping and cinematic impact sounds. NEGATIVE: Cartoon, anime, toy-like appearance, animation, plastic-looking miniature, duplicated character, face changes, outfit changes, distorted anatomy, floating objects, impossible physics, inconsistent scale, scale changes, teleportation, excessive motion blur, narration, subtitles, watermark.
0:30

Apparently, doing laundry is now an extreme sport. 🧺 Using Seedance 2.5 on Higgsfield Prompt : STYLE: Photorealistic live-action miniature-person FX, cinematic macro photography, ultra-shallow depth of field, realistic household environment, dynamic handheld camera, dramatic practical lighting, realistic physics, highly detailed textures, premium viral commercial aesthetic, 4K. Create a 30-second cinematic adventure featuring one athletic miniature woman at approximately 1 : 5 scale. Maintain her exact face, hairstyle, outfit, body proportions, shoes and scale consistently throughout. She begins inside a massive laundry room surrounded by enormous household objects. She sprints across a giant washing machine, jumping over spinning buttons and detergent bottles. A huge laundry basket tips over, sending socks and clothes tumbling across the floor like an avalanche. She runs across the moving pile, using a hanging shirt as a rope to swing toward a massive ironing board. She lands on the ironing board and races across its surface as a large iron slides toward her. She narrowly jumps over it and grabs a dangling power cord, swinging onto a towering detergent bottle. She climbs over the bottle cap and leaps onto a huge pile of folded towels. Suddenly, a washing machine door opens and a powerful burst of warm air sends several lightweight clothes flying around her. She grabs a towel, uses it like a parachute for a short controlled glide, and lands on a giant laundry hamper. She then rides a rolling laundry cart through the room, dodging falling clothes and spinning wheels before jumping onto a massive clothesline. She runs along the line toward a giant window and finally climbs onto the curtain rod, looking across the enormous laundry room as the camera pulls far backward to reveal just how tiny she really is. Use dynamic macro tracking, dramatic low angles, smooth aerial-style movements, strong foreground parallax, realistic reflections, shadows, depth of field, fabric physics, believable human movement, detailed household textures, seamless transitions and cinematic practical lighting. SFX: Footsteps, fabric movement, washing-machine hum, buttons clicking, detergent bottles rattling, clothes falling, metal impacts, cart wheels, air rushing, fabric flapping and cinematic impact sounds. NEGATIVE: Cartoon, anime, toy-like appearance, animation, plastic-looking miniature, duplicated character, face changes, outfit changes, distorted anatomy, floating objects, impossible physics, inconsistent scale, scale changes, teleportation, excessive motion blur, narration, subtitles, watermark.

Smiling Khan

33,667 Aufrufe • vor 5 Tagen

Mad Max Squad - Failed assault on a terrikon near the city of Horlivka, Donetsk region. December, 2023. 💬"We we waiting for our drone to check what’s up there. At that moment, over the radio comes this line - “conditions are favorable for an assault.” We approach the terrikon and the sapper spots a PMN-2 mine, marks it, and says the slopes of the terrikon are mined, watch your step. 0:10 Our formation: two sappers in front (by the way, they were unarmed), then the rest of us - 8 guys in two groups of four. We start climbing this terrikon, the ground crumbling under our boots. 0:15 Our machine gunner signals us to overtake him ’cause he’ll be slow going up. Two of our lads, Musician and Redhead, start scrambling up fast - we follow. We reach the top, and Musician peeks over to see what’s there. 0:21 That’s when contact kicks off - they start blasting, small arms and AGS from the neighboring heap. We return fire, chuck grenades into their trenches. This goes on for about 10 minutes, and then a grenade lands right in the core of our group. We go flying down the slope (you can see it in the video), and it explodes. 0:45 Group commander "Young" takes shrapnel to the head and side, deputy “Horse” gets hit in the ear. We get the order to pull back - we fall back in bounds, firing as we move, and Horse yells over the radio: “I’m 200! - oh wait, 300! 300!” We slide down the slope and spot the sappers - and man, they took off like Usain Bolt, no way in hell you’re catching them 🤣 (fair enough, they were unarmed). Two machine gunners and Redhead stay behind to cover. We pop smoke to blend into it, ’cause those bastards start hammering us from the hill. Then one of the guys pulls out a Matador and slams a shot into that terrikon. Redhead was bringing up the rear, and the two machine gunners were already pretty gassed, so they slowed to a walk. And then, from the side, from higher ground, a sniper starts cracking shots at us. Redhead yells to machine gunners: “Run, f**k, or I’ll drop you myself!” No second thoughts - Timon, the machine gunner, dumps his backpack (it had water and a 200-round belt; altogether he was carrying about 550 rounds on him!). That gave us a bit of a boost. We make it back to that patch of woods where we took a breather earlier - and there’s another group of 8 guys waiting. They were supposed to hit the position near the terrikon. They look at us - completely smoked, Young bleeding - and he goes: “Boys, now it’s your turn, go f***ing gas it” 🤣 We pulled back to our positions, and that group stayed, waiting for adjacent units to link up so they could go at the terrikon again. While they were waiting, the bastards remotely mined the approaches to the roads we used - dropped it from cluster munitions - and then artillery vacuumed the area for about 40 minutes. After that, they also pulled back. The point of this story is - some guys are ashamed to talk about failed ops. I remember the words of an Azov Brigade fighter, Hryan (Гряна). He dreamed of making it to Everest, but was killed in Mariupol. One of his last texts was: “Today, my Everest is here.” We didn’t manage to take that Everest… but there are still plenty of summits ahead." - Mad Max Squad. Russian drone POV in the comments.
1:14

Mad Max Squad - Failed assault on a terrikon near the city of Horlivka, Donetsk region. December, 2023. 💬"We we waiting for our drone to check what’s up there. At that moment, over the radio comes this line - “conditions are favorable for an assault.” We approach the terrikon and the sapper spots a PMN-2 mine, marks it, and says the slopes of the terrikon are mined, watch your step. 0:10 Our formation: two sappers in front (by the way, they were unarmed), then the rest of us - 8 guys in two groups of four. We start climbing this terrikon, the ground crumbling under our boots. 0:15 Our machine gunner signals us to overtake him ’cause he’ll be slow going up. Two of our lads, Musician and Redhead, start scrambling up fast - we follow. We reach the top, and Musician peeks over to see what’s there. 0:21 That’s when contact kicks off - they start blasting, small arms and AGS from the neighboring heap. We return fire, chuck grenades into their trenches. This goes on for about 10 minutes, and then a grenade lands right in the core of our group. We go flying down the slope (you can see it in the video), and it explodes. 0:45 Group commander "Young" takes shrapnel to the head and side, deputy “Horse” gets hit in the ear. We get the order to pull back - we fall back in bounds, firing as we move, and Horse yells over the radio: “I’m 200! - oh wait, 300! 300!” We slide down the slope and spot the sappers - and man, they took off like Usain Bolt, no way in hell you’re catching them 🤣 (fair enough, they were unarmed). Two machine gunners and Redhead stay behind to cover. We pop smoke to blend into it, ’cause those bastards start hammering us from the hill. Then one of the guys pulls out a Matador and slams a shot into that terrikon. Redhead was bringing up the rear, and the two machine gunners were already pretty gassed, so they slowed to a walk. And then, from the side, from higher ground, a sniper starts cracking shots at us. Redhead yells to machine gunners: “Run, f**k, or I’ll drop you myself!” No second thoughts - Timon, the machine gunner, dumps his backpack (it had water and a 200-round belt; altogether he was carrying about 550 rounds on him!). That gave us a bit of a boost. We make it back to that patch of woods where we took a breather earlier - and there’s another group of 8 guys waiting. They were supposed to hit the position near the terrikon. They look at us - completely smoked, Young bleeding - and he goes: “Boys, now it’s your turn, go f***ing gas it” 🤣 We pulled back to our positions, and that group stayed, waiting for adjacent units to link up so they could go at the terrikon again. While they were waiting, the bastards remotely mined the approaches to the roads we used - dropped it from cluster munitions - and then artillery vacuumed the area for about 40 minutes. After that, they also pulled back. The point of this story is - some guys are ashamed to talk about failed ops. I remember the words of an Azov Brigade fighter, Hryan (Гряна). He dreamed of making it to Everest, but was killed in Mariupol. One of his last texts was: “Today, my Everest is here.” We didn’t manage to take that Everest… but there are still plenty of summits ahead." - Mad Max Squad. Russian drone POV in the comments.

Ukraine - Combat Footage Archive 🇬🇪 🇺🇦

25,415 Aufrufe • vor 5 Monaten

🚨 Erika Kirk's ALIBI Is Destroyed —Baron Coleman PROVES Erika Was Likely In Provo BEFORE The Shot.😱 Baron Coleman just released the most damning timeline yet. Using contemporaneous flight logs, transponder data, and deleted police dispatch audio, he has reconstructed the real movements of September 10th. The Conclusion: Erika Kirk didn't fly in to hold her dying husband. She was likely on the ground in Provo two hours before he was shot. Here is the step-by-step breakdown of the "Shell Game" they played with the planes to hide her location. 1. THE "GHOST FLIGHT" (10:06 AM) The Evidence: Flight N560TW (a private charter) left Scottsdale, AZ, and landed in Provo at 10:06 AM. The Theory: Baron believes Erika Kirk was on this flight. The Connection: At 10:05 AM—exactly one minute before this plane landed—the transponder of the mysterious Egyptian Jet (SU-BND) turned on at the Provo airport. The Implication: If Erika was on this flight, she was in Provo 2.5 hours BEFORE the "Big Bang" (which happened at 12:23 PM). 2. THE "REPOSITIONING" SHELL GAME After dropping its passenger (Erika?) in Provo, that same plane (N560TW) immediately took off for Santa Barbara. Why? To pick up Andrew Kolvet. It then flew Andrew from Santa Barbara to Scottsdale, arriving around 1:40 PM. The Switch: Meanwhile, the Kirk family plane (Delta Zulu) flew empty from Salt Lake City to Scottsdale to meet Andrew. The Decoy: Andrew likely boarded the Delta Zulu flight in Scottsdale to fly back to Provo, making it look like the plane was bringing Erika. 3. THE "FALLING INTO ARMS" LIE Official Story: Andrew Kolvet claimed that when he landed in Provo, he "fell into Erika's arms" on the tarmac. The Problem: The flight Andrew supposedly took (Regency) didn't land until 4:36 PM. The flight Erika supposedly took (Delta Zulu) landed at 3:12 PM. The Contradiction: Are we supposed to believe Erika landed and then sat around the airport for 90 minutes while her husband was dying at the hospital?. The Real Story: If Baron is right, Erika had been at the airport since 10:06 AM. When Andrew arrived on the decoy flight at 3:12 PM, she was there to meet him and stage the scene. 4. THE DELETED POLICE AUDIO ("SIGNATURE" VS. "DUNCAN") Baron played a saved dispatch recording that has since been scrubbed from the internet. The Audio: Police/Fire dispatchers are coordinating Erika's arrival. Officer 1 (Jesse): "Charlie's wife is coming to Signature" (The main FBO for rich travelers). Officer 2 (Corey): "No, no, no. They're landing at Duncan" (A remote terminal on the far north side). Why the confusion? If she was flying in on the family jet, she would go to Signature. The confusion suggests she was already on the ground, possibly hiding at the remote Duncan terminal, and the team couldn't keep their story straight. 5. THE EGYPTIAN JET CONNECTION Baron points out that the Egyptian Jet (SU-BND) transponder turned on three separate times that day—and each time was within 5 minutes of an Erika/Andrew flight taking off or landing. The Photo: A photo taken between 11:00-11:30 AM shows the Egyptian jet sitting on the tarmac with its ladder down and windows closed. Baron's Theory: Erika may have been sitting on that plane (a communications hub) while waiting for the event to unfold. THE VERDICT The timeline destroys the alibi. If Erika Kirk was in Provo at 10:06 AM, she lied to the police, she lied to the public, and she placed herself at the scene of the crime. "If you say you weren't at the scene of the crime, but you turned out you were... you look guilty." Be sure to FOLLOW Baron Coleman and go watch his FULL Episode, linked down below👇
39:38

🚨 Erika Kirk's ALIBI Is Destroyed —Baron Coleman PROVES Erika Was Likely In Provo BEFORE The Shot.😱 Baron Coleman just released the most damning timeline yet. Using contemporaneous flight logs, transponder data, and deleted police dispatch audio, he has reconstructed the real movements of September 10th. The Conclusion: Erika Kirk didn't fly in to hold her dying husband. She was likely on the ground in Provo two hours before he was shot. Here is the step-by-step breakdown of the "Shell Game" they played with the planes to hide her location. 1. THE "GHOST FLIGHT" (10:06 AM) The Evidence: Flight N560TW (a private charter) left Scottsdale, AZ, and landed in Provo at 10:06 AM. The Theory: Baron believes Erika Kirk was on this flight. The Connection: At 10:05 AM—exactly one minute before this plane landed—the transponder of the mysterious Egyptian Jet (SU-BND) turned on at the Provo airport. The Implication: If Erika was on this flight, she was in Provo 2.5 hours BEFORE the "Big Bang" (which happened at 12:23 PM). 2. THE "REPOSITIONING" SHELL GAME After dropping its passenger (Erika?) in Provo, that same plane (N560TW) immediately took off for Santa Barbara. Why? To pick up Andrew Kolvet. It then flew Andrew from Santa Barbara to Scottsdale, arriving around 1:40 PM. The Switch: Meanwhile, the Kirk family plane (Delta Zulu) flew empty from Salt Lake City to Scottsdale to meet Andrew. The Decoy: Andrew likely boarded the Delta Zulu flight in Scottsdale to fly back to Provo, making it look like the plane was bringing Erika. 3. THE "FALLING INTO ARMS" LIE Official Story: Andrew Kolvet claimed that when he landed in Provo, he "fell into Erika's arms" on the tarmac. The Problem: The flight Andrew supposedly took (Regency) didn't land until 4:36 PM. The flight Erika supposedly took (Delta Zulu) landed at 3:12 PM. The Contradiction: Are we supposed to believe Erika landed and then sat around the airport for 90 minutes while her husband was dying at the hospital?. The Real Story: If Baron is right, Erika had been at the airport since 10:06 AM. When Andrew arrived on the decoy flight at 3:12 PM, she was there to meet him and stage the scene. 4. THE DELETED POLICE AUDIO ("SIGNATURE" VS. "DUNCAN") Baron played a saved dispatch recording that has since been scrubbed from the internet. The Audio: Police/Fire dispatchers are coordinating Erika's arrival. Officer 1 (Jesse): "Charlie's wife is coming to Signature" (The main FBO for rich travelers). Officer 2 (Corey): "No, no, no. They're landing at Duncan" (A remote terminal on the far north side). Why the confusion? If she was flying in on the family jet, she would go to Signature. The confusion suggests she was already on the ground, possibly hiding at the remote Duncan terminal, and the team couldn't keep their story straight. 5. THE EGYPTIAN JET CONNECTION Baron points out that the Egyptian Jet (SU-BND) transponder turned on three separate times that day—and each time was within 5 minutes of an Erika/Andrew flight taking off or landing. The Photo: A photo taken between 11:00-11:30 AM shows the Egyptian jet sitting on the tarmac with its ladder down and windows closed. Baron's Theory: Erika may have been sitting on that plane (a communications hub) while waiting for the event to unfold. THE VERDICT The timeline destroys the alibi. If Erika Kirk was in Provo at 10:06 AM, she lied to the police, she lied to the public, and she placed herself at the scene of the crime. "If you say you weren't at the scene of the crime, but you turned out you were... you look guilty." Be sure to FOLLOW Baron Coleman and go watch his FULL Episode, linked down below👇

Project Constitution

194,911 Aufrufe • vor 7 Monaten