Same here, I’ve never had this problem, ever. I don’t even get how it’s possible to not know where your files are being saved if you are the least bit techsavvy.
wpuckering
- 0 posts
- 6 comments
Joined 3 years ago
Cake day: June 5th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
- wpuckering@lm.williampuckering.comtoGaming@beehaw.org•Most emotional moments in games? (SPOILERS)English3 years
The ending of Soma.
- wpuckering@lm.williampuckering.comto
3 yearsInstalled Sync as soon as I could, but went back to Jerboa for now due to lack of a one-time purchase option. Not a fan of subscriptions, I need less of those in my life.
- 3 years
I run all of my services in containers, and intentionally leave my Docker host as barebones as possible so that it’s disposable (I don’t backup anything aside from data to do with the services themselves, the host can be launched into the sun without any backups and it wouldn’t matter). I like to keep things simple yet practical, so I just run a nightly cron job that spins down all my stacks, creates archives of everything as-is at that time, and uploads them to Wasabi, AWS S3, and Backblaze B2. Then everything just spins back up, rinse and repeat the next night. I use lifecycle policies to keep the last 90 days worth of backups.
You shouldn’t be charged for unauthorized requests to your buckets. Currently if you know any person’s bucket name, which is easily discoverable if you know what you’re doing, that means you can maliciously rack up their bill just to hurt them financially by spamming it with anonymous requests.