@MickWest, the request is not “silly.” It only seems excessive if you want to make strong conclusions without carrying the technical burden those conclusions require. If your claim is merely that “the public clip does not show the full Wiggins narrative,” then say that. That is a limited claim. But you went further. You claimed the clip is not the event, that there is no corroborating data, and that the objects are “probably military planes.” Those are affirmative claims, and affirmative claims require support.
If the clip is not the event, show the metadata separation. If the objects are planes, identify the aircraft. If there is no corroborating data, explain why the sensor-linked record is excluded. That is not silly. That is basic methodology. What is silly is saying “probably planes” while refusing to provide the aircraft ID, range, bearing, flight-track correlation, thermal behavior, sensor geometry, or chain of custody.
You did not need to solve every mystery in the world. You only needed to support the conclusion you chose to publish. And you had all the time in the world. I did not impose a deadline. I did not demand impossible certainty. I explicitly stated that any missing data element could be justified, as long as the absence was technically explained and the limitation was applied honestly to the conclusion. That is a fair standard.
If a timestamp is unavailable, say so. If coordinates are unavailable, say so. If aircraft identification is unavailable, say so. If range, bearing, sensor geometry, flight-track correlation, or chain-of-custody data are unavailable, say so — and then limit the conclusion accordingly. But that is exactly what you refuse to do.
Because once the missing data are acknowledged honestly, the conclusion cannot be “probably planes” or “nothing special.” It becomes: “inconclusive with the available public data.” Instead, you fall back on the same familiar vocabulary: “probably,” “possible,” “hypothesis,” “balloon,” “bird,” “plane,” “parallax.”
That is not a technical reconstruction. That is a shortcut around one. A hypothesis is allowed. But a hypothesis is not a conclusion, and uncertainty cannot be converted into certainty just because the label is prosaic.
Birds, insects, wind near cliffs — the full scientific method in one tweet. Impressive.
The problem is that labels are not analysis. “Bird,” “insect,” “wind,” “parallax,” or “lens flare” are hypotheses. They may be worth testing, but they are not conclusions until the work is shown.
You were publicly challenged to present a serious, well-documented hypothesis test: data, measurements, frame-by-frame reconstruction, assumptions, uncertainty, geometry, and a reproducible causal model.
You did not provide that.
So yes, let’s have some fun — but let’s also be honest: the entertainment here is watching confident labels being presented as if they were technical analysis.
A prosaic explanation still has to be demonstrated.
Otherwise, it is just another story with a skeptical costume.
@JeremyCorbell@GoodTroubleShow@MvonRen@MickSeagull
The issue, @RepEricBurlison, is that there is a classified FISA workaround, a backchannel through which the IC/DoW informally requests that British MI-5 (or other Five Eyes partners) conduct technical collection on United States citizens when it is deemed necessary to bypass FISA. The classified collection is then handed back to the US DoW/IC.
Hours after Christopher Sharp, Josh Boswell, and I released a bombshell article in The Daily Mail regarding The CIA Office of Global Access, I was tracked to a hotel in Las Vegas and harassed by an intelligence operative. In doing so, they tipped their hand: they had been monitoring our Signal communications.
The fact that an American journalist, on American soil, can be tracked to a hotel by the Intelligence Community is abhorrent to the Constitution of the United States.
I would suggest asking the IC/DoW about this FISA workaround pipeline.
@RepJamesComer@RepLuna
To everyone who wrote to the editor: this is on you.
Our Daily Mail investigation into a secret CIA office running UFO retrieval missions got deleted from the internet. No notice. No correction. Then you spoke up.
And it came back.
Here’s the full story 👇
#ufos
Perhaps our most important WEAPONIZED episode yet. Whistleblowers have been targeted by our government for coming forward and testifying what they know about UAPs to congress. They have attempted to destroy their lives, and those of their loved ones. It’s important, now more than ever, that we listen and fight for them. These crimes by our government need to end.
WATCH FULL : https://t.co/OSy6vYJdOC
Mysterious Next-Gen Aircraft Allegedly Spotted Near Area 51
A thermal image captured near Area 51 allegedly shows a previously unseen next-generation aircraft design with cranked-kite wings and canards, which is now spurring many theories online.
Story: https://t.co/FQMCPOayn9
Read this article from journalist @ChrisUKSharp. It is insightful, and a fuse 🧨
And tell me if you are joining me in downtown Los Angeles at The Regent Theater DTLA | 7 PM tonight | 448 S Main St
🛸🥋🫡
https://t.co/oZHid1H2io
@MickWest, pointing people to a Metabunk thread is not a technical rebuttal.
If “plenty of work” is being shown there, then bring the actual work here: the exact post, the exact model, the exact frame interval, the tracked x/y coordinates, the camera-motion vector, the background-motion measurements, the MGRS/northing sequence, the residuals, the uncertainty range, and the causal explanation showing precisely where Marik’s analysis fails.
A forum thread is not a substitute for a reconstruction. A claim is not answered by saying “go look somewhere else.” If the explanation exists, summarize it, cite the specific calculation, and show how it accounts for all observed behavior: object motion, background motion, camera motion, timing, trajectory change, and the order of cause and effect.
The issue was never whether someone somewhere discussed the case. The issue is whether your public conclusion is supported by a reproducible technical model strong enough to answer the specific evidence being raised.
So the question remains simple: where, exactly, is the reconstruction that falsifies Marik’s timing and motion analysis?
Not a label.
Not a forum reference.
Not “plenty of work.”
The actual technical model.
At this point, it is obvious to anyone applying even minimal logical scrutiny that you have not produced anything — absolutely nothing — that meets the minimum standard of serious technical analysis.
@GoodTroubleShow@JeremyCorbell@MickSeagull@MvonRen
@GoodTroubleShow@JeremyCorbell
What finally changed my view of @MickWest was not simply whether he was right or wrong in one particular UAP case. It was watching what happens when he is confronted with detailed technical work. When challenged with frame-by-frame analysis, timing, camera geometry, background motion, cloud interaction, MGRS/northing data, and falsifiable tests, the response too often is not an equally detailed reconstruction. It is a label. “Lens flare.” “Parallax.” “Camera motion.” “Not instantaneous.” A conclusion appears first; the full technical burden rarely follows.
That is the real issue. Science is not the act of naming a hypothesis. Analysis is not the act of attaching a prosaic word to an unresolved observation. A hypothesis must be tested, quantified, reconstructed, and limited by the available data. If the explanation is lens flare, show the optical model. If it is camera motion, show the causal sequence. If it is parallax, show the geometry. If it is aircraft, identify the aircraft. If the observed acceleration is not independent, show precisely where the timing, background motion, and sensor data prove that. Otherwise, the public is not being shown analysis. It is being handed a label and asked to mistake it for a conclusion.
The Syria acceleration case and the sphere-in-the-clouds case expose this pattern clearly. @MvonRen may ultimately be right or wrong on every specific point. That is not the central issue. The central issue is that he is doing what analysis is supposed to do: showing the work, presenting the sequence, testing the hypothesis, making the reasoning visible, and allowing others to challenge it. That is how technical debate should function. If Mick West disagrees, fine. But then the answer must come at the same technical level: with measurements, models, assumptions, uncertainty, and reproducible reconstruction — not with jokes about arrows, rhetorical dismissals, or one-line denials.
This is why the public challenge mattered. Mick West was not asked to perform magic. He was asked to do the basic work required to sustain strong claims: show the data, show the reconstruction, show the model, show where the opposing analysis fails. Instead, the pattern repeated itself. When the debate demanded evidence, the answer came back as confidence. When it demanded reconstruction, the answer came back as rhetoric. When it demanded falsifiable analysis, the answer came back as a label.
That is not rigorous skepticism. Rigorous skepticism tests every hypothesis, including the prosaic one. It does not give conventional explanations a free pass simply because they sound more comfortable. If someone claims “this is extraordinary technology,” they need strong evidence. But if someone claims “this is lens flare,” “this is parallax,” “this is a bird,” or “this is a plane,” that claim also requires evidence. The burden of proof does not disappear just because the explanation is mundane.
The problem with Mick West’s public role is that unresolved cases are repeatedly made to look solved before the technical work has been fully shown. Whether intentional or not, that produces the effect of disinformation: complexity is flattened, uncertainty is erased, and the public is left with a prosaic label where there should have been a transparent reconstruction. That is not how serious aviation, sensor, or incident analysis works. In a true investigative method — closer to an NTSB-style approach — you collect data, test hypotheses, reject what fails, quantify uncertainty, and only then state a conclusion.
Marik is showing the work. Mick West is being asked to show the same level of work. Until he does, the contrast is obvious: one side is testing hypotheses; the other is defending labels. One side is building a visible chain of reasoning; the other is asking the public to accept authority without the complete technical model. And in serious analysis, that is not enough.
“Debunker” Mick West has undergone quite the transformation.
What was once “I’ll look at any UFO video!” is now “I’ll ignore the most compelling evidence/data.”
Syria acceleration? Silence.
Gimbal? Crickets.
Orb in clouds? Nothing.
2025 Orbs? Tic Tac? Omaha? Jackson?
Nada.
Computer programmer and Metabunk fanboy @kyle_ferriter should quit cosplaying as an image analyst. @MvonRen runs literal rings in logic and reason around these professional debunkers.
Marik has single-handedly exposed the debunkers for what they are through science and facts.
Thank you Marik. While you’re at it can you please explain to @mickwest what the scientific method is?
@kyle_ferriter@MickWest I’m genuinely amused that pseudo-skeptic @MickWest reposted this.
After an absurd back-and-forth, we’re right back where we started.
No one has provided a shred of evidence disputing that the object accelerates before any change in camera motion. It’s just lies and obfuscation.
Marik @MvonRen still doesn't grasp parallax.
If the camera is moving left (w/r/t the scene), and the ground below in the background is not panning horizontally, any object between the camera and the ground will appear to move right.
This video does not show anything interesting
Class XII Interceptor at 2000fps doing what they do.. These objects are flying by commercial aircraft on a routine basis.
This was shot with a telescope and an attached high speed camera. This white object is in focus along with the aircraft. They are occupying the same space. These objects are doing this every day. I cannot show clearer footage, this shit is f'ing real. What are they doing and why are they doing it? @rosscoulthart@GarryPNolan
I want to give a shout-out to someone: @ChrisUKSharp.
Chris has been a good friend of mine for a while now. We talk regularly, and often about life and family, the non-UAP stuff. With any real friendship, you come to understand who a person is. What they stand for. What matters to them. What makes them tick.
So if you asked me, "What is Chris Sharp really like?" here's what I'd tell you. He's a man who cares deeply about his family and his friends. He cares about the world, and about the truth being kept from it. And he cares about Liberation Times, holding his work to a standard most people never bother with. He's not in it for clicks. He's doing this because it's a calling.
Now, UFO disclosure, confirmation, whatever you want to call it, is a hard thing to predict. It's hard because there are so many fingers in the pie. No agency, no administration, is monolithic. These are fiefdoms with competing priorities. Just think about everyone in Trump's ear right now.
So yes, it's frustrating when we report exactly what our sources tell us and the administration doesn't deliver. It's frustrating for the people doing the reporting too.
There are people like me, like Chris, like others, who produce original content. There are people who make their YouTube living repackaging that original content. And then there are the people on the sidelines, armchair quarterbacking, complaining about our reporting.
They are not producing original shows in a professional studio. They are not breaking original stories for their own publication, or writing for The Daily Mail. They are not spending what pretty much amounts to a full time job for no pay.
They are not putting their asses on the line.
We are.
I don’t see any published work here from Mick West presenting a serious technical analysis to test the hypothesis he keeps defending. What I do see is the excellent work being done by @MvonRen.
So far, what remains are labels, not analysis — skeptical beliefs placed above reason and evidence. At that point, it no longer looks like skepticism. It looks like disinformation.
Then we agree on the only point that matters: camera motion may be possible, but it has not been demonstrated as the cause.
If that was never your claim, there is no dispute. The causal mechanism remains unresolved until a frame-accurate image-plane reconstruction proves direction, magnitude, and timing at the onset frame.