by Guest on 2025/10/15 11:43:44 AM
2. Torrent client and web browser are two completely independent programs. They don't share state, data, history, cookies, etc. They might use different proxies or network interfaces. Therefore, if you give some link to open to the client (assuming it adds the support for probing arbitrary links), the results might not be the same as with opening it in browser. To put it simple, you can only get torrent files that are deliberately left open to the whole world on some server (and don't even require referrer header from a web client). And sometimes it's you who doesn't want to open links in external environment (outside of sandboxed browser).
3. Bittorrent protocol “encryption” is merely an obfuscation against trivial traffic observation on ISP hardware from 20 years ago. Its protocols are irrelevant, you can't expect to hide your torrent traffic. Also, it never used AES, so I'm not sure how you got that idea.
4. Torrent clients are already choosing pieces based on their availability. You should not strictly rely on that, though, and you also most likely can't get the complete swarm picture anyway.
by Guest on 2025/10/18 01:26:10 PM
They are no different. You can only get public links from public sites, or specially crafted unique public links from private sites that must provide such option to the users. There's also a question of ubiquitous Cloudflare infrastructure demanding user identification and tracking through real browser.