Fix x.com status ingestion via fxtwitter - #3
Open
onevcat wants to merge 1 commit into
Open
Conversation
Co-authored-by: onevclaw <onevclaw@onevcat.com>
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.
What
x.com/twitter.comstatus URLs (/.../status/<id>), ingest via fxtwitter API instead of fetching HTML directly.# <title>) so the assistant can translate it.apply-translation.mjsrobust whensource.mdhas missing/empty frontmatter (stripundefinedfields + default date).Why
Direct HTML fetch to x.com is often blocked and returns the “Something went wrong…” bot-detection page, producing junk
source.md/prompt and requiring manual retries.Tests
scripts/x-article.mjsand forapply-translation.mjshandling missing frontmatter.npm testpasses.