MultiPar VS Nyuu

but... depending on how much effort you want to spend fixing it I might be able to fix your current corrupt files, especially if the corrupt files are only mildly corrupt I could create a '.par2' file from mine (assuming you are on build 1436.28), then you would use MultiPar (i.e. https://github.com/Yutaka-Sawada/MultiPar/releases ) to scan your files and it will tell me how many blocks you need to fix it and then I could create recovery data with MultiPar. doing this might dramatically lower the amount of data I would have to upload as then you could use MultiPar which will fix your current corrupt files so they match mine identically.

MultiPar is the continuation for Windows https://github.com/Yutaka-Sawada/MultiPar

And this for Linux https://github.com/animetosho/par2cmdline-turbo

* MultiPar supports in-situ repair, which bypasses this problem entirely

To detect bitrot I use dynamix file integrity plugin, it compute Blake3 hash for each file, it is stored as extend attribute. You Can choose which share will be covered. For correction i then use par2 files using multipar https://hp.vector.co.jp/authors/VA021385/ https://github.com/Yutaka-Sawada/MultiPar (Windows only, par2cmdline for Linux. You could compile from source and add it to unraid if you want, i've done it for testing purpose)

And last but not less important - make regular parity files of your healthy important data, and store them somewhere. MultiPar is your best friend. Even if your data gets corrupt, with parity files you can restore it to it's former glory. Some limitations will apply, read the manual.

This is possible with MultiPar https://github.com/Yutaka-Sawada/MultiPar

More sanely, perhaps, get some M-Disc DVDs (if you can find real ones - apparently they're becoming just normal DVDs) and put one file on each, and then run https://github.com/Yutaka-Sawada/MultiPar on it to create parity files. Then store the file, the parity files, and the software you need (MultiPar) on the disc. To be safe, you probably also need to store the DVD burner you used to make it, as those are getting thin on the ground these days.

Note about par2: if one is using a windows system with a nvidia GPU this version of par2 is faster as it speaks CUDA.

For any file repairs use multipar, it's still being updated and has gpu acceleration. https://github.com/Yutaka-Sawada/MultiPar/releases

Hopefully that slowly stops being the standard: https://github.com/animetosho/Nyuu/wiki/Stop-RAR-Uploads

Can someone eli5 how to do it? I've looked at https://github.com/animetosho/Nyuu/wiki/Usenet-Uploaders but I don't know to how to install these. The github links on that page are confusing to me as I don't know where to click to actually download the programs.

* does depend a bit on how crazy/complex you want to go I suppose. My NNTP implementation ended up being a lot less straightforward, as I put a lot of effort into error handling / retry functionality (which I don't see implemented in most libraries), and speed optimised yEnc isn't exactly straightforward either

It's used as a poor man's BitTorrent equivalent for FTP, in some prominent sharing circles. Of course, BitTorrent exists, but getting some people to adopt technology invented this millennium can be difficult. It's also still used by many Usenet uploaders likely due to misconceptions on how the system works. Again, it makes little technical sense today, but it's an old environment with a lot of old traditions.

That's the conclusion I came to, but contrary to expectations, I saw newer uploaders lowering it to 700k for compatibility instead. - https://github.com/demanuel/NewsUP/pull/67 - https://github.com/animetosho/Nyuu/issues/1

You do not need to split your file. RARs are unnecessary on Usenet https://github.com/animetosho/Nyuu/wiki/Stop-RAR-Uploads

In theory, it's possible if there's no missing articles and uploaders stop RARing uploads.

All the posting tools make a NZB file as they upload https://github.com/animetosho/nyuu

Yet another reason to get uploaders to stop RARing uploads. Just spreading the word around ;)