Fix LinkedIn detection - resolve HTTP 999 error #2689
+3
−2
Conversation
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
- Updated LinkedIn URL to use www.linkedin.com/in/{} - Added errorCode: 999 to handle LinkedIn's anti-bot response - Fixed false negatives where existing profiles showed as Available - Tested with real profiles: satyanadella, reidhoffman, jeffweiner08 - Resolves Hacktoberfest issue regarding LinkedIn detection failures Fixes #[issue-number]
Automatic validation of changes
|
|
Crazy how easy that was and it just got overlooked. Appreciate the fix! Having some others test real quick, but marking this as accepted in the meantime so you get credit while pending that additional validation. |
1 task
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.
🐛 Problem
LinkedIn was returning HTTP 999 status codes for all profile requests, causing Sherlock to incorrectly classify all profiles as "Available" regardless of whether they actually existed.
🔧 Solution
linkedin.com/in/{}towww.linkedin.com/in/{}errorCode: 999to properly handle LinkedIn's anti-bot response✅ Testing
Verified with real LinkedIn profiles:
satyanadella(Microsoft CEO) - correctly detected as "Claimed"reidhoffman(LinkedIn founder) - correctly detected as "Claimed"jeffweiner08(former LinkedIn CEO) - correctly detected as "Claimed"nonexistentuser999999- correctly detected as "Available"📋 Type of Change
Fixes the LinkedIn detection issue mentioned in recent issues.
Fixes: #2652 (edited to add by @ppfeister)