Moving your port over to a nonstandard one is not a solution (unless the problem you experience is too many logs from sshd, and even then, logrotate exists), its security by obscurity which doesn’t really solve anything at all. Only way your server will be safe is by ensuring the packages on your server are up to date and that you harden it to the point where it isn’t too much of nuisance.
It is aimed at members (often new)of private trackers, a hobby which often assumes you’ve already got a 170tb NAS at home that just needs content to fill it. This is evidenced by the fact they inherit HDBs “golden popcorn” system and tier their groups pretty high up.
I think TRaSH serves as a good base. Their custom filters can be instantly imported using recyclarr and give you a general idea of how custom filters are meant to be used (which can be very overwhelming when you’re new to the ordeal) but sadly I disagree with TRaSH a lot on their group tiers for media formats. I think they make some mistakes placing some encoders as high as they do. (for example: micro encodes from PTer and BHDStudio shouldn’t be in the BluRay groups at all, as some of their releases are compressed harder than WEB releases from streaming services. I download BluRay encodes because I want it to be compressed to the point where it still looks identical to the BluRay it was sourced from.) Once you’re in the game long enough you just make up your own mind on what release groups should be prioritized over others.
As for your question regarding staying within the same file system, the answer is yes. Moving things over to the SSD does two things for you. 1) for every file you also need a duplicate on the SSD, not very efficient. 2) there’s not much to gain from this unless you’re expecting a large amount of simultaneous traffic. An HDD can carry about ~20 streams of 1080p content (as most releases are compressed to 8-10mbps) which is more than enough for most households.
I’d keep the SSD for seeding honestly, so that you can build up buffer on the trackers you’re on, but for most it’s still perfectly doable with HDDs only.
Cloud computing can be replaced (albeit it’s a hard process, sorta like detox). Good luck starting an independent ICANN and DNS zones.
0.0.0.0 means listen on all IPs
The only thing that’s worse than having the US as your enemy, is having the US as your ally.
For the license to be changed every team member needs to submit a written agreement that he agrees to the change, otherwise their contributions must be removed as they were written under a different license, the only exception is usually permissive licenses such as MIT/BSD 3 clause.
Usually, to rugpull FOSS contributors, companies who maintain FOSS software ask contributors to sign a CLA which waives their rights and lets the control their contributions. Immich isn’t doing any of that, and it will likely remain AGPL forever because changing the license will be a big hassle for them with the amount of contributors.
Hi, I recommend you read the book “Run Your Own Mail Server”. The fact that a book exists for this topic is all the proof you need to not do this decision. But if you absolutely must, this is the way.
You’ll be surprised how cheap some equipment goes for when a company runs out of business. Just sayin
Pretty good. Downloads on the main app has been something that held people back.