Repository navigation
Remove three rotted X/Twitter catalog entries - #45
Merged
Merged
Conversation
All three verified on 18 Oct 2026: tweetbeaver.com 301 -> https://www.jbo88b.com/vn/ onemilliontweetmap.com no response searchfortweets1.com no response TweetBeaver is the urgent one. The domain no longer hosts the tool; it redirects to a gambling site. The entry dates from 7f23cb4 (Aug 2025), when it was a real tool, so this is ordinary link rot that has since been picked up by someone else. Listing it as a vetted OSINT tool now sends people to an unrelated betting operator. The other two resolve to nothing and are simply dead. Reported by @twtdata while submitting #43, and independently confirmed before removal. Note that the link checker would not have caught any of these: - tweetbeaver answers 200 after following the redirect, and the parked-domain heuristic only matches parking nameservers and ww\d+.* hostnames. A redirect that leaves the registrable domain entirely is not currently a signal. - the other two fail DNS, and probe() inspects err.message, which undici always sets to "fetch failed" while the real code sits in err.cause.code — so DNS failures are classified "other" and do not fail CI. Both gaps are tracked separately; this commit only removes the entries.
Deploying osintelligence with
|
| Latest commit: |
e6c9ca7
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://9eac0115.osintelligence.pages.dev |
| Branch Preview URL: | https://fix-remove-rotted-twitter-en.osintelligence.pages.dev |
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
1 participant
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.
Removes three X/Twitter entries from
public/tools/social-media-intelligence.mdthat no longer point at the tools they claim.Verified 18 Oct 2026:
tweetbeaver.com301→https://www.jbo88b.com/vn/— a gambling siteonemilliontweetmap.comsearchfortweets1.comTweetBeaver is the reason this is not just tidy-up. The domain no longer hosts the tool and now redirects to an unrelated betting operator. The entry dates from
7f23cb4(Aug 2025), when it was genuine, so this is ordinary link rot that someone else has since picked up — the same failure mode as the parked typosquat removed inc8aac72. A directory whose value is vetted tooling should not be routing people there.Reported by @twtdata while submitting #43, and independently confirmed before removal.
Why CI did not catch this
Neither failure mode is currently detected, which is the more useful finding:
200after the redirect is followed. The parked-domain heuristic inscripts/validate-links.jsonly matches parking nameservers andww\d+.*hostnames;jbo88b.comis neither. A redirect that leaves the registrable domain entirely is not treated as a signal.probe()inspectserr.message, which undici always sets to the generic"fetch failed"— the realENOTFOUNDsits inerr.cause.code. So every DNS failure is classifiedotherand does not fail the build.So the weekly sweep would have passed all three. Both gaps are tracked separately; this PR only removes the entries.
Validation
npm run validateclean · 7/7 tests pass ·npx tsc --noEmitclean