People suggested formatting to exFAT which is valid, but first you could just try either compressing the file (tar czvf file tarball.tgz for instance). FAT32 cannot handle files larger than 4GB, and compression might just make your file small enough.
As a workaround you could also split it in half and stich it back on the target machine
My guess is click farms with some unknown custom made os that skew that data?
That also might be a source of Linux users hence the relatively high market share of the OS?
Not to mention that India still has a lot of call centers (some for scams) that may use Linux because it's free (compared to a windows license)
I've used truenas scale (comes with k3s preinstalled) and I ended up fucking up the cluster on accident a couple of times (mostly because of power outages), I've since moved over to Debian and a manual kubeadm install. Will make upgrading the cluster a bit more painful, but so far it's stable (ish, I have had issues with the Nvidia containerd backend)
I know that banks in Europe are bound by law to follow PSD2, which is a set of guidelines to propose APIs. I found a stackoverflow post to generate the required certificates for that but those are only supposed to be for testing purposes https://stackoverflow.com/questions/50045376/how-to-create-eidas-certificate-with-qwac-and-qsealc-profiles-psd2-specific-att
You can use the PSD2 api to fetch the transactions from your account directly, that would be a lot less troublesome. There is also the woob (formerly weboob) project that has web scraping for a lot of banks (specifically french but also some American ones like amex)
Isn't that when trolls decided to post child abuse material on lemmy world? Since it's a large instance it federated to a bunch of others whose admin, rightfully so, decided to take down their instance to avoid legal repercussions, as well as take the time to clean everything up
You could use grafana loki to handle logs, it's similar to Prometheus so if you're already using that and/or grafana it's an easy setup and the API is really simple too.
What's wrong with 12ft?
Kinda expected it to be honest. That kind of behaviour is what prevents more developers from joining open source projects and contributing in the first place. When you go through the effort of, on your own time of forking, cloning, patching, compiling, testing, and make the pull request only to be shut down at the finish line for bullshit reasons, it's nothing but discouraging.
There are already tools existing for dyndns that are free. If you're using cloud flare as your dns provider, there's cloudflareddns that checks your public ip and updates dns records. You just need 1 record to be updated, the other records can just be CNAME to that primary one.
OVH has DynHost to deal with that as well.
You could also write a script to do that with your own DNS provider if one doesn't exist yet. Most have good APIs you can use to that extent. At worse just use cloudflare since it just works and is well supported.
They get hated on because :
they inspect packets. They terminate the TLS sessions at their servers and reencrypt to forward to the backend. This allows them to analyze the data to spot spam, optimize compression and such
they are used everywhere. If they go down, 30% of the internet goes with them.