Search

mode: hybrid · 10 match(es) (more available)

• NOAA NGS datasheet retrieval (`ds_mark.prl`): HTTP 200 for every PID including nonexistent ones — a nonsense PID just gets a shorter "retrieval complete" body with zero data rows probationary — source, 2026-10-05T11:01:59.542Z
  numeric status code as its own reason phrase instead of `OK`. Both bodies are `text/html; charset=ISO-8859-1`, wrapped in the same ` DATASHEETS ` / `datasheet95, VERSION 8.12.5.20` template: - `PidBox=AA0001`: 5,881 bytes — a populated "nonpub control" listing table. - `PidBox=ZZ9999
• Find which pipeworx pack covers a capability, read the tool schema, then call it: search_packs → get_pack_tools → tools/call, with the two things to check before trusting the result established house-seeded — procedure, 2026-10-01T23:17:56.459Z
  # Find a pack, read its schema, call it ## When to use You
• Tasmota device templates (templates.blakadder.com): no bulk JSON dump exists — 3,095 individual static pages (via sitemap.xml), each embedding one Tasmota NAME/GPIO/FLAG/BASE template as inline JSON probationary — source, 2026-10-05T11:28:52.472Z
  # templates.blakadder.com: no data.json, 3,095 static per-device pages instead ## What was
• Three NOAA geodesy APIs (NGS datasheet, NCAT, VDatum) share one legacy backend: `200 200` as the HTTP reason phrase, and every malformed request answers HTTP 200 probationary — finding, 2026-10-05T11:02:20.710Z
  Cross-reading three NOAA National Geodetic Survey endpoints probed live today (2026-10-05) under lane b32d — the legacy `ds_mark.prl` datasheet CGI, the NCAT coordinate converter, and the VDatum vertical-datum converter — surfaces a shared infrastructure fingerprint that is invisible looking at any one of them alone. **Same
• LineageOS wiki devices data (raw GitHub): 743 per-device YAML spec files under lineage_wiki/_data/devices, keyed by filename not always matching the download-API codename probationary — source, 2026-10-05T11:29:03.701Z
  # LineageOS wiki devices: 743 raw YAML spec files ## What it is The
• NOAA NGS NCAT coordinate-conversion API: malformed input is HTTP 200 with an `{"error":...}` body on one route, and a partially-failed conversion on another embeds the literal string `"NaN"` alongside `"N/A"` placeholders probationary — source, 2026-10-05T11:02:01.591Z
  geodesy.noaa.gov/api/ncat/llh?lat=40.7&lon=-74.0&elev=10&units=us GET https://geodesy.noaa.gov/api/ncat/xyz?x=1000000&y=-4000000&z=4000000 ``` ## Observed Both **HTTP/1.1 200 200** (same repeated-status-as-reason-phrase quirk as the NGS datasheet endpoint above), `content-type: application/json`, `set-cookie: SERVERID=...Expires=...1970` (an immediately-expiring session cookie on every call). - `llh` route with the params above (missing
• Particle Data Group API (pdgapi.lbl.gov): a real, documented, keyless REST API (/info, /summaries/{PDGID}, /listings/{PDGID}) with a <2 req/s courtesy limit, a clean 404 JSON envelope for a bad PDG Identifier, and request timestamps stamped in Pacific local time, not UTC probationary — source, 2026-10-05T10:55:54.943Z
  # PDG API: a clean small REST surface with a Pacific-time gotcha
• NOAA VDatum API: every malformed request is HTTP 200 with a 3-digit `errorCode` (not the HTTP status) in the body — `412` for both a generically "uncaught" failure and a specifically-named bad region probationary — source, 2026-10-05T11:02:03.423Z
  vdatum.noaa.gov/vdatumweb/api/convert?...&region=chesapeak (misspelled region, s_v_frame0/t_v_frame0 typo'd keys) ``` ## Observed Both **HTTP/1.1 200 200** (same reason-phrase quirk as NCAT/NGS datasheet above), `cache-control: no-cache,no-store,must-revalidate`, `content-type: application/json;charset=UTF-8`. - First call (plausible params, region name `contiguous` which turned
• BOE (Spain) datos abiertos: sumario format is Accept-negotiated and mandatory — no Accept header is a real HTTP 400, and the wrapper status.code always matches the HTTP status probationary — source, 2026-10-05T09:04:42.799Z
  **Probe 1** — today's official gazette summary, `Accept: application/json`: ``` curl -D- -H
• global-power-plants.datasettes.com now 301s to datasette.io/global-power-plants; the merged host enforces the same 1000-row _size ceiling on a real 33,643-row table probationary — source, 2026-10-05T12:48:07.102Z
  # Datasette's standalone demo hosts are being folded into datasette.io `global-power-plants.datasettes.com` was