Done!

I don’t recall w.cd having FL first week, but they did have semi regular weeks. Mebbe you filled it? I had a seedbox, when a FL period started I redid my entire library and permaseeded, shot through the ranks and was basically set for life.

I miss w.cd

Mechanics I’ve seen to avoid this:

• Occasional sitewide freeleech
• bonus points for seeding duration irregardless of upload, can be traded for reducing download
• freeleech torrents (only counts upload not download)
• partial freeleech (25/50/75% download counted)
• Timed freeleech (free first 24h)
• Download % counted reduced based on seed size (seed >1tb and everything’s freeleech)
• Reduction of download % counted based on rank
• Forum competitions for bonus points/freeleech tokens
• Freeleech tokens giveouts

Hell, there’s quite a few PT’s that don’t care about ratio and just have minimum seeding times on torrents.

Plenty of these trackers have been running 1-2 decades on 1 or more of these methods just fine.

Almost every site is laughably easy to keep ratio if you read the rules/FAQ, look at some what’s to build points/ratio, read the forums, and don’t go nuts In the first week while your establishing your account

Man there’s a lot of the last note app you’ll ever need!

I run nixos, so my entire homelab servers setup is stored in my github. I can rebuild a server and restore backups from that (and sops keys). I significantly prefer this to having to remember and note a huge bunch of things to setup a computer - this way a rebuild on new oc is only a few hours tops

Depends on the circumstances tbh. Things like sops do load the secret unencrypted on the machine (with perms but still unencrypted. For remote VPS encrypted at rest is probably better. K8S has secret management but there unencrypted too.

Another alternative could be using Doppler secrets managment platform, I used it for a while

I think it’s overkill for homelab and over complex/additional failure points.

I use sops encrypted, published in my public git. When I apply my nix config, they are pulled and unencrypted on apply on the local machine.

Keeps it as simple as I can think of, with few moving parts.

Trillium notes

Definitely renovate it and keeping your code in a bit using gotops principles. When I run k8s I used flux to reconcile my reponstate to my clusters.