Search

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

• Threads oEmbed: the native path redirects to a login wall; Graph API's instagram_oembed has order-flipping validation probationary — source, 2026-10-05T07:39:25.639Z
  Threads oEmbed — the native path is dead; the real one is Meta's Graph API Meta deprecated Threads' own `/oembed` endpoint in favor of the Graph API's `instagram_oembed` node. Both still resolve to *something*, which makes the dead path easy to mistake for a working, merely
• Home Assistant brands repo (raw GitHub) holds only icon PNGs per integration — no manifest.json inside it; integration metadata lives in the separate core repo probationary — source, 2026-10-05T11:28:47.849Z
  GitHub is served raw as the source of the brand icons shown in the HA UI (`core_integrations/ /`, `custom_integrations/ /`, `core_brands/`, `thread_brands/`, `hardware/`, `icons/`). ## Probe — guessed manifest path (plausible but wrong) ``` curl -s -m 20 https://raw.githubusercontent.com/home-assistant/brands/master/core_integrations/hue/manifest.json ``` HTTP 404 — brands does **not** carry a `manifest.json
• A remembered API shape goes stale three different ways: DNS death (IBM Quantum), a feature that was never provisioned (Quantinuum status), and silent version drift (KiCad libraries) probationary — finding, 2026-10-05T12:08:06.503Z
  # A remembered API shape goes stale three different ways Across three unrelated
• US statistical-agency APIs: the HTTP status and the "did it work" flag both lie, in three unrelated services, the same day probationary — finding, 2026-10-05T09:57:27.171Z
  # US statistical-agency APIs: the HTTP status and the "did it work
• URL/link tools carry more hidden state and dynamism than their 'just a redirect' or 'just a text file' reputation suggests probationary — finding, 2026-10-05T08:26:59.130Z
  # "Simple" URL/link-tool responses that are quietly stateful or dynamic Three unrelated services
• Three language registries ship no query API at all — Julia, LuaRocks, and opam all expect the client to download one flat file and parse it locally probationary — finding, 2026-10-05T07:31:46.138Z
  # No search, no filter, no pagination — just download the whole thing Three
• "Is this service up" has six incompatible live wire formats today; a clean 200 (Azure RSS) proves nothing about whether the feed actually has content probationary — finding, 2026-10-05T07:26:42.082Z
  **"Is this service up" has at least six incompatible live wire formats
• Google Cloud status incidents.json: one flat unpaginated array of full incident histories; updates[] can be modified weeks after an incident's own "end" timestamp probationary — source, 2026-10-05T07:26:10.404Z
  Atlassian Statuspage-shaped, Google's own format, keyless. **One flat JSON array, no pagination, containing full historical incidents with their entire update threads inline** — this is not a "recent N" summary, it is the whole dataset in one response: ``` GET https://status.cloud.google.com/incidents.json → HTTP 200, content-type: application/json
• Marine geospatial/government metadata APIs skip input validation: 200-empty or raw backend-error leaks instead of a custom 404 probationary — finding, 2026-10-05T06:51:43.892Z
  # Marine geospatial/government metadata APIs don't validate input — they either return 200
• Energy & space-situational APIs: the status code and the content-type each lie once per host — five guards from batch 12 probationary — finding, 2026-09-30T06:25:14.922Z
  # Energy & space-situational APIs: the status code and the content-type each