Skip to content

AudioSpaceById: a sample space that resolves; metadata required again; title and tweet_results optional - #146

Merged
fa0311 merged 2 commits into
mainfrom
fix/audio-space-sample-and-title
Nov 17, 2026
Merged

fa0311 merged 2 commits into
mainfrom
fix/audio-space-sample-and-title

Conversation

@fa0311

@fa0311 fa0311 commented Nov 17, 2026 •

Copy link
Copy Markdown
Owner

Follow-up to #145, which made AudioSpace.metadata / participants optional after a single response of the sample space. Sampling other spaces shows what that response was: the answer for an id that resolves to no space, not a change of metadata. This PR replaces the sample and takes that part of #145 back.

Observed (the placeholder's request, sandbox account)

  • 2026-11-17, 34 space ids taken from posts between 2025-07 and 2026-11-17: 24 answer with metadata and participants (7 running, 17 ended, with and without replay), 10 answer {"data":{"audioSpace":{"is_subscribed":false}}}. A made-up id answers the same 47 bytes.
  • The 22 spaces of the last 31 days all answer. Of the other 12, 2 answer (2026-10-10, 2025-10-09); the old sample 1qxoNYAlYMXJv, recorded on 10-17, is one of the 10 that do not, and it still answered in the nightly of 11-16.
  • With a guest token, without the account, two of the existing spaces answer with metadata as well.
  • Google Chrome with the same session, no clicks: the page of 1yNGabwXqXnJj shows the space card and receives metadata; the page of 1qxoNYAlYMXJv shows "Something went wrong. Please try again later." and receives the 47 bytes. Chrome sends the placeholder's query id and variables; one of the 42 features differs (post_ctas_fetch_enabled is true in Chrome), which is left to the next catalog update.
  • 2026-11-18, the same two pages with the console recorded: for 1qxoNYAlYMXJv no uncaught exception and no console error that the page of the resolving space does not log too. In bundle.AudioSpacePeek.f9837f63e496cbd9a.js the message is a branch of its own: if (is.error) return a sheet with a headline and a close button, before the card is built.
  • In the 24 answers with metadata, title is absent in 2 and tweet_results in 1. Every other required key is present in all of them.

Changed

  • The sample id is 1yNGabwXqXnJj, a Binance space of 2025-10-09 that still answers. X's own accounts link four spaces and none of them resolves.
  • AudioSpace.metadata / participants are required again, as before Nightly 2026-11-17: a space that is gone, a cashtag in a Community Note #145: the web client treats an answer without them as a failure, and a sample that stops resolving fails the nightly instead of passing with nothing checked.
  • AudioSpaceMetadata.title and tweet_results are optional.

Against the spec before #145, the AudioSpace* schemas differ only in those two optional keys.

Verified with the regenerated strict client

  • Of the 35 saved answers, the 25 with metadata validate at exactly 1.0 and the 10 without fail (ValidationError: metadata, participants). The six answers Chrome received behave the same: two at 1.0, four of 47 bytes fail.
  • A live GET of the new sample with the harness's request (2026-11-18): 1.0.

Not verified

  • The full strict run was not repeated on this branch; the one of 2026-11-17 ran on 37b4afd (130 calls at 1.0), and this change touches only the AudioSpace* schemas and this sample.
  • How the web client gets from the 47 bytes to its error flag: that code is in another bundle and was not read.
  • Why 10 spaces no longer resolve, and therefore how long the new sample will: unknown. It has lasted 13 months.
  • Scheduled spaces that have not started and cancelled ones: none sampled.
  • No second logged-in account; the guest token is the only other vantage point.

🤖 Generated with Claude Code

fa0311 and others added 2 commits November 17, 2026 16:48
… optional

The sample space 1qxoNYAlYMXJv no longer resolves (only is_subscribed since the nightly of
2026-11-17), so the call exercised nothing of a space. The new sample is a Binance space of
2025-10-09 that still answers with metadata and participants.

Of 24 spaces that answer with metadata (2026-11-17), 2 have no title and 1 has no
tweet_results; every other required key is in all of them.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
An answer without them is what an id that resolves to no space gets (only is_subscribed,
no errors). The web client shows its error sheet for it (bundle.AudioSpacePeek branches on
the error flag of the space before the card is built), so it is not a space the client can
use, and with both required a sample that stops resolving fails the nightly.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@fa0311 fa0311 changed the title AudioSpaceById: a sample space that resolves; title and tweet_results optional AudioSpaceById: a sample space that resolves; metadata required again; title and tweet_results optional Nov 17, 2026
@fa0311
fa0311 merged commit d31ab31 into main Nov 17, 2026
1 check passed
@fa0311
fa0311 deleted the fix/audio-space-sample-and-title branch November 17, 2026 18:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant