[twtdata]

Thanks for merging SnapDataHub in #40. This adds one X (Twitter) entry next to getdaytrends and Trendsmap, in the same format.

What it covers: trending topics by country and city at https://twtdata.com/twitter-trends/, plus a dated archive with one page per location and day (for example https://twtdata.com/twitter-trends/brazil/10-18-2026/). For recent days each topic shows its best position and hours on the list, which helps date when a hashtag took off in a given country. The trends pages are free with no account, hence Free: true. Follower and tweet exports on the same site are paid.

Disclosure: I work on twtData.

While checking nearby X entries today (19 Oct): https://tweetbeaver.com/ now redirects to a betting site (jbo88b.com), and searchfortweets1.com and onemilliontweetmap.com do not load. Happy to send a separate PR removing them.

[atiilla]

Merging. Entry is well-formed and correctly placed next to getdaytrends and Trendsmap, and it is one of the few entries in that file with a real description rather than No description. Thanks for the disclosure — that is the right way to submit a tool you work on. Link check passes.

I verified the three rotted entries you flagged, and all three are confirmed:

tweetbeaver.com        301 -> https://www.jbo88b.com/vn/   (betting site)
searchfortweets1.com   no response
onemilliontweetmap.com no response

TweetBeaver is the serious one — a repurposed domain now redirecting to a gambling site, listed as a vetted OSINT tool. That is the same failure mode as the parked typosquat removed from the username catalog earlier. Please do send that PR; all three are in public/tools/social-media-intelligence.md at lines 302, 332 and 368. If you would rather not, say so and I will take it.

Worth noting that the link check only started reporting your one new URL as of #44, which landed a few minutes ago. Before that it validated every URL in the file you touched, which is why your first run failed on 12 dead and 4 parked links that had nothing to do with your change. Nothing you did wrong.

[atiilla]

Following up on the three rotted entries you flagged — I went ahead and removed them rather than leaving you to send a second PR: #45.

All three re-confirmed immediately before removal:

tweetbeaver.com         301 -> https://www.jbo88b.com/vn/
onemilliontweetmap.com  no response
searchfortweets1.com    no response

TweetBeaver was the one worth moving on quickly. The entry dates from August 2025, when it was a real tool, so the domain has since been picked up and repointed at a betting operator — exactly the kind of thing a directory of vetted tooling should not be routing people to. Thanks for spotting it; that is a genuinely useful report, and it is the second time this catalog has had a listing quietly turn into something else.

Your report also exposed two blind spots in our link checker, which is the more valuable outcome. TweetBeaver returns 200 once the redirect is followed, and our parked-domain heuristic only looks for parking nameservers and ww\d+.* hostnames — it does not treat "redirects to a completely different registrable domain" as suspicious. The other two fail DNS, and our error classifier reads err.message, which undici always sets to the generic "fetch failed" while the real ENOTFOUND sits in err.cause.code, so DNS failures were being bucketed as non-fatal. In other words the weekly sweep would have passed all three indefinitely. Both are being fixed.

No action needed from you. Thanks again for the entry and the heads-up.