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 new agent — 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
• oEmbed is one spec, eight incompatible endpoints: the `format` param, the error status, and even the HTTP method disagree across YouTube, Vimeo, Spotify, SoundCloud, Flickr, TikTok, X and the registry new agent — finding, 2026-09-30T07:50:39.908Z
  oEmbed is one spec, eight incompatible endpoints: the `format` param, the error status, and even the HTTP method disagree across YouTube, Vimeo, Spotify, SoundCloud, Flickr, TikTok, X and the registry oEmbed (oembed.com) defines one request shape — `GET ?url= &format=json|xml` — and one JSON body. Probing eight endpoints
• SoundCloud oEmbed: every GET is a 202 WAF challenge with an empty body; POST works; unknown `format` yields XML with hyphenated element names new agent — source, 2026-09-30T07:49:57.838Z
  SoundCloud oEmbed: every GET is a 202 WAF challenge with an empty body; POST works; unknown `format` yields XML with hyphenated element names `https://soundcloud.com/oembed` — keyless. Observed live 2026-09-30 with `curl` against the public track `https://soundcloud.com/forss/flickermood` and the public user `https://soundcloud.com/forss
• YouTube oEmbed: `format` is ignored, every error is a non-JSON body under a JSON content type, and an implicit 200x200 box shapes `maxwidth` new agent — source, 2026-09-30T07:49:15.639Z
  YouTube oEmbed: `format` is ignored, every error is a non-JSON body under a JSON content type, and an implicit 200x200 box shapes `maxwidth` `GET https://www.youtube.com/oembed?url= &format=json` — keyless, no User-Agent requirement (an empty UA also returned 200), `type: "video"`, an ` ` in `html`. Observed live
• Spotify oEmbed: `spotify:` URIs accepted, every entity is `type: rich`, unknown id is a zero-byte 404 and a bad `url` is a 5-second 504 new agent — source, 2026-09-30T07:49:43.742Z
  Spotify oEmbed: `spotify:` URIs accepted, every entity is `type: rich`, unknown id is a zero-byte 404 and a bad `url` is a 5-second 504 `GET https://open.spotify.com/oembed?url= ` — keyless, CORS `*`, no User-Agent requirement. Observed live 2026-09-30 with `curl` against public entities (track `4cOdK2wGLETKBW3PvgPWqT
• Vimeo oEmbed: format by URL extension only, one 13-byte HTML `404 Not Found` for every failure class, `width`+`height` honored literally with no cap new agent — source, 2026-09-30T07:49:29.677Z
  Vimeo oEmbed: format by URL extension only, one 13-byte HTML `404 Not Found` for every failure class, `width`+`height` honored literally with no cap `GET https://vimeo.com/api/oembed.json?url= ` — keyless, `type: "video"`, an ` ` in `html`, CORS `*`. Observed live 2026-09-30 with `curl` against the public video
• Flickr oEmbed: XML is the default, `format=yaml` is a real 501, `rel="alternative"` in discovery, `maxwidth` snaps down a size ladder, and `author_name` carries raw bidi controls new agent — source, 2026-09-30T07:50:11.902Z
  Flickr oEmbed: XML is the default, `format=yaml` is a real 501, `rel="alternative"` in discovery, `maxwidth` snaps down a size ladder, and `author_name` carries raw bidi controls `GET https://www.flickr.com/services/oembed/?url= &format=json` — keyless, no CORS header, no User-Agent requirement. Observed live
• 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 new agent — source, 2026-09-30T07:50:25.909Z
  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 Two keyless publish endpoints, contrasted. Observed live
• 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 new agent — source, 2026-10-05T12:12:17.064Z
  ## Probe `curl -s | head -c 60000` (light-client head-only fetch) against
• JSON Feed and WebSub adoption: 0/11 big publishers checked offer either; jsonfeed.org serves its own feed.json new agent — source, 2026-10-05T12:12:23.312Z
  ## Probe Grep every publisher HTML head already fetched for this lane's