There just aren’t many german torrents, at least on public trackers. Might be because of this law firm that constantly sends out letters asking for hundreds of euros per infringement.
I’ve had more luck with Usenet, especially the indexers SceneNZBs and DrunkenSlug. The former is a collaboration with the forum House Of Usenet, which gives me almost always the result I want (e.g. remux, german english dual language).
Automation with *arr works great, but it’s not the type of search and play like with Torrentio + real-debrid. Downloading the entire movie/show takes time depending on the bandwidth.
I am very new to the whole torrenting and stremio thing, so I have basically no clue how to utilise any new indexers. I just looked up what it actually means and as far as I understand, they are the tools to find suitable torrents for the target media, is that right? So, is the goal here is to replace Torrentio and hook it up to stremio by itself?
Because the setup has to be cheap and secure, I will probably have to rely on RD and I am not aware of any way to use its service outside of Torrentio.
Or does switching to the *arr alternatives provide enough security while living in Germany. I am really not looking forward to getting annoying letters for any leaking.
Indexers are search engines for usenet, just like trackers allow for searching for torrents. You’re curently using torrent trackers through Torrentio, which downloads the torrents through RD. RD then streams the media to you. This is convenient but as far as I know only works with public trackers, since most private trackers require you to directly upload as much as you download.
Yes, the *arr apps download the requested media through torrent or usenet. They usually run on a server (old laptop, RPi, …). They allow for searching and then automatically downloading content in the right resolution, language and size through torrents or usenet. This downloaded media might then be watched through Jellyfin or Kodi.
If you use torrents directly (public or private), always use a VPN in Germany. Downloading through usenet isn’t a big risk without VPN, just like torrents with RD isn’t risky either. Using *arr with torrents means a VPN is necessary to avoid unfriendly letters.
So, is the goal here is to replace Torrentio and hook it up to stremio by itself?
I don’t know whether Usenet works with Streamio but there might be a plugin. It might be that Streamio just doesn’t work well for german content.
Sorry, it’ll be difficult beating Streamio + RD in ease of use and cost. I’m using *arr and Jellyfin which means I have a server (desktop pc) with a big HDD running 24/7. Since I’m using usenet the cost of indexer and provider comes on top.
The setup just ain’t right for me. I am extremely happy with the simplicity RD provides and I don’t want to actually store the media on my hardware, nor am I looking forward to letting my PC run throughout most of the day, just so my family can watch whenever they want.
I guess I will have to accept that I will not be able to reliably get German sources with my setup. I am glad that my family is bilingual and therefore is also happy with watching movies in Russian, which provides more than enough public trackers. Though most current movies don’t actually have proper voice dubs and rely on fan dubs because of the current political situation I think.
Yes, one of the main reasons I set up *arr was that I have a server running anyway, so I better put it to good use. RD seems gets mentioned a lot and after trying it out for a few weeks the value and simplicity is great.
Glad to hear that you’re family is bilingual as I won’t get far with english only with mine. That’s a major reason I switched to usenet as it’s easier to find dual language content than getting into private trackers.
check one of my previous comments on my profile. the provider I mentioned has french channels for ~20eur/year. in my comment a mention a new box I bought but before that I was using the service on a mi box given by my ISP
I use automatic torrent management mode with qBittorrent for most things and set it to seed every torrent for 40 days (iirc). If I had unlimited storage space, I’d probably seed forever, but I found that 40 days works well for me.
Also, don’t use a Debrid service. These services just leech requested torrents and then instantly stop seeding (if they even upload during download, not sure). This is bad for torrent health on public trackers, and will quickly get you banned on private trackers.
If you seed from the same drive where you store your files, learn the art of hardlinking any torrents you’ve downloaded (that don’t require unpacking), and you can seed without taking up too much more space on your drive.
Hard links are essentially links that point to the same file. When one link is deleted, the other still exists and it is only when the last hard link is deleted that the underlying file is actually deleted.
I don’t put it on my router because there are certain things it would kind of mess with (for example: Netflix on the TV would get all weird and restrict content if it goes through a VPN, I assume it’d slow down online gaming on the Playstation and I don’t really care if that’s anonymous or not and so on.) I could probably split tunnel that stuff, but for me it’s just easier to run it locally on the things I think need it (my laptop, phone etc.) than figure all that out.
That’s just me though, it really all depends on your preferences/threat model I guess.
For animated content, 𝚗𝚢𝚊𝚊.𝚜𝚒 (as mentioned by @sbs1313)
For general Asian movies and stuff, 𝚊𝚟𝚒𝚜𝚝𝚊𝚣.𝚝𝚘, although since it’s a private tracker you’ll need to keep an eye out for open signups - they have a discord waitlist where you can get notified
There’s very little info to work with so it’s unlikely you’ll receive any specific advice.
But mainly you do want to be fully connectable (port forwarded) so check that. Go to any port test website (www.canyouseeme.org, www.yougetsignal.com/tools/open-ports/, etc.) and enter your torrent client’s incoming connection port there. (for qBittorrent that is in Tools / Options / Connection / Listening Port)
If that test fails then you need to figure out what is blocking your torrent client’s incoming connection port.
If you’re using a proxy that’s the issue, won’t get an incoming connection port via proxy
If you’re using a VPN service that does not support port forwarding then that’s the issue, it is impossible to port forward on a VPN without port forwarding support
If you’re using a VPN service with port forwarding support then go to their website & figure out how to configure it, each VPN service is slightly different
If you’re not using a VPN/Proxy then most likely you’ll need to log into your network router/firewall & configure a port forward there. Basically create a port forward for your torrent client’s incoming connection port & point it to your local system on the network (your NAS)
Also make sure to whitelist your torrent client in any anti-virus/malware software you are using, those will definitely slow you down and/or block connections to your torrent client.
There’s potentially other issues but everyone starts with being connectable first.
Was to lazy to change instances even though .world was always down. Actively censoring made me finally pull the plug. Thanks for helping me out I guess
Can someone explain to me what port forwarding in the context of torrenting is about? I use qbittorrent and nordvpn in docker containers and have never exposed/forwarded a port but get more than adequate upload/download speeds.
Port forwarding allows you to bypass your NAT firewall which will naturally block all unsolicited traffic on a closed port. What that means for a torrent download is peers cannot introduce themselves to you and create a new connection, you can only connect to active peers who have their ports open.
Just to add more background to that, before your torrent can begin downloading pieces from various peers, you need to know the address of the peers sharing the pieces you need. Typically that is handled by the tracker and/or DHT. A tracker acts as sort of a logistics middle-man. It helps facilitate efficient transmission between peers by tracking what each peer has and needs. If peer B needs piece X, the tracker will supply peer B with the address to peer A who has piece X. Assuming peer A has their incoming port open, they will accept the request for piece X and send it to peer B. If their port is closed, the request will simply be denied and no traffic will be shared between the peers. The tracker’s address, as well as the data hash and some other misc data is coded into the torrent file. DHT is a little more unique and complicated. It is a fully distributed hash table on a P2P network and does not rely on a tracker at all, it’s strictly P2P. The only little catch to that is to initially introduce yourself into the network you need to bootstrap your connection using some hardcoded addresses, often from a very centralized source. Port forwarding becomes much more important for DHT because after the initial bootstrap, there is no middle-man, it’s strictly peer to peer and by having your ports closed, your client can’t effectively communicate across the network. Without two-way communication across peers, your client will generally be stuck with a very limited pool of peers it can communicate with. Magnet links as well as most torrent clients utilize DHT.
One reason it’s not so noticeable these days when ports are closed is because many torrent peers exist in big data centers with virtually unlimited bandwidth. When torrents were still young, most if not all peers were hosted on consumer grade hardware at a residence so you needed every connection you could get.
If your torrent download happens to be a well-known Linux ISO, chances are very likely that there will be at least two or three peers you’ll connect to that exist in a data center, they will most likely account for 80%+ of your download speed.
Blocking ports ultimately hurts seeding the most which can effect the overall “health” of a torrent. Say a peer labeled A can’t connect to those giant data center peers for whatever reason, they now have to seek out other peers that may have the data they are looking for. If all the other peers have their ports closed, well then the torrent is essentially dead for peer A and they’ll have to either wait for someone with open ports to come online and start seeding or search for an entirely new torrent.
Sorry, this was a bit of an on-the-go mind dump so please anyone correct me if I’m wrong anywhere here but that’s pretty much the gist of port forwarding in the context of torrenting.
When torrenting your client should be “Connectable” which means fully accessible from others. You can use the guides others have posted to achieve that but basically, an unconnectable client can still seed to those who are connectable, but two unconnectable clients cant connect to each other. Or at least this is how it has been described to me by a private tracker.
piracy
Najstarsze
Magazyn ze zdalnego serwera może być niekompletny. Zobacz więcej na oryginalnej instancji.