I very recently started using borgbackup. I'm extremely impressed with how much it compressed the data before sending, and how well it detects changes and only sends the difference. I have not yet attempted a proper restore from backup, though.
I have much less data I'm currently securing (50gb) and much more uplink bandwidth (115mbps) so my situation isn't nearly as dire. But it was able to compress that down to less than 25gb before sending, and after the initial upload, the next week's backup only required about 100mb of data transfer.
If you can find a way to seed your data from a faster location, reduce the amount you need to back up, and/or break it up into multiple smaller transfers, this might be an effective solution for you.
Borgbase's highest plan has an upper limit of 8TB, which you would be brushing right up against, but Hetzner storage boxes go up to 20TB and officially support Borg.
Outside of that, if you don't expect the data to change often, you might be looking for some sort of cheap S3 storage from AWS or other similar large datacenter company. But you'll still need to find a way to actually get them the data safely, and I'm not sure if they support differential uploads like Borg does.
I distinctly remember Democrats opposing Trump on moving the embassy to Jerusalem. They never fought him as much as they should, but they did fight him.
Exactly, so we can't rely on Democrats to effectively contain Trump as you suggested we might. They are not strong or reliable enough. They capitulate far too easily.
Let's not forget this is also what lead to the rise of the DSA and the largest protest movement in American history.
What really led to the DSA growing so much was Bernie Sanders radicalizing millions with his 2016 run. Then, the squad capitalized on that energy in 2018 and onwards, leading to many DSA members being elected nationwide, which then further grew the organization through the attention they bring.
I know it's not considered "cool" amongst leftists to admit electoralism can ever lead to positive outcomes, but them's the breaks. None of this would have happened if not for them.
It's far better than it used to be. They didn't get the reputation for no reason. There were lots of Nvidia-specific bugs that have been slowly sorted out over the years. I'm told Wayland is even in a roughly usable state now. But it takes a lot of time to regain the lost trust. Let's see how long it takes them to support HDR, and what that support looks like.
This is just completely ahistorical. Democrats repeatedly worked with Trump throughout his presidency. Pelosi and Schumer met with him constantly to try and broker deals. They literally bragged constantly about "crossing the aisle", how they were "moderates". Dems love posturing as the mature adults in the room.
In some instances, it was legitimate to work together. They supported his administration's 2019 infrastructure plan. Trump worked with Dems instead of the GOP to get hurricane relief. Some good spending packages were passed by him working with Dems when the GOP was too disorganized.
In other cases, they should have obstructed harder but didn't. They fast tracked many of his federal judge appointments. Some voted for his supreme court picks. They didn't obstruct his tax cuts enough.
The idea that Democrats were impetulently obstinate with Trump for no reason is a far-right talking point, it has no basis in reality, so I'm not sure why I'm seeing supposed leftists repeating such misinfo. They weren't obstinate enough with Trump, especially when it mattered; that's part of the problem with Democrats! They're far too conciliatory to the right-wing! That's why we hate them, remember?
No they wouldn't. They would happily work with Republicans to fund Israel. I have no idea where you got it in your head that Democrats have any sort of tendency towards contrarianism; they trip over their own feet rushing to work with the Republicans on anything they can to prove they're "moderate" and "non-partisan".
You shouldn't put a protector on it. If you get a normal protector, you're basically just re-adding glare. If you get an anti-glare protector, you're further increasing the blurriness and darkening the screen, as that's how anti-glare works. The adhesive will also fill in the etching and reduce its effectiveness (search for "scotch tape frosted glass", same concept), but how permanent that is has never truly been verified; presumably, a good rub with alcohol should fix that problem.
The goal here is to make it difficult to link to things uploaded to discord from outside of discord. The malware reason is BS. If they wanted to curb malware it would be as easy as making it a nitro feature. What that doesn't fix is all the people piggybacking on discord as a free CDN.
Discord isn't even wrong for doing this. I just resent their dishonesty.
The computer didn't get it wrong; the computer did exactly what it was programmed to do. Blaming the computer implies that this can be solved by fixing the computer, that it "just wasn't good enough yet", when it was the humans who actually did it. It was the humans who were supposed to exercise their judgment that got it wrong. You can't fix that from the computer.
Convincing argument, but unfortunately a cursory Google search will reveal he was right. There is very little CPU overhead. The only real consideration is a bite extra storage and RAM to store and load the redundant dependencies of the container.
While that isn't false, defaults carry immense weight. Also, very few have the means to host at scale like Docker Hub; if the goal is to not just repeat the same mistake later, each project would have to host their own, or perhaps band together into smaller groups. And unfortunately, being a good programmer does not make you good at devops or sysadmin work, so now we need to involve more people with those skillsets.
To be clear, I'm totally in favor of this kind of fragmentation. I'm just also realistic about what it means.
I very recently started using borgbackup. I'm extremely impressed with how much it compressed the data before sending, and how well it detects changes and only sends the difference. I have not yet attempted a proper restore from backup, though.
I have much less data I'm currently securing (50gb) and much more uplink bandwidth (115mbps) so my situation isn't nearly as dire. But it was able to compress that down to less than 25gb before sending, and after the initial upload, the next week's backup only required about 100mb of data transfer.
If you can find a way to seed your data from a faster location, reduce the amount you need to back up, and/or break it up into multiple smaller transfers, this might be an effective solution for you.
Borgbase's highest plan has an upper limit of 8TB, which you would be brushing right up against, but Hetzner storage boxes go up to 20TB and officially support Borg.
Outside of that, if you don't expect the data to change often, you might be looking for some sort of cheap S3 storage from AWS or other similar large datacenter company. But you'll still need to find a way to actually get them the data safely, and I'm not sure if they support differential uploads like Borg does.