Reading the takedown it sounds like just having the decryption code itself counts as “circumvention”. I feel like emulators would be a lot safer if game decryption was a separate codebase. Then the emulator would be free to develop while Nintendo plays whack a mole with tiny easily remade decryption repos that just take your key and the file and decrypt it.

Hell ryujinx could even detect that you have the decryptor installed and automatically call it when needed, or it could be bundled during packaging but separate in development like how Bluray decryption is distributed in a separately library but can be used by for eg. VLC.

Wow that’s impressive! I tend to be very value oriented, and at the sub $5 price, you’re getting so little that I feel like you’re mostly paying for a public IP and bandwidth. And of course selfhosting your compute is usually a win, especially if you already have something laying around. So I just pay the public IP tax for a reverse proxy and home host it all. I would probably go with a cheaper VPS for my reverse proxy but I need the confidence it’ll hold up to multiple friends Plex streaming.

Yeah if you aren’t down to publicly expose your IP address / port forward, the cheapest way I can think of still involves a several $/mo VPS that just reverse proxies home to a more powerful PC. That’s what I do since I’m behind CGNAT.

Not only is there the issue of getting approval from the video creators, there’s the issue that most PeerTube servers aren’t ready to handle a huge influx in uploads, as this would likely be a bulk operation.

Personally I think mirroring YouTube content would be more viable once ActivityPods lands and is integrated with PeerTube, which could potentially let you self host your PeerTube account data while still being part of a separate “home instance”, which would greatly help with the storage issue for PeerTube as we could all bring our own storage.

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.

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

I don’t really have a recommendation atm, I used to use mullvad but for torrenting I feel like the lack of port forwarding (once they removed that feature) was hurting my ability to seed so I switched to proton. I also recently added Usenet into my mix and since many providers bundle a VPN subscription - and mine in particular supposedly also supports port forwarding (usenetdirect bundles a ghost path VPN subscription), I’m gonna try to get it to work with that so I don’t have to pay for a VPN separately but I haven’t tried it yet.

Sounds like their strategy is to force US companies to block access to piracy sites.

I already run my torrent client through a non-US VPN so this can literally be bypassed by adding this to my prowlarr docker compose:

network_mode: service:gluetun

I think they’re making it more complicated than it needs to be. On any other social media site, you find people by their username. So just ask for your friends username (username@instance.com) and put it in the search bar and it’ll come up. Using the URL can be convenient on desktop because you can just copy and paste it from the address bar when you’re looking at someone’s profile.

And if you want to discover new people where you don’t already know their username, then I believe that is the same as any other social media as well, you can come across them in the comments of people you follow or go to the discover tab or search hashtags and you’ll find new people that you can tap on and follow.

I feel like this basically covers how you would find people. A lot of people get hung up on how you know what instance other people are on but it doesn’t usually matter. Either someone will give you their username which includes @instance.com, or if you don’t know the instance you can search for their name and all known accounts with that name will show up.

For example if I just search my username “BakedCatboy” (not my real username), the search results show both my mastodon and Pixelfed accounts.

It was waitlist for a while, not sure if it still is but I got my welcome email like a week later.

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.

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

aHR0cHM6Ly9ub3RlYmluLmRlLz9lMzk3YWE0OTdhYmQzNzkxIzVxeWRDODltY3JxVGluNEZUTTJlV1lnSEFoMnk2V1Q1dmNwTXRKWjVtOWFG