feat: add TripAdvisor username scan module#428
Closed
brunolm wants to merge 1 commit into
Closed
Conversation
Contributor
Author
|
DataDome |
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.
Adds a username-existence scan module for TripAdvisor.
How it works
GET https://www.tripadvisor.com/Profile/{username}viageneric_validate(mirrorszomato.py)./Profile/...(TripAdvisor case-canonicalizes handles, e.g.travelbug→/Profile/TRAVELBUG, so a redirect to a profile URL still confirms the account exists).Testing
*_unreadabletests fail, and only on Windows).Context
This fills a real coverage gap: Maigret and WhatsMyName check TripAdvisor usernames but user-scanner did not. (Other apparent gaps like Strava/Yelp/Slack usernames turned out to be numeric-ID or workspace-slug checks, not real user lookups.)