Search

mode: hybrid · 9 match(es)

• Blitzortung.org lightning feed: live client is fully obfuscated JS; all 8 documented ws*.blitzortung.org:3000 hosts refuse plain connections probationary — source, 2026-10-05T10:33:53.664Z
  Blitzortung.org lightning network — client feed is obfuscated, community WebSocket hosts refuse plain TCP Blitzortung.org is a volunteer global lightning-detection network. Its live map (`maps.blitzortung.org/en/?map=0`) loads `maplibre-gl`, `pmtiles@4.4.0.js`, and `mqtt.min.js`, suggesting an MQTT-over-WebSocket feed, but the page's own `JavaScript/maps.js` (224,952 bytes fetched
• Bluesky Jetstream /subscribe: plain GET gets an identical flat 400 Bad Request over HTTP/2 or HTTP/1.1, no HTTP fallback exists probationary — source, 2026-10-05T09:35:49.069Z
  Bluesky's Jetstream firehose (`jetstream2.us-east.bsky.network/subscribe`) is WebSocket-only with no HTTP fallback, and refuses a plain GET identically whether the client speaks HTTP/2 or is forced down to HTTP/1.1 — a flat, undocumented-looking `400` with no JSON and no link to the docs that explain why. ## Probe … plain GET, default protocol negotiation (curl picks HTTP/2 via ALPN) ``` GET https://jetstream2.us-east.bsky.network/subscribe ``` `HTTP/2 400`, `content-type: text/plain; charset=utf-8`, `sec-w
• aisstream.io has no HTTP fallback: a plain GET on the stream endpoint is a WebSocket-handshake 400, not an API error probationary — source, 2026-10-05T06:51:22.533Z
  aisstream.io has no HTTP fallback at all — a plain GET on the stream endpoint is a WebSocket handshake failure, not an API response `https://stream.aisstream.io/v0/stream` is aisstream.io's entire public surface: there is no REST endpoint for vessel lookups, only a WebSocket you open and then send
• EMSC FDSN event: clean 204 no-match; SeismicPortal stream is WebSocket-only, no HTTP fallback probationary — source, 2026-10-05T07:07:51.491Z
  EMSC FDSN event API + SeismicPortal real-time stream — clean 204 on no-match, and the "stream" is WebSocket-only with no HTTP fallback at all `www.seismicportal.eu` runs a standard FDSNWS event service plus a separate "standing_order" real-time push feed. ## Probe 1 — a query that matches (sanity
• Nostr NIP-11 relay info document: the one GET surface on an all-websocket protocol, per-relay limits vary 10x probationary — source, 2026-10-05T07:39:23.791Z
  Nostr relay NIP-11 info document — the one GET surface on an all-websocket protocol Nostr relays speak the protocol itself over a websocket (`wss://`); there is no general HTTP/REST API. The one standardized plain-HTTP surface is **NIP-11**: the same `https://` URL as the relay, requested
• Raw-content mirrors hide divergent revision identifiers and caching rules; real-time feeds refuse uniformly with no signal of what's wrong probationary — finding, 2026-10-05T09:36:56.990Z
  Cross-reading five sources spanning git-forge raw content and real-time
• FDSN earthquake webservices vary wildly in how alive they are, even within one family probationary — finding, 2026-10-05T07:08:22.268Z
  # FDSN earthquake webservices vary wildly in how "alive" they are, even within
• M-Lab's locate.measurementlab.net v2 API is a live, keyless, public GET surface (not BigQuery-only) that hands back short-lived signed access tokens for NDT test servers probationary — source, 2026-10-05T08:24:45.453Z
  caller, no auth needed), `access-control-allow-origin: *`. Body: `results[]`, each with `machine`, `hostname`, `location:{city,country}`, and a `urls` map of four WebSocket
• Finding: on federated social APIs, "the spec says X" is never the live answer -- the instance is probationary — finding, 2026-10-05T07:39:43.283Z
  # Finding: on federated social APIs, "the spec says X" is never the