Ah cool, I knew there was patent problems keeping it out, but I also haven't used a USB drive of any meaningful size in a while (I went NAS over removable storage) but that's nice that there's a "universal" file system.
IIRC, exFAT is still a fuse module, but FAT32 is kernel native, if that's a thing that matters (in case you're ever on a Linux where you can't install fuse+exFAT).
It doesn't seem all that limited; I'll get 4-5 in a burst, then nothing for a couple of hours or a day or so, then 4-5 more, and so on.
Been ongoing for a couple of months now, and given it's a random 6 digit number, I don't think they're even remotely doing enough attempts to try to brute force it.
To add for people who might not be up on the technical aspects: DDOS mitigation works only if you have absolutely enormous amounts of bandwidth and compute resources to intercept and scrub the traffic.
It's not some magic wand someone is waving at a server and poof the DDOS disappears; it still comes into a datacenter, hits a server and is then mitigated before making it to your actual host.
So you have to invest in enough bandwidth and hardware to outscale the largest DDOS you're expecting, which is going to be far less than what's going to REALLY happen, and it has to be available even when nothing is going on.
It's expensive to offer, expensive to run, and only really gets "affordable" at the scale of someone like Cloudflare or Akamai or a hyperscaler.
It's either private, good, or cheap: pick one, maybe two.
Maybe I misread the article, but this would have simply given poorer people the same incentive richer ones ALREADY get, and.... the argument Republicans have is essentially fuck you, you worthless poor person?
If you write the script yourself, just make sure you test it a couple of times, and preferably with different datasets from different runs.
I found some edgecase stuff that would have prevented a restore even after I had tested it successfully (some permission issues due to changes in containers and whatnot were resulting in less than the expected data being archived and restored) a couple of times.
Everything is deployed with a docker compose, and all the docker volume data are bind mounts and, for example, a Jellyfin install would have everything in /stacks/jellyfin.
The backup script makes a tarball of each service individually (and stops the stack if there's anything in there doing database things or anything else that might end up being inconsistent by just archiving the filesystem), and uploads them to a S3 storage provider AND burns them to a BluRay.
The recovery script does the opposite: it downloads and unarchives the data.
As long as you're on Linux and have Docker, it should just magically work.
Like most things with fascists, it's a show of loyalty. Sure, it's not dressing up in Hugo Boss and marching through the streets, but for 2024, 'Oh, I use Truth Social' is more or less the same kind of indicator.
This is going to be a bit of my grumpy-greybeard, but again: if you're learning, then something like Docker and docker-compose is much simpler and less prone to fuckups than a bunch of K8s.
If you don't know ANYTHING about what you're doing, starting with the simplest tools and then deciding if you want to learn the more complicated ones is probably a less insane path than jumping right into the configuration-as-code DevOps pipeline.
And, at that point, you should have your "production" and "testing" environments set up in such a way they won't eat each other when you do an oops.
Ah cool, I knew there was patent problems keeping it out, but I also haven't used a USB drive of any meaningful size in a while (I went NAS over removable storage) but that's nice that there's a "universal" file system.