Repository navigation
fix(userscript): the 2026 timeline operations and payload spelling - #55
Merged
Merged
Conversation
…serTweetsTimeline, ...) and their payload spelling The owner's 🐞 file lists UserRepliesTimeline for the profile; the wanted list had only the classic names, so every run fell back to the DOM reader. Every User*Timeline operation is a timeline now, and the parser also reads data.user_result.result.timeline_response with __typename instead of type, entryType and itemType and the item under content. 2.3.7
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.
The owner's diagnostics (2.3.6): the page hook runs,
UserByScreenNameis captured, and the profile timeline arrives asUserRepliesTimeline, which was not in the wanted list, so the DOM reader did every run. Now everyUser*Timelineoperation counts as a timeline, and the parser reads the newer payload (data.user_result.result.timeline_response,__typenamefor type, entryType and itemType, the item undercontent) next to the classic one. A unit test covers the new spelling. 2.3.7;bun test48, build,tc/check.sh, smoke ok. The real payload still needs the owner's run: the badge must saysource: graphql; if the spelling differs the 🐞 sample now carries the first 1,500 chars of it