I post content. You view content. I moderate content. You no like, you no pay

  • 7 Posts
  • 40 Comments
Joined 1 year ago
cake
Cake day: June 6th, 2023

help-circle



  • DMCA only come from trackers that are open to the world. ISPs don’t snitch on you. They only do what is required of them by law, usually. (Forwarding DMCA complaints).
    The copyright companies, connect to these trackers and perform regular torrent client requests, such as “hey, who is seeding this torrent”. And the tracker responds. They take note of the IPs and do whatever they do.

    Deep Packet Inspection (DPI) can only find out that you are doing a P2P connection and possibly torrenting. Which in of itself is not illegal.

    With private torrents you are blocked from the DMCA copyright companies because they cannot find out what torrents are on the trackers because you need the metadata of a torrent & the password to get the peer list.

    A VPN only solves the problem where the ISP is hostile to you, the consumer and obfuscates who you are connecting too. With DPI and packet analysis (which is slightly expensive) they could figure out you are torrenting via a VPN with a high degree of certainty. Butt at the end of the day, all they would see is encrypted packets. This data is no different than telling your torrent client to Force Encryption, which everyone should do and I get annoyed all the time when people don’t have it on.

    Tldr,

    • VPN only blocks ISP from seeing unencrypted P2P traffic and makes it harder to identify.
    • DMCA companies can only access public trackers peer lists where it gets its information from







  • I have a Pi4B but with a m2 drive as the OS instead of the sdcard which I highly recommend due to the amount of read/write downloading files does.

    A pi4 should have 0 trouble (via ethernet) doing anything you are saying.

    From what I could tell your setup is internet -> pi4 -> appletv. If the pi & applet are on Wifi that would be a huge issue. The most any wifi can realistically do is 270mbps and that is when you are next to the damn thing.
    As let’s say you are streaming 1080p content which requires around 20-50mbps. Router to pi (20mbps) + pi to router (20mbps) + router to Apple TV 20mbps), so you’d already be pushing 60mbps at best internally all over wifi.

    Temporarily add cables to everything if possible or move the pi onto a cable as a minimum. then you will cut down on the back-and-forth it needs to do over wifi so then your router can dedicate all its bandwidth to sending the data to the appletv.


    If it’s all on cables already then I guess it’s a filesystem issue, as your not using a SSD but using a SD card. Run iostat via command line while streaming and see if there is any big “iowait” values. I’d there is then your sd card is not keeping up with the total bandwidth










  • You might have setup something wrong then. It should work. The problem with torrenting on 1 server and saving the data to another directly via smb/NFS is that every write is at the behest of uploading to that network storage.

    What would be better might be that you:

    • add categories
    • mount /completed/tv/ as a network share to hetzner-storage
    • then only when the torrenting is done does it auto copy the data to the SMB share

    I have this all done internally. I torrent on one box, it’s finished and gets moved via NFS to the storage server. Which sonarr/radarr file away. They notify jellyfin to resync the library. The jellyfin box has the storage box mounted via NFS.

    If you can test with small files, IE copy a 100m file onto the SMB share and then see if that was replicated to the storage box then you will have the basis of the solution.