Repository navigation
fix(search): drop 1337x, now behind a browser challenge on every mirror - #211
Merged
Merged
Conversation
Every 1337x mirror torlink tries (1337x.to, 1337x.st, x1337x.ws, 1337xx.to) answers a Cloudflare JavaScript challenge, which no plain HTTP client passes, so the source has been down for every search and counted twice in the TUI's "sources down" (its Movies and TV entries). A permanently red source hides a real outage of the others, and the README promised a provider that cannot work. BitTorrented stays: it is invite-only today, not gone, and comes back on its own if that changes. Old history rows from either keep rendering through sourceStyle()'s neutral fallback.
The HTTP API gets its own heading instead of hiding under "Sharing something of your own", and the interface-binding subsection says what it does in a few lines and points at --help for the rest. The limits it used to spell out (IPv4 only, DNS through the OS resolver, update's git/npm children unbound) move into --help, next to the flags.
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
ThreatCrush Security Scan0 finding(s) No findings. |
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
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.
What and why
Every 1337x mirror torlink tries (
1337x.to,1337x.st,x1337x.ws,1337xx.to) answers a Cloudflare JavaScript challenge (cf-mitigated: challenge, the "Just a moment" page), which no plain HTTP client passes. The source has therefore been down for every search and counted twice in the TUI's "sources down" (its Movies and TV entries). A permanently red source hides a real outage of the others, and the README promised a provider that cannot work, so it goes. Nothing else changes for the Movies and TV tabs: YTS, The Pirate Bay, EZTV and BitTorrented stay.BitTorrented stays deliberately: its API answers 401 "invite only" today, which is a policy on their side, not a dead site, and it comes back on its own if that changes. Old history rows from either source keep rendering through
sourceStyle()'s neutral fallback.The second commit tidies the README's headless section so it reads in one pass: the HTTP API gets its own heading instead of sitting under "Sharing something of your own", and the interface-binding subsection says what it does in a few lines and points at
--help, which now also carries the limits (IPv4 only, DNS through the OS resolver,update's git/npm children unbound).Checked live from a sandbox: every other source answers (apibay, eztvx.to, nyaa.si, subsplease, fitgirl-repacks.site, YTS); a headless
torlnk searchon this branch reports eight sources with only BitTorrented failing.Checklist
npm run typecheckis cleannpm testpassesHELP_GROUPSandfooterHintsinsrc/ui/keymap.ts(no key added)Storefield, I updatedmakeStoreinscripts/render-previews-impl.tsx(noStorefield added)feat:/fix:/docs:/chore:)Generated by Claude Code