Skip to content

Refresh X UserTweets and SearchTimeline query IDs from current evidence - #102

Draft
0thernet wants to merge 1 commit into
mainfrom
cursor/x-web-feeds-query-id-5f8c
Draft

Refresh X UserTweets and SearchTimeline query IDs from current evidence#102
0thernet wants to merge 1 commit into
mainfrom
cursor/x-web-feeds-query-id-5f8c

Conversation

@0thernet

Copy link
Copy Markdown
Member

Live x-web feeds.read feed:"user" and feed:"search" fail closed before dispatch with:

X query-ID drift for UserTweets:query; reviewed evidence is stale
X query-ID drift for SearchTimeline:query; reviewed evidence is stale

This is the same class of failure as Bookmarks in #60. resolveUniqueXWebBundleDescriptor compares the current first-party descriptor to xWebQueryDescriptorEvidenceSnapshot. The reviewed IDs were still the July main.9929b02a.js values:

  • UserTweets 6r5OLCC_wFH4CpRyXKuAmQ
  • SearchTimeline hz_94eVAtrtQo_vO3my7Rw

Observed 2026-08-29 from https://abs.twimg.com/responsive-web/client-web/main.868c69e3a403a8bda.js (HTTP 200, 1054493 bytes, last-modified 2026-08-28) using the runtime regex:

  • exactly one UserTweets:query with queryId SXVCYB8XHSS25nzIljNtZA
  • exactly one SearchTimeline:query with queryId hyPfJYJ_XAtDYoslQc-Rgg
  • both still live in main; sourceText continues to use the current main bundle when sourceChunk starts with main.
  • declared field toggles remain the reviewed set (withPayments, withAuxiliaryUserLabels, withArticleRichContentState, withArticlePlainText, withArticleSummaryText, withArticleVoiceOver, withGrokAnalyze, withDisallowedReplyControls)

This updates those two evidence rows to the current IDs, sourceChunk: "main.868c69e3a403a8bda.js", and observedOn: "2026-08-29". Adapter and contract versions are unchanged because this is revision evidence, not a semantic-contract change. posts.publish, replies.create, and Made with AI fail-closed behavior are untouched. There is no DOM fallback.

Tests record the new IDs, keep user-feed identity echo, and keep public-text plus over-limit cursor contracts for user and search. A mismatched live ID still fails closed without revealing the new value.

Open in Web Open in Cursor 

Live feeds.read feed=user and feed=search fail before dispatch because
the reviewed UserTweets and SearchTimeline IDs still recorded the July
main.9929b02a.js values. Replace them with the unique IDs from the
current main.868c69e3a403a8bda.js bundle (observed 2026-08-29) and keep
public-text, identity-echo, and over-limit cursor contracts.

Co-authored-by: ben <0thernet@users.noreply.github.com>
@vercel

vercel Bot commented Aug 29, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
wrench Ready Ready Preview Aug 29, 2026 9:50pm

Request Review

@0thernet
0thernet marked this pull request as ready for review August 29, 2026 22:41
@0thernet
0thernet marked this pull request as draft August 29, 2026 22:57
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.

2 participants