Repository navigation
AudioSpaceById: a sample space that resolves; metadata required again; title and tweet_results optional - #146
Merged
Merged
Conversation
… 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>
This was referenced Nov 17, 2026
Merged
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #145, which made
AudioSpace.metadata/participantsoptional 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 ofmetadata. This PR replaces the sample and takes that part of #145 back.Observed (the placeholder's request, sandbox account)
metadataandparticipants(7 running, 17 ended, with and without replay), 10 answer{"data":{"audioSpace":{"is_subscribed":false}}}. A made-up id answers the same 47 bytes.1qxoNYAlYMXJv, recorded on 10-17, is one of the 10 that do not, and it still answered in the nightly of 11-16.metadataas well.1yNGabwXqXnJjshows the space card and receivesmetadata; the page of1qxoNYAlYMXJvshows "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_enabledistruein Chrome), which is left to the next catalog update.1qxoNYAlYMXJvno uncaught exception and no console error that the page of the resolving space does not log too. Inbundle.AudioSpacePeek.f9837f63e496cbd9a.jsthe message is a branch of its own:if (is.error) returna sheet with a headline and a close button, before the card is built.metadata,titleis absent in 2 andtweet_resultsin 1. Every other required key is present in all of them.Changed
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/participantsare 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.titleandtweet_resultsare optional.Against the spec before #145, the
AudioSpace*schemas differ only in those two optional keys.Verified with the regenerated strict client
metadatavalidate 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.Not verified
AudioSpace*schemas and this sample.🤖 Generated with Claude Code