Add x.com URL support to TwitterRipper - #2188
Merged
Merged
Conversation
- Update sanitizeURL regex patterns to accept both twitter.com and x.com URLs - Add canRip() override to match both twitter.com and x.com hostnames - Use non-capturing group (?:twitter|x) to avoid breaking group numbering - Add x.com URL test cases for both user timeline and search Closes RipMeApp#2068 (mega-thread request for x.com support)
soloturn
approved these changes
Aug 8, 2026
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
2 participants
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.
Description
This PR adds support for x.com URLs in the TwitterRipper, in addition to the existing twitter.com support. Since Twitter rebranded to X, many users share x.com URLs that previously failed to rip.
Changes
sanitizeURLregex patterns to accept bothtwitter.comandx.comURLs using non-capturing groups(?:twitter|x)canRip()override to match bothtwitter.comandx.comhostnamesapi.twitter.com) remain unchanged since the API still uses twitter.comTesting
Addresses the x.com support request from issue #2068