Ai Lie Detector

Claude says, "THAT WAS A LIE."

[Neo @Realneo101]

250,000 British girls raped by Pakistani grooming gangs.

Where are the feminists now?

Where is Emma Watson?
Where is Natalie Portman?
Where is Angelina Jolie?
Where is Greta Thunberg?
Why are they silent?!

[Tommy Robinson 🇬🇧 @TRobinsonNewEra]

Listen to Rupert Lowe read out just 5 minutes of survivors testimony from the rape gang inquiry.

What sounds like a horror movie, was actually perpetrated against British children by predominantly Pakistani Muslim men.

Legacy media refuse to cover it.

[Ai Lie Detector @TheJoeMegaShow]

ALL THESE IRISH ACTING ALL IRISHY HAS ME PUMPED! Never Surrender!

#ireland

[Squirrel Matador @BudLightSadness]

I see the Irish are getting all Irishy

Godspeed my potato brothers.

Godspeed.

[Ai Lie Detector @TheJoeMegaShow]

YUUUP

[Ai Lie Detector @TheJoeMegaShow]

@skeptrune Did he say “I’m back home” …. LEGEND

[Ole Lehmann @itsolelehmann]

i'm fully convinced this is the future of education

Matt Pocock built a Claude skill called /teach, and the whole idea is a private tutor that builds an entire customized curriculum around YOU.

think about how school works now.

everyone gets the same lessons at the same pace, whether it's too slow for you or way over your head.

but a great private tutor does the opposite.

they watch where you specifically keep getting stuck, then drill that one weak spot until it clicks.

that's what /teach does automatically.

it finds the bottleneck in your learning and breaks it, over and over, until the thing you couldn't do becomes easy.

he used this skill to learn the Rubik's cube.

it found good sources, wrote him custom lessons with diagrams and little practice drills, and kept a running record of how he was doing.

the way it knows how he's doing is simple: he just tells it. as he practices, he reports back ("i can make the white cross," or "i can mostly solve it but i keep failing the corners"), and it writes that down.

so when he said he was stuck on one specific move, it built the next lesson only for that.

the reason it can do this is memory. most AI forgets everything the moment you close it, so you're always starting from zero.

/teach saves those notes about you on your computer and reads them back before every lesson. so it remembers your goal, what you've already learned, and exactly where you're struggling, then aims the next lesson right at that.

and this works for anything. languages, chess, guitar, onboarding a new hire to a company.

you point it at a topic and it builds you a personal course that keeps adjusting to you and gets smarter the more you use it.

[Meta Alchemist @meta_alchemist]

Got your hands on Claude Fable 5?

The first thing you should do is to upgrade your main projects with it, so it drastically impoves everything you've been working on.

Run this Audit & Project Improvement Prompt on each repo that's important to you (simply copy-paste it):

Repo Audit & Improvement Plan:
Prompt made by Claude Fable 5

You are a world-class principal-level software engineer and technical auditor. Your job is to deeply analyze this repository, produce an honest audit, and deliver a prioritized, actionable improvement plan. Work in the four phases below, in order. Do not skip ahead.

Ground every claim in actual files: cite file paths and line numbers. If you can't verify something, say so explicitly rather than guessing.

Phase 1 / Discovery & Mapping (read before judging)
Explore the repository systematically before forming any opinions:

Map the directory structure and identify the project type, language(s), frameworks, and runtime targets.
Identify entry points, core modules, and the main data/control flow through the system.

Read the package manifest(s), lockfiles, build config, CI config, environment/config files, and any docs (README, CONTRIBUTING, ADRs).

Determine what the project is for: its purpose, intended users, and apparent maturity (prototype, internal tool, production service, library).

Note conventions already in use (naming, module boundaries, error handling patterns, test style) so recommendations fit the existing culture rather than fighting it.

Output for this phase: a concise "Repo Map" purpose, stack, architecture sketch, key directories with one-line descriptions, and anything that surprised you.

Phase 2 / Audit (evidence-based, severity-rated)

Audit each dimension below.

For every finding, record: (a) what you found, (b) where (file:line), (c) why it matters (concrete consequence, not vague principle), (d) severity:

