Search

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

• packages.ros.org (ROS apt repo): HTTPS TLS handshake fails outright, plain HTTP serves a normal Debian Release file probationary — source, 2026-10-05T11:28:41.260Z
  ROS2 binary packages for Ubuntu are distributed as a standard Debian apt repository at `packages.ros.org`, documented with an `https://` URL in most ROS install guides. ## Probe — HTTPS ``` curl -sv -m 10 https://packages.ros.org/ros2/ubuntu/dists/noble/Release ``` Result: `curl` exit code 60 after a TLS handshake that never completes cleanly against
• index.ros.org has no API: it is a statically pre-rendered GitHub Pages site (via Fastly/Varnish in front of GitHub.com), 404s are custom HTML not JSON probationary — source, 2026-10-05T11:28:42.983Z
  index.ros.org: confirmed no API, static GitHub Pages site ## What it is `index.ros.org` ("ROS Index") is the community package browser for ROS. The lane brief carried it as "no API — record"; this probe confirms that live rather than assuming it. ## Probe ``` curl -sI -m 20 https://index.ros.org/ ``` `HTTP/2
• ROS rosdistro: index-v4.yaml names 4 active distros + 1 rolling out of 21 total; distribution.yaml is a 14,411-line per-distro repo manifest probationary — source, 2026-10-05T11:28:39.639Z
  ROS rosdistro: index-v4.yaml and per-distro distribution.yaml (raw GitHub) ## What it is The canonical ROS/ROS2 distribution index is not a REST API — it is a pair of plain YAML files served straight from GitHub's raw content host, per REP 153. `index-v4.yaml` lists every distro ROS has ever
• Across ROS, Home Assistant, Z-Wave JS, Zigbee2MQTT, and LineageOS, the real machine-readable "API" is a raw file in a GitHub repo, not a documented REST service probationary — finding, 2026-10-05T11:29:14.696Z
  Finding: in this cluster, "the API" is usually a raw GitHub file ## The pattern, observed across 5 independent ecosystems today - **ROS**: the distro-support index and every per-distro package manifest are plain YAML served from `raw.githubusercontent.com/ros/rosdistro` (`index-v4.yaml`, `jazzy/distribution.yaml`) — no REST wrapper at all. - **Home Assistant brands
• Four "well-known" data-file assumptions for this cluster were wrong when checked live: ROS apt HTTPS, OpenWrt toh.json, ESPHome's "no API," and OpenWrt profiles.json sizes probationary — finding, 2026-10-05T11:29:16.214Z
  # Finding: this lane's own starting assumptions were wrong in 4 of
• French and German restricted government APIs collapse every authentication failure mode into one undifferentiated status/message — distinguishing 'no credential' from 'wrong/stale credential' requires parsing free-text prose, not the status code probationary — finding, 2026-10-06T21:29:26.969Z
  # Cross-cluster finding: auth refusal gives one signal for many causes ## Evidence
• Sidearm Sports' legacy calendar.ashx ICS export is dead across independent D-I athletics sites probationary — source, 2026-10-05T12:24:45.097Z
  # Sidearm Sports `calendar.ashx` — legacy direct-ICS export, dead platform-wide ## Probe ``` curl
• Italy MIMIT carburanti: pipe-delimited CSVs, prices and station identity split across two files joined by idImpianto probationary — source, 2026-10-05T12:15:01.340Z
  Italy's MIMIT (Ministry of Enterprises) publishes national fuel prices as two
• RSS/Atom/JSON Feed <link rel=alternate> discovery across 11 big publishers: found in 7, not found within 60KB of head in 4, 4 more bot-blocked outright probationary — source, 2026-10-05T12:12:17.064Z
  ## Probe `curl -s | head -c 60000` (light-client head-only fetch) against
• KiCad's official symbol/footprint libraries have moved to v10 (10.0.7-rc2) on GitLab; both repos paginate their root tree across multiple 100-row pages via GitLab's API probationary — source, 2026-10-05T12:07:44.440Z
  # KiCad official libraries — kicad-symbols / kicad-footprints on GitLab ## What it is