A lot of people self host so they are in control. This is Plex taking away that control, plain and simple.

I don't know how many people host completely legitimately acquired content in their libraries, but your reasoning is such a cop out. Are you gonna defend them if they start scanning libraries for potentially illegally obtained content and blocking that because it could "put them in legal hot water?"

Wow this is great. I've been having trouble getting exit nodes working properly with these two. Sad that mullvad dropped port forwarding though so I'm not sure if I'll stay with them.

It's a special feature in Sync. Just long press an option in settings and it copies the markdown to your clipboard

Yep.

Settings shortcut: Comment options > Collapse parent

This usually happens to me after I check my inbox if there's nothing there. A quick force close and reopen always fixes it. Not ideal, but not a big enough problem for me to try to do something about it

This is ultimately why I decided to roll my own instance. I'm keeping my backup here though in case I mess something up, but full control is nice to have.

From Summit:

You can already do this. You can specify an env file or use the default .env file.

The compose file would look like this:

environment:
      PUBLIC_RADARR_API_KEY: ${PUBLIC_RADARR_API_KEY}
      PUBLIC_RADARR_BASE_URL: ${PUBLIC_RADARR_BASE_URL}
      PUBLIC_SONARR_API_KEY: ${PUBLIC_SONARR_API_KEY}
      PUBLIC_SONARR_BASE_URL: ${PUBLIC_SONARR_BASE_URL}
      PUBLIC_JELLYFIN_API_KEY: ${PUBLIC_JELLYFIN_API_KEY}
      PUBLIC_JELLYFIN_URL: ${PUBLIC_JELLYFIN_URL}

And your .env file would look like this:

PUBLIC_RADARR_API_KEY=yourapikeyhere
PUBLIC_RADARR_BASE_URL=http://127.0.0.1:7878
PUBLIC_SONARR_API_KEY=yourapikeyhere
PUBLIC_SONARR_BASE_URL=http://127.0.0.1:8989
PUBLIC_JELLYFIN_API_KEY=yourapikeyhere
PUBLIC_JELLYFIN_URL=http://127.0.0.1:8096

This is how I do all of my compose files and then I throw .env in .gitignore and throw it into a local forgejo instance.

They have a similar integration with Bitwarden that I've used a bit. I ended up stopping though because I rely on a catch-all and just give out companyname@ or something generic like work@ or family@. Sure it's easy to guess but I haven't had any spam issues in the ~15 years I've been operating this way.

Nobody actually gets my Fastmail login address though. I picked a random string on one of their domains that's literally only used to sign in. A fun little added obscurity feature.

I moved to Fastmail last year and it's been entirely unremarkable which is exactly what I want. Mail in and out works, it's reliable, I have my custom domains.

It really depends on the level of privacy you're going for and what features you want. For me I needed custom domain support with catchalls. The only other requirement I had was to not be Google. I debated between Fastmail and Proton for a while (Fastmail for features/price, Proton for the "better" privacy.) Ultimately I ended up on Fastmail because I would have had to pay for a higher than necessary account at Proton for what I wanted.

Like others have asked, how exactly did you create these containers? If they were through Portainer did you use a compose file in a stack or did you use the GUI the entire way?

This will nuke them assuming you don't have something recreating them.

docker ps -a # find your rogue container, copy the container id, my example is a0ff66a83c73
docker stop a0ff66a83c73
docker rm a0ff66a83c73

My suggestion is to go through the process you did to try to deploy them and clean it up from that direction.

I pretty much always leave stuff seeding once I get it these days. Ever since I bumped the disk space on my NAS it made it a lot easier to leave stuff instead of jockeying for space on disk.

My higher ratio items are all old shits like You Got Served lmao