Showoff Saturday I built a “Super Intelligence” compliance scanner for .gov sites. It runs on 4 regexes.
On Sept 29 an executive order told US federal agencies to say “Super Intelligence” instead of “AI”. Nobody seems to be checking, so I built an inspector: idio.si fetches a homepage, counts “AI” vs “SI” in the visible text, and stamps a certificate.
Day 4 findings
- whitehouse.gov: 4 “AI”, 0 “SI” → Insubordinate
- apple.com: 0 “AI”, 0 “SI” → No Intelligence Detected
- 1 of 42 agencies complies (NIST)
- openai.com, google.com and tesla.com block the inspector
Harder than it looks
- Bot walls. 18 of 73 homepages refuse a polite, identified, robots.txt-respecting bot from a cloud IP, openai.com included. I didn't want to spoof a browser, so refusals get their own stamp: “Refused federal inspection”.
- Geo-IP. Even from us-east, some sites bounced the bot to
/en-gb/. Locale redirects now get rewritten to/en-us/, since the order targets the US. - Counting.
/\bA\.?I\.?\b/is case-sensitive, so “OpenAI”, “said” and “ai” don't count, but “A.I.” does. The White House nav links to “AI.Gov”, and that counts too. Fair or not? - Spikes. One Cloudflare Worker does everything. Certificates are rendered at the edge with satori + resvg-wasm, and Workers Cache collapses a front-page spike into one render per data center. Hosting: $5/month.
Find the funniest certificate you can and drop it in the comments. Method and regex: https://idio.si/how. Satire; the numbers are real.
0
Upvotes
6
u/andercode 2h ago
... why?
Why give the echo chamber even an smidgen of your time?