feat(Innertube): Add PostManager - #1244
Draft
Illusion137 wants to merge 72 commits into
Draft
Conversation
…eatePost` interface + fetching ytcfg and init attestation + update parser to include a version of `RunAttestationCommand` + create the main logic for `createPost()`
… as an command, just parse it as an action instead of creating a duplicate class
…Continuation` and `FilteredChannelList` should really refactor Actions into a general Actions type
…y grab the `attestation_data` from the `R` component
…nce they are needed for attestation
…nd finish up the creating post sequence
…e data + await attestation_log_response
…age_attestation_cache` and also await the attestation command's botguard_solver
…r `scheduledPublishTimeSec`
…nager.create()` have different return type based on parameters + update posts example
…not Content-Type
…ad check `input_is_raw_url`
Illusion137
marked this pull request as draft
August 19, 2026 01:48
LuanRT
changed the title
PostManager
…otentially binds) + updating HTTPClient to support raw page fetches
…use in attestation challenges
…ager take in a required`content_binding` instead + update the log function to auto support new system
fix(BotGuard): make challenge fetching use new `ChallengeFetchingArgs` instead of `ChallengeSolverArgs`
…o generate `context.user.delegationContext`
…ed by the session
…TOR_STUDIO_ACTION`
…Challenge` args and refactored `client` to be of type `InnerTubeClient`
… add a function to solve the studio session process: `studioSessionToken`
…ResponseData` + rework `studioSessionToken`
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
1 participant
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.
Adds support to create posts via a
PostManagerclass.Noteable changes and features
initialData()function toInnertubewhich takes in a YouTube page url and it extracts both theytcfgandaTn(attestation data). Modifed HTTPClient to support these html page fetches.RunAttestationCommandPostManagerwhich just allows for the creation of postsTesting
Added a single example at
examples/posts/src/index.ts- automatically fetches cookies if you have a chrome browser for easier testing (with caveats), then creates aPostManagerand creates anIMAGE_POLLpost and logs the result.Other Notes
BackstagePostDialogmay be overly long because I tried to include as much stuff also found inhttps://github.com/LuanRT/youtubei-dts.The example is pretty easy to use since it does auto-fetch cookies, although it can be removed since it was just a quality of life for testing. It uses a library that if you have
ChromElevatorinstalled to path on windows, then it gets cookies that way, otherwise it uses a slightly modified version ofchrome-cookies-secure. Again not necessary, just makes things easy for testing./att/logfrom my testing, will return200no matter what, as long as it has the right shape. Not exactly sure if there is a verifiable way to see if theBotGuardSolverthat you pass in is in any way correct. Nonetheless it is still kept in the create post pipeline just in case.Fixes #255