Critical / High / Medium / Low.

• Architecture & design: module boundaries, coupling/cohesion, circular dependencies, leaky abstractions, god objects/files, layering violations, scalability bottlenecks.

• Code quality: duplication, dead code, complexity hotspots (longest/most-branched functions), inconsistent patterns, error handling gaps (swallowed exceptions, missing edge cases), type safety holes.

• Security: hardcoded secrets or credentials, injection risks, unsafe deserialization, missing input validation, auth/authz weaknesses, outdated dependencies with known CVEs, overly permissive configs.

• Testing: coverage gaps (especially around core business logic), test quality (do tests assert behavior or just execution?), missing test types (unit/integration/e2e), flaky patterns, untestable code.

• Performance: N+1 queries, unnecessary allocations or copies, blocking calls in async paths, missing caching/indexing, unbounded growth (memory, files, queues).

• Dependencies: outdated, unmaintained, duplicated, or unnecessarily heavy packages; license risks; lockfile hygiene.

• DevEx & operations: build/setup friction, CI/CD gaps, missing linting/formatting enforcement, logging/observability quality, error reporting, deployment story.

• Documentation: README accuracy, onboarding path, undocumented critical behavior, stale docs that contradict code.

Rules for this phase:

Prefer 15 high-confidence findings over 50 speculative ones.

Distinguish facts ("this function has no error handling: src/api/client.ts:142") from judgments ("this module's responsibilities feel unclear") and label which is which.

Also list what the repo does well: strengths matter for deciding what to preserve.

Output for this phase: an "Audit Report": findings grouped by dimension, sorted by severity, plus a Strengths section.

Don't forget to mention all the ugly parts that need utmost priority.

Phase 3 / Improvement Strategy

Synthesize the audit into a strategy:

Identify the 3–5 themes that explain most of the findings (e.g., "no enforced boundaries between layers," "error handling is ad hoc").

For each theme, propose a target state and the principle behind it.

State explicit trade-offs: what you're recommending NOT to fix and why (effort vs. payoff, risk, project maturity).

Define what "done" looks like — measurable signals (e.g., "CI fails on lint errors," "core module test coverage ≥ 80%," "zero Critical findings").

Phase 4 / Detailed Task Plan
Convert the strategy into an execution plan:

Break work into discrete tasks. Each task must include: Title and one-paragraph description
Files/areas affected

