It is, but doesn't really play well with PTs in general. Not all trackers support it (some of the software is that old), and even when it works I've run into unexpected issues.
I would like it if there was increased adoption.
It is, but doesn't really play well with PTs in general. Not all trackers support it (some of the software is that old), and even when it works I've run into unexpected issues.
I would like it if there was increased adoption.
I don't know of any private trackers who are interested in users in your particular circumstances. The reality is, you can't really seed behind CGNAT. I would really consider shelling out for a VPN, you can get an okay one for 5-10 euro a month. If you're technically inclined, you could even set your own up on a cheap VPS for less, given you don't need fast networking.
If you have more experience with Linux CLI over powershell, I'd go with that. There are a few options: WSL2, MSYS2, Cygwin.
It makes way more sense to implement an auth cooldown over increasing the server load for a single action. I can't speak on the ideal settings for Argon2id, but I like to think the defaults are fine in most cases.
It is possible to tonemap DV to SDR, and I think to static HDR as well. Look into madvr and/or mpv. Both should be able to provide real-time tonemapping during playback. For reference, these pink/green videos would be DV Profile 5 (P5). I've heard the results are not great, so I would stick with P8 hybrid releases.
To start small setup a static website behind nginx. This requires you to create a basic website or copy a template, it goes somewhere in your filesystem, in linux /var/www is common. Once you have that, setup the nginx service and point it to that location. You can do this locally then expose it to the net or put on a VPS. Here is a dead simple guide presuming you have a remote server: https://dev.to/starcc/how-to-deploy-a-simple-website-with-nginx-a-comically-easy-guide-202g
Once you have that covered, ensure you know how to setup ssh keys and such, then install, configure, and run services. From there, most things are easy outside of overly complicated configurations.
Whether you like it or not, that's more or less what happens. You can/will lose a bunch of accounts for causing trouble. Sometimes I think it's a bit over the top. Instead of keeping out toxic or non-contributing folks it becomes a personal vendetta or innocent violation.
Overall, I'm a fan of banning known bad users, but restraint should be used and collected personal information should be minimized.
When you are seeding, you broadcast to other peers that you have pieces available. The most efficient way to exchange data is for them to open a connection to you. Without an open port (from port forwarding) they have no way to make this direct connection.
I happened across this tool to help you create configs, it looks pretty good, easier than piecing together all the parameters separately: https://www.digitalocean.com/community/tools/nginx
Seems like it has directions for certbot and generating dhparams, etc. as well.
I would approach it this way:
From there you can work your way up to full automation and such if you like. I don't think it's necessary for most people.
As for data layout, just make some folders like movies, tv, music, etc, and lay out stuff in there logically. If you have a fancy storage setup, you might do separate shares for them, whatever works for you. Some people like to link from their "download" folder into their actual media folder to keep things clean. You can do hard and soft links on Windows with NTFS, but it's kind of a pain.
Mullvad doesn't have port forwarding, so that's going to be a factor.
Yeah, you can turn off registration without a token. Then, if you want someone to register you can issue them a registration token, or manually create their account.
Federation can be turned on, on a case by case basis.
You can set rooms to invite only and not discoverable. Alternately, you can use an invite-only space that allows users to join rooms from there.
The first two parts are done in the server config, see the synapse docs. The last is done once the server is setup and running as an admin.