Yes it’s already enabled, which is how I assume it’s working in Plex. Jellyfin isn’t even deciding to transcode to hevc, so it seems like more of a detection thing in jellyfin since it works fine in Plex web

So I just grabbed the nightly and it looks like it’s direct playing hevc in Plex. Jellyfin still says codec not supported for me, not sure if I have any settings wrong or of they need to change the auto detect in jellyfin.

Sure, but you also don’t need to give them full benefit of the doubt just because that’s how the court operates. It’s a perfectly reasonable stance to not believe their claim that they loopholed the law by not seeding, which I don’t think is contradictory with supporting piracy. And comparing the mass ingestion of human creative work into an exploitative AI model to an individual person pirating for human consumption as if someone who is against one must be against the other is absurd.

My argument is that just because the courts may give Meta the benefit of the doubt, it doesn’t mean that you need to as well. It shouldn’t be any surprise to you that you’re getting the response you’re getting here when you seem to be bending over backwards to find any excuse to give Meta a pass.

And no - wanting Meta to be fully investigated on the basis that they most likely did break the law has no bearing on wanting to oppress the enemy lol.

I’m not a court so absent any actual evidence from Meta, I can assume whatever I want. Meta can suck a dick.

It’s a distinction without a difference, because there is no reason to believe Meta’s word that they blocked seeding when downloading. So whether it’s always or usually makes no difference, because in either case, Meta should not be given the benefit of the doubt.

Both things can be true at the same time - you can get a letter for leeching only AND usually when leeching you are also seeding. I don’t know what your issue is with that statement.

I don’t know if this is news to you or not, but while you are leeching, you are also seeding.

I am the reader and I have made the determination that you are wrong. Plenty of people get letters for leeching only - just your presence in the swarm is all it takes, and that’s all they check for before sending you a letter - at least in the US.

One related thing to watch out for is the state table size - one of my old cheap routers back in the day showed how full it was and it was hitting 100% a lot and seemed to grind the network to a halt when it did (I was in a house of 5 young people with lots of devices and multiple people torrenting behind a cheapo Netgear running ddwrt). That’s what lead me to switch to high end or x86 based routers. Being able to see the state table stats really helps to know how likely it is to be a problem, it’s so big when using opnsense on an x86 box that I don’t think it ever goes above 1% now.

Edit: now that I think about it, if your VPN is working I wouldn’t expect any states related to peer connections to show up since your router won’t be NATing them, I guess I was just bold back in the day because it was a huge problem then.

Not really, as long as your VPN setup is solid (assuming you need it to avoid letters) and you don’t mind the bandwidth usage. I have some ratios in the 500s

Sounds likely, I haven’t used port forwarding with my VPN since Mullvad stopped supporting it, so when I recently shared my own torrent I paid for 1 month of a seedbox just to make sure it seeds well and the seedbox uploaded ~50GB while my local setup on a VPN without port forwarding only uploaded 1.8GB (and it hardly showed any peers as if nobody was trying to download). So it seems peers had a much easier time connecting to the seedbox.

I have since setup port forwarding in gluetun for my local torrent client. I just wish there was more support for it because gluetun only has built in support for port forwarding for 2 providers (I guess automated requesting a forwarded port), and even then you still have to make your own script to automatically set the port in the torrent client when it’s assigned / changed. It’s possible that some providers do it more like Mullvad where you get assigned a port via the website that is tied to the VPN credentials, so you just have to plug the assigned port into the torrent client settings (that’s how it worked with Mullvad so I could just enter the port once and forget about it) but I haven’t checked other providers to see.

I interpreted the meme as sarcastic vindication not genuine surprise.

Partially yes, the tricky thing is that when using network_mode: "service:tailscale" (presumably on the caddy container since that’s what needs to receive traffic from the tailscale network), you won’t be able to attach the caddy container to any networks since it’s using the tailscale network stack. This means that in order for caddy to reach your containers, you will need to add the tailscale container itself to the relevant networks. Any attached containers will be connected as well.

(Not sure if I misread the first time or if you edited but the way you say it is right, add the tailscale container to the proxy network so that caddy will also be added and can reach the containers)

Here’s the super condensed version of what matters for connecting traefik/caddy to a VPN like wireguard/tailscale.

