Remove defunct mastodon.cloud instance #2579
Conversation
The mastodon.cloud instance appears to be defunct as both existing and non-existing usernames redirect to the same error page. This causes false positives in username detection.
dollaransh17
changed the title
|
Site is live and results return as expected (was possibly just down for a while?) |
@ppfeister I've restored mastodon.cloud as you mentioned it's working, but I'm still seeing both valid and invalid usernames redirect to the same page: Valid user: https://mastodon.cloud/@TheAdmin → redirects to https://media.mastodon.cloud/cloud-093img.html Invalid user: https://mastodon.cloud/@nonexistentuser12345 → also redirects to same page This causes Sherlock to report both as 'Found' since they return same 301 status. Could you double-check if you're seeing different behavior? Maybe it's regional or the instance was temporarily down when I initially tested?
|
Seems to be regional. Testing it being conducted within the USA. This may be resolvable by way of #2597, which added support for multiple errorTypes. Let's see... |
|
Can you try (or Please ensure you're using the latest state of |
@ppfeister Excellent fix Test Results using your fix branch: Output: Your solution is brilliant , handles regional differences |
|
Just to be clear, did you mean Not Found for those items? Found would mean we still have false positives being returned. |
@ppfeister You're absolutely right , my apologies for the confusion Correction: All three test usernames are showing as "Found" which means false positives are still occurring |
|
Perfect. This one will have to remain as-is for now, as merging this fix will break existing installs. However, it will be corrected eventually after 0.17.0 is released with the new schema. |
In the meantime, should I, |
|
May as well, yeah |
The mastodon.cloud instance appears to be defunct as both existing and non-existing usernames redirect to the same error page. This causes false positives in username detection.