Skip to content

fix(data): update InterPals absence string to match current site response#2442

Merged
soxoj merged 1 commit intosoxoj:mainfrom
juliosuas:fix/false-positive-interpals
Apr 3, 2026
Merged

fix(data): update InterPals absence string to match current site response#2442
soxoj merged 1 commit intosoxoj:mainfrom
juliosuas:fix/false-positive-interpals

Conversation

@juliosuas
Copy link
Copy Markdown
Contributor

Problem

InterPals was reporting false positives — claiming users exist when they do not (issue #2433).

The site returns HTTP 200 for both existing and non-existing users, so detection relies entirely on page content matching.

Root Cause

The previous absence string The requested user does not exist or is inactive no longer matches what interpals.net returns for non-existent profiles.

Fix

Updated absenceStrs to match the current site response:

- "The requested user does not exist or is inactive"
+ "User not found"

Testing

Manually verified against live site:

  • interpals.net/noneownsthisusername → returns "User not found" ✓ (correctly detected as absent)
  • interpals.net/blue → returns user profile ✓ (correctly detected as claimed)

Fixes #2433

@soxoj
Copy link
Copy Markdown
Owner

soxoj commented Mar 31, 2026

Thanks @juliosuas! Could you please resolve the data.json conflict? I see that you have added two other sites in this commit. They are in the DB already: https://github.com/soxoj/maigret/blob/main/sites.md

…onse

The previous absence string 'The requested user does not exist or is inactive'
no longer matches the live site response. InterPals now returns 'User not found'
for non-existent profiles, causing false positives for all username searches.

Tested against interpals.net/noneownsthisusername (non-existent) and
interpals.net/blue (claimed) to confirm detection accuracy.

Closes soxoj#2433
@juliosuas juliosuas force-pushed the fix/false-positive-interpals branch from 1fc7a23 to d48037c Compare April 3, 2026 07:04
@juliosuas
Copy link
Copy Markdown
Contributor Author

Rebased on upstream main and resolved the conflict. Removed the duplicate site entries (infopps.moy.su, iXBT, and the lowercase interpals duplicate) that were already in the database — they were carried over from a previous feature branch merge. The PR now contains only the targeted InterPals absence string fix ("The requested user does not exist or is inactive"" → "User not found"`). Clean single-commit diff against main.

@soxoj
Copy link
Copy Markdown
Owner

soxoj commented Apr 3, 2026

Good job 🤝

@soxoj soxoj merged commit eeb38cc into soxoj:main Apr 3, 2026
4 checks passed
soxoj pushed a commit that referenced this pull request Apr 7, 2026
…onse (#2442)

The previous absence string 'The requested user does not exist or is inactive'
no longer matches the live site response. InterPals now returns 'User not found'
for non-existent profiles, causing false positives for all username searches.

Tested against interpals.net/noneownsthisusername (non-existent) and
interpals.net/blue (claimed) to confirm detection accuracy.

Closes #2433

Co-authored-by: Julio César Suástegui <juliosuas@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Maigret bot] False-positive site probe: InterPals

2 participants