fix(twitter): restore intercepted readers - #9
Merged
Conversation
Align the collect step with AutoCLI’s interceptor buffer, accept current X timeline_v2 user timelines, and use the supported scroll option names for notifications.
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.
Summary
Restore the reader-side subset of upstream AutoCLI PR nashsu#65 on top of the current fork main.
This ports the already-tested fixes from the old
fix/twitter-upstream-syncbranch without bringing the unrelated reply changes:CollectStepread and clear AutoCLI's actual interceptor buffer,window.__autocli_intercepted__opencli_interceptedtimeline_v2payloads in followers/following while retaining the legacy fallbackscroll.count/scroll.delayfields in notifications/followerstimeline instead of/verified_followersProvenance
Reader fix originally landed as
2758e4con the old PR nashsu#65 branch, followed by the followers timeline fix4208b67. Those commits never entered this fork'smain, which is whytwitter notificationsregressed to[]after returning to main-based builds.This PR reapplies only those reader changes onto current
main @ 59f357d.Validation
node --checkadapters/twitter/followers.yamladapters/twitter/following.yamladapters/twitter/notifications.yamlcrates/autocli-pipeline/src/steps/browser.rsThe current VPS maintenance lane no longer has a Rust toolchain installed, so Rust compilation/tests are left to repository CI rather than installing a new toolchain ad hoc.