• I left out all WG config since presumably you know how to configure tailscale
• Left out acme / letsencrypt stuff since that would be different on caddy anyway
• You may need to configure caddy to trust the tailscale tunnel IP of the machine on the other end that will be reverse proxying over the tunnel.
• Traefik I guess requires you to specify the docker network to use to reach stuff, I just put anything that should be accessible into “ingress” as you can see. I’m not sure if my setup supports using a different proxy network per app but maybe caddy allows that.

My traefik compose:

services:
  wireguard:
    container_name: wireguard
    networks:
      - ingress

  traefik:
    network_mode: "service:wireguard"
    depends_on:
      - wireguard
    command:
      - "--entryPoints.web.proxyProtocol.trustedIPs=10.13.13.1" # Trust remote tunnel IP, the WG container is 10.13.13.2
      - "--entrypoints.websecure.address=:443"
      - "--entryPoints.websecure.proxyProtocol.trustedIPs=10.13.13.1"
      - "--entrypoints.web.http.redirections.entrypoint.to=websecure"
      - "--entrypoints.web.http.redirections.entrypoint.scheme=https"
      - "--entrypoints.web.http.redirections.entrypoint.priority=100"
      - "--providers.docker.exposedByDefault=false"
      - "--providers.docker.network=ingress"

networks:
  ingress:
    external: true

And then in a service’s docker-compose:

services:
  ui:
    image: myapp
    read_only: true
    restart: always
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.myapp.rule=Host(`xxxx.xxxx.xxxx`)"
      - "traefik.http.services.myapp.loadbalancer.server.port=80"
      - "traefik.http.routers.myapp.entrypoints=websecure"
      - "traefik.http.routers.myapp.tls.certresolver=mytlschallenge"
    networks:
      - ingress

networks:
  ingress:
    external: true

(edited to fix formatting on mobile)

I’ve done something similar but I’m not sure how helpful my example would be because I use wireguard instead of tailscale and traefik instead of caddy.

The principle is the same though, iirc I have my traefik container set to network_mode: “service:wireguard” so that the traefik container uses the wireguard container’s network stack. That way the traefik container also sees the wireguard interface and can receive traffic going to the wireguard IP. Then at the other end of the wireguard tunnel I can use haproxy to pass traffic to the wireguard IP through the tunnel and it automatically hits traefik.

So realized that the season pack from deadorbit uses subs from opensubtitles which seems to be missing on screen text translations and title-cards, so I remuxed in the subs OP linked - which appears to have been edited to include title-cards and on screen text - to replace the ones in the deadorbit pack. Here’s a base64-ed link to a paste with the magnet for that if anyone wants it since I already went through the work for my own collection - it’s 1080p web-dl x264 8 bit AC3 5.1

aHR0cHM6Ly9ub3RlYmluLmRlLz84MjYzYTQyYjhhYmZkNDhiI0V3cHA2ZmZOZnQ5REpzVmg0YWNndG9NZ2lOa2dENXlLalNzVHI1RktiZkJt

Edit: since torrents can be slow to start, here’s a direct download link on mega, if you download that way consider grabbing the torrent from the first link and pointing your torrent client to the downloaded files. And of course feel free to repost and reshare everything:

aHR0cHM6Ly9tZWdhLm56L2ZvbGRlci8xSVFHMVQ3SyN4UkYyM25WZ0xVZXpTd3NpSnRBVXNB

Thanks for the reminder to grab the subs for this, sonarr downloaded the ollonborre release a while back and I couldn’t find subs.

Looks like there’s now a season pack on 1337x from deadorbit with muxed eng subs, and all in DD5.1 too.

I’m pretty sure this will be a lot of work. Even assuming you didn’t rename any files and all the torrents are in a single folder, you still need to re-search for every torrent file and add them to a torrent client that should automatically find the files in the target location and check them to see that it’s already downloaded. I’m not sure if all torrent clients do this so I would advise testing it first - when re-adding a torrent with existing files I usually add it paused and then force re-check to be safe.

In theory it should be possible to make a program that does this - automatically indexes and crawls torrent sites and DHT, fetches torrent meta info, then scans your HD for matching files to seed. This feature is a proposed one for the DHT crawler “bit magnet” so I’m hopeful that one day there will be a program that can do that.

If the battery inverter in the Anker box doesn’t pass through grid power then I think you would use an automatic transfer switch that switches between mains and battery inverter depending on which is powered. I had dreams of offsetting my homelab power with solar + battery + inverter.

If the machine doesn’t boot then you can use this to access the bios and boot a recovery environment of your choice remotely using pxeboot.