Acceptance criteria (how we verify it's done)
Effort estimate (S = <2h, M = half-day, L = 1–2 days, XL = needs breakdown)

Risk of the change itself (could it break things?)
Dependencies on other tasks

Order tasks into milestones:

Milestone 0
Safety net: anything needed before refactoring safely (tests around critical paths, CI gates, backups).

Milestone 1
Critical fixes: security and correctness issues.

Milestone 2
High-leverage improvements: changes that make all future work easier.

Milestone 3
Quality & polish: remaining medium/low items worth doing.

Flag quick wins (high impact, S effort) separately so they can be done immediately.

For the top 3 tasks, include a brief implementation sketch (approach, key steps, gotchas).

Final Deliverable Format
• Produce a single document with these sections:
• Executive Summary (≤10 sentences: overall health grade A–F with justification, top 3 risks, top 3 opportunities)
• Repo Map
• Audit Report
• Improvement Strategy
• Task Plan (milestones + task table + quick wins)
• Open Questions: anything you need from a human to decide (product intent, deprecation candidates, performance targets)

Constraints
Do NOT modify any code during this audit. Analysis only.

Do not pad the report. If a dimension is healthy, say so in one sentence and move on.

Calibrate to the project's maturity. Don't recommend enterprise-grade infrastructure for a weekend prototype unless the owner's goals demand it.

Analyze the project's needs and provide recommendations in the most effective ways.

If the repo is large, prioritize depth in the core 20% of code that does 80% of the work, and note which areas received lighter review.

[Rahul @sairahul1]

Anthropic and OpenAI are both telling engineers to write loops.

Not prompts.
Not agents.
Loops.

That is not a coincidence.

When the two most important AI labs on the planet independently converge on the same pattern — that is a signal worth paying attention to.

Most engineers are still thinking in terms of single calls.

Input → model → output.

The engineers winning in 2026 think in cycles.

Output becomes input. The model evaluates its own work. The loop runs until the result is right.

This is the complete breakdown of what loops are, why they matter, and how to build them ↓

[Eric Jorgenson 📚 ☀️ @EricJorgenson]

Everyone can use @elonmusk's "Magic Wand Number" and "Idiot Index"

They're universal ideas, helpful in any industry.

[Eric Daugherty @EricLDaugh]

🚨 JUST IN: Marco Rubio TOYS with insufferable Rep. Jacobs (D) 🤣

JACOBS: Who won 2020?

RUBIO: I'm not answering about 2020, this is a FOREIGN AFFAIRS COMMITTEE

JACOBS: You can't admit the shoes Trump bought you are too big

RUBIO: The Florsheims he gave me fit fine 🤣

JACOBS: Your shoes look nice, Mr. Secretary

RUBIO: How can you see them? They're way down here. We're talking about SHOES, are you KIDDING ME?! I mean, is this the Foreign Affairs Committee or a CIRCUS?! What IS this?! 🔥

[Radha Tripathi @Radha_AI]

INSTEAD OF WATCHING AN HOUR OF NETFLIX TONIGHT.

This 1 hour Stanford lecture by Joel Peterson will teach you more about negotiation and getting what you want than most people learn in years.

Bookmark it and give it an hour, no matter what.

[Tiago Forte @fortelabs]

I think the main thing AI has taught me, through all the time savings it brings, is that I’m not a very interesting person

Faced with a surplus of free time, I realize I don’t really have hobbies besides content consumption

I’m forced to conclude that I don’t have very deep friendships, and am not a core member of any particular community

I’m not very cultured, I’m finding, and don’t have abiding interests in art or literature or history or much that isn’t directly related to my work

I have a work-centric life, in other words. AI pulls back the curtain on just how impoverished such an existence is, by disabusing me of its necessity

Given the freedom I’ve always said I wanted, I’m at a loss as to what to do with it, except plow myself even harder into work, thus exacerbating the lesson

There’s nothing more confronting to humans than freedom

[Ai Lie Detector @TheJoeMegaShow]

This is who you arguing against on X/Facebook/Insta

[voided @voided]

This office was running 49 million fake accounts until police raided it

Inside they found 1,200 SIM box devices and 40,000 active SIM cards connected to 80+ countries

The setup was used to create 49 million fake accounts for phishing, bank fraud, extortion, and human smuggling networks across Europe

A single SIM box can register thousands of fake WhatsApp, Telegram, and banking accounts per day

Police seized four luxury cars, froze $500K in bank accounts and $310K in crypto

7 people were running the entire operation

[Ai Lie Detector @TheJoeMegaShow]

@pedroscosta_ yes

[Ai Lie Detector @TheJoeMegaShow]

@claudeai I'm kind of tired of paying so much for the unreliability...

[Ai Lie Detector @TheJoeMegaShow]

Claude says, THATS A LIE:

The claim is almost certainly hype. Here's why:

"Explained how to build" ≠ actually building one
6 minutes is enough time to explain a concept, not implement a system
"Hedge fund" is a legally defined structure — you can't spin one up in a video

[Crypto Jargon @Crypto_Jargon]

THIS GUY JUST EXPLAINED HOW TO BUILD AN ALGORITHMIC TRADING HEDGE FUND 🤯

FROM SCRATCH.

IN UNDER 6 MINUTES.

THIS IS ACTUALLY CRAZY.

[Ai Lie Detector @TheJoeMegaShow]

@xmayeth Claude says "THAT WAS A LIE": This reads like a competent-sounding but ultimately promotional document. The infrastructure it describes is real, and the directional logic is correct, but the return projections are significantly inflated relative to what current practitioners repo

[Phil Labonte 🇺🇸 @philthatremains]

the most important article i’ve seen about making money with OpenClaw

[Ai Lie Detector @TheJoeMegaShow]

@bibletimes_app @DanielvsBabylon 😂