I think that considering the federal bill in the US currently aimed at forcing ISPs and VPN providers to block foreign piracy websites that copyright holders absolutely see piracy as an untapped market. Even if their plan is to ban their competition rather than change their business practices in a way that would attract those customers

I use Proton and i don’t know if that same functionality exists, but it does have a dedicated service for aliases that automatically forward back to your inbox so you just make an alias for a given use case and use that without exposing your actual email address, then if it gets too spammy you can delete the whole alias and never receive the spam addressed to it.

The idea being you can use it like an alias, so if you give youtube the address of “myemail+youtube@gmail.com” then when you get unsolicited spam emails addressed to “myemail+youtube@gmail.com” you know which service sold your information. Probably also makes it easier to sort the inbox based on where it is addressed

Ive got a reverse proxy config that was available in the Audiobookshelf github documentation, I was mainly struggling to understand how to get all of the parts working together. Thanks for the help

Is 172.17.0.1 like dockers loopback for its own services?

I had considered the VPN route, but i think its enough of a technical hurdle for other people that it would stop my parents and friends from being able/willing to get onto the audiobookshelf server

I had considered not using nginx for precisely those reasons, but like the plex server i want to make it available to my family and friends and so the nginx reverse proxy build seemed to be the most widely applicable and still secure option so I only need to tell them to download audiobookshelf and point it at the correct domain name.

Thank you so much this is very helpful, I’ll definitely be taking a run at it with all of this advice in mind this week. When you mention running the whole thing as a single stack does that mean getting all of it running inside a single docker container such that it only takes the 1 docker run command? Is it a requirement to get them able to talk or just a more elegant way to have the entirety of the server running in a singular container instead of spread across several?

I know, and that’s on my to-do list, but I wanted to get this up and running at least once before upgrading and potentially having to start from square 1.