• 0 Posts
  • 24 Comments
Joined 3 years ago
cake
Cake day: June 22nd, 2023

help-circle




  • As part of a websites DNS info they have to provide a TTL (time to live). This value can be just about anything but is often in the 30s to 5m range, and serves as an instruction on how long a client should cache the IP address locally before checking for updates.

    This is because IP addresses can change, and you don’t want to experience hours of downtime for all clients every time your IP changes.

    Every time your client queries your tracker for server updates (every few minutes, give or take, based on tracker preferences) it should follow your system DNS settings, which should involve checking your local cache, then going to the upstream server indicated in your system DNS settings.

    If your system is set to a DNS server outside of your local network (e.g., 8.8.8.8) that request should go through your VPN

    If your system is set to use a local DNS server (e.g., 192.168.X.X…), typically either done through something like a pi-hole, or if your router sets itself as the DNS server then forwards all requests, this MIGHT create a DNS leak around your VPN.

    A good VPN like Mullvad should have an option to force their own DNS settings when enabled to prevent this leak.








  • Is the h264 or x264 part of the name the bitrate?

    No, that’s the encoding algorithm, aka codec. As another person pointed out, AVC/h264/x264 (all different names for what is effectively the same thing) is a lot easier to process than HEVC/h265/x265 (again, different names, same end result).

    Bitrate is just the overall file size divided by the movie duration, basically indicating how compressed the movie is, with compression coming at the loss of finer details. You can generally gauge bitrate based on file size. A 5000 Mb file that is 1000 s long is, on average, 5000/1000=5 Mbps.

    Since you’re very clearly not picky, you’re probably best off going for 720p or 1080p content with small file sizes (1-5 GB / movie). Feel free to download smaller though, if it doesn’t impact your experience, just make a mental note if you ever find anything that is too small for you to tolerate, and set your minimum file size somewhere above that.

    Based on your criteria, you probably want to steer clear of terms like Atmos, TrueHD, DTS-MA, and DTS-X. These are all terms for different flavors of totally uncompressed audio, which alone can be up to 5GB of unnecessary (for you) added disc space for a given movie. Instead you want compressed audio like DDP, AAC, or AC3

    DivX/XVID are really old video codecs, kinda like x264. I wouldn’t fuck with them even with your preferences unless you have no other choice, given your average potato nowadays can handle x264.

    TL;DR, based on your preferences, look for / avoid these terms, but know not all files have all of the same fields identified:

    GOOD

    Video

    AVC/h264/x264

    720p or 1080p

    8-bit (you’ll want this over 10-bit, if specified)

    Audio

    DDP, AAC, or AC3

    Overall

    1-5 GB file size / movie

    MEH

    Video

    DivX/XVID

    Overall

    Be mindful of files smaller than 1 GB / movie, they may be fine for you but this is where you can really start to see some gnarly banding

    AVOID

    Video

    HEVC/h265/x265 or VC1

    2160p

    HDR, HDR10, HDR10+, DoVi, or DV (not mentioned earlier but these need special, more modern, displays)

    Audio

    Atmos, TrueHD, DTS-MA, and DTS-X

    Overall

    Really large or comically small files.


  • Unfortunately quality is entirely subjective. What you may think is fine, I may hate, and vice versa.

    Generally speaking, for a given movie, quality and bitrate are linked, but two movies with the same bitrate likely don’t have the same quality because of a myriad of factors.

    For me, with a few limited exceptions of movies I know like the back of my hand, I have a really hard time distinguishing between a good 4K webrip (15-20 Mbps) and remux (40-80 Mbps), so I have no issue keeping the majority of my library encoded at ~18Mbps

    Unfortunately there’s no quality magic wand, but if you find a release group that does encodes you like, try to get to their home tracker and just let them handle it.

    If you’re good with 1080p non-HDR content, for your use case you probably want to focus on “AVC” aka “H.264” or “x264” encodes of decent bitrate. HEVC yields better quality than AVC for a given bitrate, but comes at the cost of being much more intensive to encode and decode, which may be a source of problems for your 10 y.o. box. If your bar is “tell what’s happening”, you can go to pretty low bitrates.

    Handbrake is a robust piece of software, but it’s really not beginner friendly because the automatic encoder settings will just absolutely ruin whatever you feed it.

    If you’re on windows, check out StaxRip for encoding







  • It’s a poor analogy, but imagine a public IP like a hotel, there can be lots of guests (clients) at this hotel. Hotel policy is they won’t let any outsiders in unless you know the room number (port) of the person you’re trying to reach.

    Imagine you and a friend are staying in separate hotels and want to give each other copies of your favorite Linux .ISOs, but neither of you knows the other’s room number - you show up at the hotel and the front desk tells you to pound sand because you don’t have their room number.

    As long as one of you knows the other’s room number though, you can meet.

    Torrenting without port forwarding means you can only trade your favorite .ISOs with people who have port forwarding enabled (sharing their room number to the tracker), which makes you less effective of a seeder. Enabling port forwarding allows you to share with anyone (sharing your room number with the tracker).