🇨🇦

  • 24 Posts
  • 509 Comments
Joined 3 years ago
cake
Cake day: July 1st, 2023

help-circle
  • For me, Usenet isn’t about availability; but speed, risk exposure, and convenience.

    Torrents take longer, even with lots of quality seeds and fast network speeds; mostly because of the seeding process. Plus, while you are seeding: you have to publicly expose yourself as a content host, even if just through a VPN. Hosts are what copyright holders target, they don’t GAF about the people downloading, they try to take down the hosts to stop the spread. Finally you have to keep the content you downloaded in the format you downloaded, at least until seeding is done.

    I prefer to use Tdarr to automatically transcode downloaded content into h265 (HEVC) to reduce it’s size. Most content is found in h264 (AVC); converting it, on average, reduces its size by ~30% while maintaining good quality. Overall this step has saved me at least ~7TB so far (Tdarr reports it’s saved 4.8TB, but I converted a ton of stuff with Embys convert feature before implementing Tdarr). That conversion can only be done after seeding or the torrent breaks as the original files are no longer available to seed. Usenet removes the seeding step completely, so I can do whatever I want with the files as soon as they’ve downloaded, which in it self only takes 5min.




  • Darkassassin07@lemmy.catomemes@lemmy.worldThe Next (De)Generation
    link
    fedilink
    English
    arrow-up
    26
    ·
    edit-2
    2 days ago

    This was one of my biggest motivations for moving to usenet. I don’t like exposing myself by seeding. I have a giant folder full of copyright notices forwarded by my ISP because of it, and I don’t want to pay for a vpn as it’s far more expensive than usenet and just moves the problem/target to the vpn provider.

    But an ssl connection to a usenet server goes unnoticed… Plus WAY faster download speeds, far more consistency in available files, and less spam/garbage content (at least in my experience, anecdotal).


    Torrents took anywhere from an hour to multiple days before either completing or giving up and trying a different torrent. And then there’s the seeding process ontop.

    NZBs (usenet) take at the very most, 5min to finish or fail, at which point a new one can be tried automatically by sonarr/radarr if it had failed. Requests for media are now pretty much always ready to watch within 25min of requesting, and most of that is waiting for the library scan to trigger (I’m using SAMBA so filesystem updates can’t trigger scans automatically, they’re on a timer instead)




  • If you have a static IP address, you can just use A records for each subdomain you want to use and not really worry about it.

    If you do not have a static IP address, you may want to use one single A record, usually your base domain (example.com), then CNAME records for each of your subdomains.

    A CNAME record is used to point one name at another name, in this case your base domain. This way, when your IP address changes, you only have to change the one A record and all the CNAME records will point at that new IP as well.

    Example:

    A example.com 1.2.3.4

    CNAME sub1.example.com example.com

    CNAME sub2.example.com example.com

    You’d then use a tool like ACME.sh to automatically update that single A record when your IP changes.