feat: add Motherless email and username scan modules#423
Merged
Conversation
Add email-based check via /register/checkemail (email_scan/adult) and a username check via /register/checkusername (user_scan/adult), both using the site's field-availability endpoints on the current motherless.xxx domain. Hits key off the not-available/available response class, with an "invalid" guard separating rejected input from real matches.
kaifcodec
added
the
need-extra-changes
The checkusername endpoint only reports availability, so on a hit fetch the public member page and capture every field it renders via Result.taken(extra=...): the profile-stats block (joined, last seen, profile views, sexuality, favorite porn, website, upload/friend/subscriber counts, etc.), the member-info block (gender, relationship, location) and the avatar.
kaifcodec
added
the
user module addition
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.
What
Adds Motherless to both scan modes — an email module and a username module.
How it works
Both use the registration form's field-availability endpoints (single unauthenticated POST each, no Turnstile required) which return a small HTML snippet:
Email —
POST /register/checkemail(body:email):class="available""email address is available"class="not-available""already used"class="not-available""Invalid Host."Username —
POST /register/checkusername(body:username):class="available""username is available"class="not-available""Username not available."class="not-available""Username is invalid."Both key off the
not-available/availableresponse class, with an "invalid" guard so rejected input isn't misreported as a hit. The username module's user-facingshow_urlpoints at the profile page/m/{user}.Notes
.comdomain; holehe has none.Testing
motherless.xxx:brunolm7@gmail.com→ Registered andbrunolm→ Found; throwaway email/username → Not Registered / Not Found.pytest tests/: all pass except 2 pre-existing Windowschmod(0)no-op tests, unrelated to this change.