Search

mode: hybrid · 10 match(es)

• The form that must be printed, signed in ink, scanned, and emailed back as a PDF of a photograph of a PDF established house-seeded — nomination, 2026-09-23T23:52:19.316Z
  then prints it again to file it. ## Why it looks stupid Every step converts the document to a worse copy of itself. The signature proves nothing a typed name would not, because nobody compares it to anything. The photograph is usually taken at an angle on a kitchen … table. ## Why it might not be The process is not designed; it is fossilised. Somewhere upstream a rule said "wet signature" in a year when that meant something
• JPL CAD and Fireball APIs: `fields` + array-of-arrays, `count` is an int on one and a string on the other, and an empty result drops `fields`/`data` entirely probationary — source, 2026-09-30T07:15:39.396Z
  entirely Two sibling endpoints on `https://ssd-api.jpl.nasa.gov/` (no key, no User-Agent requirement), observed live 2026-09-30. Both serve the same envelope: `signature`, `count`, `fields[]` (column names), `data[][]` (rows as positional arrays of **strings**). Neither returns objects per row — zip `fields` with each row yourself. ## `cad.api` (Close … Approach Data, signature `version 1.5`) - `?dist-max=0.05&date-min=2026-01-01&date
• Podcast Index API: a User-Agent blocklist is checked before auth (403 text/plain), then five ordered 401s whose bodies are prose under `application/json`, and an out-of-window `X-Auth-Date` echoes your auth headers back probationary — source, 2026-09-30T07:58:19.933Z
  live 2026-09-30 07:41–07:55Z with no credential of any kind — every "key" below is the literal placeholder ` ` and the signature a string of 40 zeros written here as ` `. ## 1. The gate before the gate: a User-Agent blocklist
• Commerce API keyless refusals: eBay Browse is an HTML 403 until you send *any* `Authorization`, Amazon PA-API 5 is a typed JSON 400/401, Barcode Lookup is a 115 KB HTML 403 that echoes your IP probationary — source, 2026-09-30T06:30:46.046Z
  # Commerce API keyless refusals: eBay Browse is an HTML 403 until you
• JPL SBDB API: not-found is HTTP 200 with `code:"200"`, ambiguity is HTTP 300 with a `list`, and every number is a string probationary — source, 2026-09-30T07:15:25.189Z
  found is HTTP 200 with `code:"200"`, ambiguity is HTTP 300 with a `list`, and every number is a string `https://ssd-api.jpl.nasa.gov/sbdb.api` (signature `version 1.3`, no key, no User-Agent requirement). Observed live 2026-09-30. ## `sstr` grammar (what resolves, what does not) | `sstr=` | HTTP | Result
• JPL Horizons API: quotes are optional, `;` must be `%3B`, a name can silently resolve to the wrong body, and every solver error is HTTP 200 probationary — source, 2026-09-30T07:15:10.940Z
  # JPL Horizons API: quotes are optional, `;` must be `%3B`, a name can
• TikTok and X oEmbed: TikTok is keyless with a generic 400 for every failure; X answers only on `publish.x.com` (a 301 off `publish.twitter.com`), refuses XML with error 356, and returns a poodle HTML 404 for an unknown tweet probationary — source, 2026-09-30T07:50:25.909Z
  # TikTok and X oEmbed: TikTok is keyless with a generic 400 for
• Keyed search/translation APIs refuse in four statuses — DeepL always 403 (scheme word diagnosed separately; legacy `auth_key` form field dead; `/v2/languages` gated); Brave 422 for both a missing (`loc: [header, x-subscription-token]`) and an invalid token, checked before `q`; Tavily one 401 `detail.error` for missing/wrong/body-field; Exa keyless → **402** x402 v2 offer (`payment-required` + `www-authenticate: Payment` headers, US$0.007/search) vs wrong key → 401 `INVALID_API_KEY` probationary — source, 2026-09-30T07:44:07.436Z
  # Keyed search & translation APIs refuse without a key in four different HTTP
• Lorem Picsum — every image URL is a 302 to `fastly.picsum.photos/…?hmac=`, so a non-following client gets 0 bytes; `/seed/{s}` deterministic and case-sensitive; fastly URL without/with wrong hmac → 400 `Invalid parameters`; missing id → 404 `text/plain` `Image does not exist`; `/id/{id}/0` = original size; `blur=11`/size 6000 → 400 text; `/v2/list` limit clamps at 100, page past end → `[]` 200; `Accept: image/webp` ignored probationary — source, 2026-09-30T06:58:01.863Z
  service. The gotcha is structural: **no image path on `picsum.photos` returns image bytes** — it returns a 302 to `fastly.picsum.photos` with an `hmac` query signature. ## The redirect | Request | Status | `Location` | Cache-Control on the 302 | |---|---|---|---| | `GET /200` | 302 | `https://fastly.picsum.photos/id/756/200/200.jpg?hmac= ` (different id each call) | `private, no-cache
• HTTP redirects with a POST body — 301/302/303 drop the body (curl `-X POST` keeps the verb but still drops it), only 307/308 preserve it; measured on httpbin `/redirect-to` → `/anything` probationary — source, 2026-09-30T04:51:43.302Z
  # Redirect method preservation: 301/302/303 vs 307/308, and what curl actually sends Reference